The reason of iteration planning is for the team to finish the set of top-ranked product backlog items. This commitment is time boxed based on the length of iteration and team velocity.
Scrum Master − The scrum master acts as a facilitator for the agile delivery team.
Product Owner − The product owner deals with the detailed view of the product backlog and their acknowledgment criteria.
Agile Team − Agile delivery characterizes their assignments and sets the effort estimates required to satisfy the dedication.
Following are the steps associated in iteration planning −
An agile team calculates velocity dependent on past iterations. Velocity is an average number of units required to complete user stories in an iteration. For example, if a team took 12, 14, 10 story points in each iteration for the last three iterations, the team can take 12 as velocity for the next iteration.
Planned velocity tells the team how many user stories can be finished in the current iteration. If the team quickly finishes the tasks assigned, then more user stories can be pulled in. Otherwise, stories can be moved out too to the following iteration.
The capacity of a team is derived from the following three facts −
Suppose a team has 5 members, committed to work full time (8 hours a day) on a project and no one is on leave during an iteration, then the task capacity for a two-week iteration will be −