Contents
What is planning poker technique?
Planning Poker® is a consensus-based estimating technique. Agile teams around the world use Planning Poker to estimate their product backlogs. Planning Poker can be used with story points, ideal days, or any other estimating unit.
What is planning poker used for?
Planning Poker is a consensus-based technique for estimating, mostly used to estimate effort or relative size of user stories in Scrum. Planning Poker combines three estimation techniques − Wideband Delphi Technique, Analogous Estimation, and Estimation using WBS.
Which of the following is a characteristic of planning poker?
Planning poker is based on a list of features to be delivered, several copies of a deck of cards and optionally, an egg timer that can be used to limit time spent in discussion of each item. The feature list, often a list of user stories, describes some software that needs to be developed.
Which of the following is are the benefits of a planning poker session?
Planning Poker: Advantages and Disadvantages One clear advantage is that each team member can “voice” his or her estimates, which potentially encourages group discussion and collaboration. It also allows team members to feel more committed to the project plan.
Why do you need to use planning poker?
Planning poker can be a useful estimation technique for any team in any organization. But the approach works particularly well for smaller businesses and smaller teams. Larger organizations tend to have more substantial teams. The more people participate in a planning poker session, the longer it will take to reach a full consensus on each item.
How is planning poker used in sprint planning?
Planning poker is a collaborative way to get the whole team to help estimate the work involved in a user story. It drives consensus and tends to be more accurate. If you use Jira to conduct your sprint planning meetings, you already have a tool that organizes your user stories and product backlog.
How is planning poker used in agile development?
One agile estimation technique is planning poker. Agile development is a collaborative pursuit, and planning poker is a consensus-building exercise that gets your entire team involved in the estimation process. Software development teams use planning poker to assign effort (for example, story points or ideal days) to items in their product backlog.
When do you repeat the poker planning process?
The poker planning process is repeated until consensus is achieved or until the estimators decide that agile estimating and planning of a particular item needs to be deferred until additional information can be acquired.