Planning in Agile

Basic idea

Planning in Agile is layered (portfolio → product → release → sprint → daily) and deferred — detailed planning happens at the start of each iteration, not up-front. Velocity (story points / sprint) drives forecasts.

Key formulas

Planning in Agile

Takes a signigicantly different flavour from traditional approaches.

Detailed planning is deferred until the start of the iteration.

Planning is based on light weight lists

Planning in SCRUM

LevelHorizonWhoFocusDeliverables
PortfolioYear or moreStakholders, product ownersManaing portfolio of projectsPortfolio backlog and collection of in-process products
ProductMonthsProduct owner, stakeholdersVisions and product evolutionProduct vision, high level features, roadmap
ReleaseThree to Nine monthsSCRUM team, Stakeholdersbalance customer value, constraintsRelease PLan
SprintWeek to MonthSCRUM teamWhat to deliver next sprintSprint goals backlog
DailyDailySCRUM Master, developement teamHow to complete commited featuresInspection of current progress

Fixed Date Release Planning

  1. Determine the number of sprints N by N := allocated_time/sprint_length
  2. Groom the product backlog by estimating and prioritizing stories
  3. Measure team velocity range, V_min, V_max
  4. Compute minimum and maximum story points based on velocity. SP_min := V_min * N, SP_max := V_max * N
  5. Draw lines through product backlog to show above

Fixed Scope Release Planning

  1. Groom the product backlog by creating, estimating and prioritizing and identify must-have stories.
  2. Determine total number of must have story points, SP_total.
  3. Measure team velocity, V_min, V_max.
  4. Compute minimum and maximum number of sprints, S_min := SP_total/V_max, S_max := SP_total/V_min
  5. Show burndown chart

Siblings