Posts Tagged ‘backlog’


Agile Heresy

January 2, 2012

 Those who do the work are the best people to estimate what it takes to perform the work.  Makes sense.  Sounds reasonable.  The problem with such a definitive statement is the subjective word “best”.  Most of us read “best qualified” into that statement.  But what if the “best” person to do the estimation, won’t?  Have you ever worked with people on an agile team who don’t want to contribute to the backlog item estimation activity?  Sometimes a rigid corporate culture causes people who are, or perceive themselves to be “lower on the food chain” to say little and thereby avoid perceived conflict or anger of a more senior person.  Sometimes it’s a cultural behavior.  Sometimes fear.  Sometimes shyness.

 One successful team that I coached found a workable solution.  They selected a small sub-team from the more senior people on the team.  This sub-team did the estimation for the whole team.  It worked well and they have been very successful.

 But do you think this is agile heresy?  If so, how would you otherwise fix such a situation?

 Paraphrasing that old adage: You can lead a horse to water, but you can’t make him estimate.


Backlog vs. Fatlog

February 2, 2010

I recently spoke with a CIO whose teams were trying to become more agile, but were having significant problems with the basic question of when they were “done”. There are many reasons that this deceptively simple question still eludes people. John Sonmez recently wrote about one reason – the Fatlog.

Do you use a bulldozer to build your sprint backlog – just scooping up everything in sight and building large piles of work items? Does your sprint have an objective or is it just a heap of stuff? How about doing just a little bit of analysis to make your sprint content cohesive? Or as John suggests, just simply divide up your Fatlog into smaller pieces.

So often the most challenging problems can be resolved with very basic, pragmatic techniques. What do you do to organize your sprint backlogs? Enjoy John’s article.