Contents
Is planning poker done during sprint planning?
Practically, then, this means that a team should estimate with Planning Poker at two different times. The second time a team should play Planning Poker is once per sprint. Some teams will do this as part of a regular product backlog grooming meeting, and I think that’s fine if the whole team participates in grooming.
When should you do poker planning?
When should we engage in Planning Poker? Most teams will hold a Planning Poker session shortly after an initial product backlog is written. This session (which may be spread over multiple days) is used to create initial estimates useful in scoping or sizing the project.
What is planning poker estimation technique used for agile planning?
Planning poker is also referred to as Agile Poker. It is a group estimation technique often used by agile teams to estimate the amount of effort or relative size of development goals in software development.
What is the planning poker technique 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.
How is planning poker used in sprint planning?
What is Planning Poker? Planning poker is a technique used to have a healthy discussion during sprint planning, it not only help to identify the problem by discussing deeply about the problem, it also enables team to reach to a comparative complexity which in turn provide a better estimate for the user story or issue in question.
What do you need to know about planning poker?
What is Planning Poker? Planning Poker is an agile estimating and planning technique that is consensus based. To start a poker planning session, the product owner or customer reads an agile user story or describes a feature to the estimators.
How is planning poker used in Agile planning?
Planning Poker is an agile estimating and planning technique that is consensus based. To start a poker planning session, the product owner or customer reads an agile user story or describes a feature to the estimators. Each estimator is holding a deck of Planning Poker cards with values like 0, 1, 2, 3, 5, 8, 13, 20,…
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.