Iteration Area

The complete lifecycle of an Agile Iteration

Supports Teams to plan execute, monitor and review their work. It serves as the core cycle for delivering value incrementally through the 5 key events:

  • Iteration Planning: Define Goals, manage Stories Backlog and estimate Effort.
  • Daily Stand Up (DSU): Track progress, address blockers, stay aligned in real-time.
  • Backlog Refinement: Refine and prioritize Stories to prepare for upcoming iterations.
  • Iteration Review: Showcase completed work, gather feedback, validate deliverables.
  • Retrospective: Reflect on successes, challenges, improvements using actionable insights.
Iteration Planning - Sprint Started - Default View
Iteration Refinement

Iteration Refinement

Get ready… Set… Refined to go

Incorporate feedback and new insights into work items. Ensure Backlog items are well defined, prioritized and aligned with the project or product vision.

Frequency: Held during the Iteration exection.
Duration: Typically 2 hours

Iteration Planning

Best laid Iteration plans

Plan for how many Backlog Items the Agile Team can commit to delivering in the Iteration.
Create the Iteration Backlog with work items and define the acceptance criteria.
Define and summarize the Iteration Goals based on the planned work.

Frequency: Held at the start of each Iteration.
Duration: Varies depending on Iteration length but typically 2-4 hours for a 2 week iteration

Iteration Planning - Sprint Started - Default View
Velocity Tool - Daily Stand Up (DSU)

Daily Stand Up (DSU)

15′ daily alignment

Share each team member’s current progress. Identify and address short-term challenges, risks or blockers. Plan the teams work for the day by ensuring alignment to Iteration Goals.

Duration: Typically 15 minutes

Iteration Review

Inspect & Adapt following your work

Review with your team the Iteration Outcomes, including Iteration Goal completion, Definition of Done (DoD) and completed work items. Includes Iteration Burnup & Burn Down Reports which provide clear, data-driven insights into progress, helping teams stay on track & make informed decisions.

Frequency: Last day of the Iteration.
Duration: 1 hour per iteration week (up to 4 hours for a 4 week iteration)

Iteration Review with Burnup and Burn Down Reports
Iteration Retrospective

Iteration Retrospective

Time to improve, with Actions

Reflect on the Iteration regarding people, interactions, processes, tools and technical debt. Identify and prioritize the most impactful improvements to boost the team’s effectiveness. Ideally plan for 1-2 actions to address identified improvements promptly.

 

Frequency: Held on the last working day of the Iteration, following the Iteration Review.
Duration: 2 hours

Iteration Area Features

Simply getting stuff done, smarter never harder

Team Velocity in Story Points, Feature or User Story Quantities

Team Velocity

Automatically generated for you and viewable via Story Points, Features or User Stories.