Qu’est-ce que le planning Poker?
This is a requirement with risk and may require significant time to overcome teething issues. Planning Poker can be used with story points, ideal days, or any other estimating unit. Over a million developers have joined DZone. But as per my view, after some sprints, we normally stopping following this process i. Hi Avienaash, At times there are disagreements within the team in the estimation meetings and the pattern usually is that a person less comfortable with the product or knows less tends to estimate higher to accommodate for any surprises versus a person who knows the product better or is a subject matter expert. To make this easier, this module shows you:. Story points can also help to highlight an over utilization of the team if it occurs.
Sailing the Oceans of Corporate Agility
A thing of simple beauty. Used this with a team who were struggling with an unsized backlog but a hard delivery date. The team had never used planning poker before and this technique worked beautifully.
Great to hear from you: And I agree most teams do get initially hung up on the numbers. Thanks I will use this often. However, we are a geographically distributed team. Could you point me to any online tools which support this. We shared what we were doing live online.
From a quick search just now, it looks like Rally users can get this as an add-on at http: I wondered about doing something stand-alone however the challenge with writing a stand-alone app would be writing the story card data in the first place — this is dependent on what format your data is already in. What other electronic tools are you using at the moment for managing stories?
This is an online real-time scrum board where you can define your own swimlanes etc. No complex business rules — just straight board.
I tried this out about a year ago and have been using it ever since. I use it on different projects, with different customers and it always works like a charm.
Sizing stories within an hour is perfectly doable. We did around in about 90 minutes. I manage a virtual team remotely scattered and sizing-estimation can be drudgery at times…. Voting is repeated till the whole team reached consensus about the accurate estimation. Planning poker works well when you have to estimate a relative small number of items max 10 in a small team people.
More on planning poker via this link. This is a perfect technique for estimating a large backlog of relative large items. Especially when you have several concurrent scrum teams working on the same product. Items are estimated into t-shirt sizes: The decision about the size is based on an open and mutual collaborative discussion. This method is an informal and quick way to get an rough feeling about the total size of your backlog. More about T-shirt size estimation is here.
When you are faced with a relative small set of items and in need of a super simple and effective technique to estimate you can use Dot Voting. This method has originated form decision making and you can use it for estimating. Each person gets a small number of small stickers and can choose to vote for the individual items.
The more dots is an indicator of a bigger size. Works well in both small and large group. You have to limit the number of estimated items. More on dot voting here. Much faster than planning poker is the Bucket System. This system is a good alternative when estimating a large number of items with a large group of participants. Create several buckets in the sequence of planning poker. Buckets are usually different sheets of brown paper where you can place the sticky note with the item. But you can also use actual baskets to limit discussion about already processed items.
More on the bucket method here. The team is being asked to place the items in one of these categories. The first step is to categorize the obvious items in the two extreme categories.
Next the group can discuss the more complex items. This is actually a simplification of the bucket system. The system is especially good to use in smaller groups with comparable items. Next you can assign sizes to these 3 categories. This method is based on finding similarities in the estimated items.
The team is asked to group them together. Best way is to execute this is a visual way and order them form small groups to large. It works best with a small group of people and a relative small number of items.
You can assign estimation numbers to the different groups. This is an exercise where you get an accurate image on the relative size of items. This works best in a small group of expert. All items are placed in random order on a scale label ranging from low to high.