Iteration 0 is typically done before the start of a new program or major upgrade to an existing product line, and is done in preparation of the first release/quarterly planning. Iteration 0 is typically 1 week for a 3 month program. So, for example, if your program is 1 year, Iteration 0 would be 1 month. Iteration 0 is only applicable for the first Big Room planning for a new launch. The Program and Team Stakeholders are involved with Iteration 0.


  • Identify the Value Stream for delivering product to market or to the client.
  • Agile Product Roadmap with tentative releases.
  • Discuss and finalize logistics (e.g. if people will collocate, getting dedicated Scrum/Kanban team rooms, reconfigure team area to be more open space, etc.).
  • Discuss and setup initial infrastructure requirements. This can be Test environments, CI Build server, Development environment, etc.
  • Feature Backlog of Business and Technical Features.
  • Create supporting design/UI specs, if necessary, to support the Business/Technical Features and Stories in the first two sprints.
  • Ensure the initial Team Backlogs has high level User Stories by the Backlog Owners for the first one to two sprints.
  • Design the Sprints and cadence. The Agile Program Manager would be responsible to lead this effort with the Scrum Masters, because we need a common cadence for all Scrum Teams. Design happens once and then you repeat the design for every Sprint. For example, when designing sprints for multiple teams, all scrum teams should start and finish their sprints on the same day and each team should schedule their Sprint Planning, Standups, Backlog Grooming, Reviews, and Retrospectives to occur on the same cadence.
  • Discuss and agree on the Definition of Done (DoD) for the team, integration, and release levels.
  • Assign the roles.
  • Discuss initial agile architecture, as opposed to other architectures that require an extensive up-front design. Agile architecture can scale as new features are added.
  • Initial ramping up on the technologies and code base.
  • Finalize program and team agreements (Sprint Planning, Standups, Backlog Grooming, Sprint Review and Retrospective, Quarterly Planning, etc.).
  • Anything else that is essential to get the teams moving forward!