Planning Poker uses cards to define each member's opinion and then reach a general consensus.
Planning Poker is applied during the planning meeting prior to each Sprint. During this meeting, known as the Sprint Planning Meeting, all team members will meet with the product owner and the Scrum Master.
This is the step by step on how Planning Poker works.
1. Design or define the planning poker cards
Planning Poker cards can be designed specifically for the estimation meeting or can be taken from an existing deck, as long as they can cover the necessary numbering.
The cards must be in a Fibonacci scale or in duplicate values. Some teams also add the 'question mark' and 'infinity' cards.
The question means that the team member does not have enough information to make an estimate, in which case it should be explained again, and the use of documents to illustrate the tasks again should be considered.
Infinity indicates that the task will not be germany telegram data completed in that Sprint, and that member believes more tasks will be needed.
2. Define the units to be estimated with Planning Poker
Part of the pre-work is defining the requirements to be estimated in that Sprint. You should ask yourself what the values on the cards will represent. These can be units of time, such as weeks or months, or scales of difficulty (Story Points).
3. The cards are dealt
Each member of the Sprint Planning team receives a deck of cards with the same numbers, because the goal is for all participants to reach a consensus number for each story.
4. Sharing the Sprint backlog
Prior to estimating, the Product Owner presents the set of features he or she would like to see completed in the Sprint, this breakdown is known as the Sprint Backlogs . It involves reading out loud and presenting these tasks.
