re: #89 BlueGrl21

I love engineers. I am an enterprise agile coach and our agile practice leader for all software engineering at a Fortune 50 company. I could not do the job if there was not a ton of love and respect there.

But our engineers asked me a long time ago to just shut them down if they start this. Just tell them to STOP and go do something useful. All of our managers and execs have that same mindset so they ask me to tell them to shut up too.

The worst are when I’m working with our architects and they get into fights over things like the difference between a Customer and an Account or a Location and an Area or Address. I will let it go until it becomes a total masturbatory conversation and then I ask what exactly we’re trying to accomplish here. Um. Accomplish? Yes. And we’ll be prototyping this too.

Again, long day.

agile, eh?

can you tell me what the agile development methodology is like in practice in your shop that makes it different from regular *iterative* development?

(hint: i said ‘iterative’ - i can’t remember the last time anybody made me do development waterfall style)

by ‘agile’, do you mean scrum? if so, does scrum in your shop consist of anything more than daily standups?