AgileInPractice

AgileInPractice

Agile - sharing experience

The idea with the blog is to share experience about Agile in practice, I have been facilitating CoP (Community of Practice) with Scrum Masters, Product Owners, Team members etc. since 2010 with the purpose of sharing learnings from team to team...

“Learn from the mistakes of others-you can never live long enough to make them all yourself.” quote from John Luther

Purpose of poker planning

Poker planningPosted by Rune Hvalsøe Fri, November 23, 2012 21:53:40

I remeber that I asked a team about the purpose of "Poker planning", one of the team members answered, I believe that he thought it was a trick question, i.e. his answer was "to assign story points to stories"...

The answer is hower not the real purpose of Poker planning, the real value in poker planning is to ensure that each team member (including PO) have the same understanding of each story and know the scope of it; when the team members estimate the story, they often show that there is a gab in the understanding of the story and there is a valuable discussion afterwards, example is when you have a story where you on a web-page want to save some information and use it again, you may have someone estimating 1 point and someone saying that it is 20 points, each are perfectly correct according to their understanding. The person with 1 point will create a file (cookie) where you temporary save the information, where the member guessing on 20 point want to create a database on the server with a complex and very scalable system - both could be right, but the PO and the team have to discuss and agree on what they want to do...

Another value is that the PO gets information about the size of the stories, a story should never be so big that you cannot implement it in one sprint, if the PO find that one story is so big, the story have to be broken down to smaller stories.

One could argue that stories with very good DoD (Definition of Done) will never have this kind of miss-understanding; I have however only seen very few DoD which are so good that the team will not have a different understanding, and there could still be a clearification about what the PO want to achieve.

  • Comments(0)//agileblog.danskerne.se/#post0