Archive for July, 2013


Sitting In A Teamroom Makes You As Agile As Sitting In A Garage Makes You A Chevy

July 8, 2013

You have a task board in your teamroom that you use to track the status of your users stories and tasks. But do you have any idea what is a reasonable number of tasks to have in work at any one time? The burndown chart that your tooling or your scrummaster makes is posted – isn’t it? Do you use it to understand the likelihood that your work for this sprint will be completed as planned? In every planning session you dutifully use Planning Poker for estimation. However, do you understand why using it is important and why this type of estimation actually works?

A professional mechanic understands more than just how to use the tools that are in the garage. The professional mechanic also understands how the tools work and why. It’s great that your team has learned many of the various agile techniques. But if you haven’t learned why those techniques work, you risk using them improperly, putting your success in jeopardy.

There is an old story about a young woman who is preparing her first holiday feast for the whole family, which included making a delicious glazed ham. She remembered, as a young girl, watching her mother cook. She called her mother to ask her why, when she cooked ham, she cut off the end of the ham before cooking. Her mother answered “Because my mother did it that way.” Now more curious, they called the grandmother and asked why she cut of the end of the ham before cooking. Grandmother told them it was because her mother did it that way. They were very fortunate that their Great-Grandmother was still around, so they called her and asked why she cut of the end of the ham before cooking. Great-Grandmother’s answer was simple…her roasting pan was too small.

Do you know “the whys” behind the agile techniques you do?
Improving Your Software Processes and Practices
Agile Adoption and Transformation