Wed, 18 March 2009 Self Organize ....... NOW. No really, we think it is important to create an environment that allows your teams to flourish. This seems like a "Black Art" but with enough space and encouragement it can not be stopped. Enjoy -bob Comments[2] |
Hey Bob,
I enjoyed the podcast on my way to work this morning. But I do have a question. It was mentioned that as Agile coaches we want to guide the team through questions, etc. rather than being prescriptive about how to do Agile. It was also mentioned that 'best practices' is sort of not what we want to impose on the team.
However, I couldn't help but feel a little confused. Agile does have a set of practices (although not necessarily 'best' for any one team) that reflect our values. You mentioned one of them as the Retrospective. So, we do in fact have a set of practices that we need to communicate to a new team effectively so they can know what tools they have in the toolbox. How do we best do this w/o seemingly prescribing the process that we think might work best?
My thoughts on this are that we:
- Communicate to the team, like you said, that nothing is set in stone and that we can experiment to see what works for us
- Lead the team down the path that we think might work best through questions and 'guiding', but still keep all the options open
- Describe all the practices to the team at a somewhat high level and connect them to the values that they have as a team
I guess it comes down to: How do you balance the need to communicate what Agile is and yet guide the team to their own 'best' implementation of Agile w/o being too prescriptive?
I enjoyed the podcast on my way to work this morning. But I do have a question. It was mentioned that as Agile coaches we want to guide the team through questions, etc. rather than being prescriptive about how to do Agile. It was also mentioned that 'best practices' is sort of not what we want to impose on the team.
However, I couldn't help but feel a little confused. Agile does have a set of practices (although not necessarily 'best' for any one team) that reflect our values. You mentioned one of them as the Retrospective. So, we do in fact have a set of practices that we need to communicate to a new team effectively so they can know what tools they have in the toolbox. How do we best do this w/o seemingly prescribing the process that we think might work best?
My thoughts on this are that we:
- Communicate to the team, like you said, that nothing is set in stone and that we can experiment to see what works for us
- Lead the team down the path that we think might work best through questions and 'guiding', but still keep all the options open
- Describe all the practices to the team at a somewhat high level and connect them to the values that they have as a team
I guess it comes down to: How do you balance the need to communicate what Agile is and yet guide the team to their own 'best' implementation of Agile w/o being too prescriptive?
Sounds like your approach is on the money. We could have been more clear that it is the "One Right Way" idea that we do not like.
We will take time to give a longer response in a "Listener Response" podcast to come.
Thanks for the question.
-bob
We will take time to give a longer response in a "Listener Response" podcast to come.
Thanks for the question.
-bob
posted by: agiletoolkit on Thu, 3/26 06:48 AM EDT
Post your comment:
