Project Management - Iteration Planning

Functions of Iteration Planning and how it contributes to the ITaaS model:  

  • Scrum Master: Facilitates the meeting.
  • Product Owner: Represents the detail of the product backlog items and their acceptance criteria.
  • Delivery team: Defines the tasks and efforts necessary to fulfill the commitment.

The purpose of the iteration planning meeting is for the team to commit to the completion of a set of the highest-ranked product backlog items. This commitment defines the iteration backlog and is based on the team’s velocity or capacity and the length of the iteration timeframe.

Iteration lengths typically range between 1 and 4 weeks. The team holds a planning meeting at the beginning of each iteration to break down each of the features scheduled for the iteration into specific technical tasks. Iteration planning meetings generally last from 2-4 hours. 

Part 1

At the beginning of the meeting, the highest priority features are typically selected from the release plan. If the iteration does have an overarching goal, then some lower priority features may be selected if they align with the goal.

Part 2

The team will break the features down into tasks. Developers then sign up for tasks and estimate them. Tasks typically range in size from 4 hours to 2 days, with most tasks capable of being delivered within a day.