Monday 24 August 2009

Affinity Estimation-when there are a lot of stories to be estimated

I came across Rick Tonoli`s Blog and found a couple of very interesting articles. Still working my way through his postings, i'll praise him later in a separate article after covering his and other opinions on the topic of "affinity estimation". I didnt apply it myself, but it does sound like a good approach to get a high level estimation done without wasting too much time.

He is refering to Kane Mar's blog who in return references to Jukka Lindström who posted his comment here. I would love to test it as it sounds very intuitive. A might be more suitable for a pretty senior team, but then again, what isn't...

Here is Kane Mar's comment on it:
"We started by reading out each Story to the entire team. Lowell then asked us to arrange the stories horizontally on a wall in order of size, without talking. We placed the largest stories on the left and the smallest stories on the right. This only took a few minutes. We were then given a final opportunity to make adjustments to the ordering, again without talking.
 
...
Finally, “Affinity Estimating” helps make estimating a positive experience rather than a confrontational one. The next time you have a need to estimate a large number of User Stories, consider trying “Affinity Estimating."

Sounds like it could also be an interesting tool for team(member)s that struggle to speak their mind or or have problems with confrontations. Ball-parking new projects should/could be simpler as well.

You can find a more detailed description about how it works here.



Digg Technorati Delicious StumbleUpon Reddit BlinkList Furl Mixx Facebook Google Bookmark Yahoo

Google Analytics