Which statement is true about Iteration Planning
A) It is required for every iteration to enable fast learning cycles
B) It is only required for every third iteration
C) It is required for component teams but may not be required for feature teams that have no dependencies on other teams
D) It is not required for teams that consistently meet their PI Objectives
Answer Explanation for Question: Which statement is true about Iteration Planning
During iteration planning, all team members decide how much work they will deliver from the Team Backlog in the upcoming iteration. Each Iteration Goal is a commitment made by the team.In order to manage software development more efficiently, iteration planning is critical from the outset of the scrum process. Program increment (PI) planning partially completes the team backlog. After the sprint backlog is matched with the tasks, iteration planning is done for one successful sprint.
Iteration planning is intended to organize the work and define a realistic scope for the iteration. Every Agile Team decides what stories will be included in the upcoming iteration (the iteration backlog) before combining them into a set of iteration goals. Backlogs and goals for iterations are determined by the team’s capacity and take into consideration each story’s complexity, size, and dependencies on other stories and teams. Teams commit to iteration goals at the end of planning, and adjust stories as needed to meet the larger purpose. The result is that management does not interfere or change the scope of the project, allowing the team to stay focused.
During iteration planning, work is organized and a realistic scope for the iteration is defined. Agile Teams agree on an iteration backlog of stories for the upcoming iteration (the iteration backlog) and summarize the backlog into iteration goals. Based on the team’s capacity, the iteration backlog and goals reflect each story’s complexity, size, and dependencies on other stories and other teams. Team members commit to the goals of the iteration at the end of planning and adjust stories as necessary to accomplish the larger purpose. The team is able to remain focused by the management not interfering nor adjusting the scope of the iteration.
How long is iteration planning?
An iteration planning meeting is called at the beginning of each iteration to produce that iteration’s plan of programming tasks. Each iteration is 1 to 3 weeks long. User stories are chosen for this iteration by the customer from the release plan in order of the most valuable to the customer first.
What are inputs for the iteration planning?
- Team and Program PI Objectives, developed during PI planning
- In the team’s PI plan, there is a list of stories that have been identified during PI planning and have been prospectively assigned to iterations
- Additionally, additional stories have arose from local contexts, including items such as defects and Refactorings, in addition to new stories that have arose since the planning session to support Feature delivery
- Any stories that did not achieve completion (e.g., did not meet the ‘definition of done’) in the prior iteration should be included in the feedback.
- Feedback from the system demo
When should iteration planning take place?
This is done when the product owner establishes the program increments and then breaks down the requirements into user stories for the resources to work on.