Iterations Retroactive View

• The Retroactive View analyzes completed iterations only.
• It helps teams assess planning accuracy, capacity, and execution.
• Metrics differ slightly for Scrum and Kanban teams.
• Work is broken down by delivery outcome, investment type, and people effort.
• All issues link back to the original project management tool for deeper investigation.

1. Navigate to Teams → Iterations.
2. Use the iteration selector at the top of the page.
3. Select a completed sprint or week.

Planning accuracy measures how closely a team met its sprint commitments by comparing planned work with completed work.

Formula:

(Completed Issues ÷ Planned Issues) × 100

• < 70% – Possible over-commitment
• > 95% – Possible under-commitment

Capacity accuracy evaluates how much work the team completed relative to what was originally planned, including both planned and unplanned work.

This metric helps answer: Is the team taking on a reasonable workload?

Large variances may indicate:

• Unstable sprint scope
• Frequent mid-sprint interruptions
• Planning or backlog refinement gaps

For Kanban teams, LinearB replaces planning accuracy with velocity, which measures the number of issues completed per week.

• Average weekly completion rate
• Week-by-week breakdown of completed issues

Velocity helps teams track throughput trends and identify changes in execution efficiency over time.

The Delivery section categorizes work completed during the iteration:

• Completed – Planned work finished during the iteration
• Unplanned – Work added after the iteration started and completed within it
• Uncompleted – Planned work not finished by the end of the iteration
• Planned – Work added before or within 24 hours of iteration start

The Investment Profile shows how effort was distributed across work types, based on data from your project management tool (for example, Jira or Shortcut).

• New features
• Bugs
• Tasks
• Other configured issue types

This view helps teams understand whether execution aligns with product and engineering priorities.

People Effort measures the percentage of team members who actively contributed to completed work during the iteration.

Formula:

(Active Contributors ÷ Total Developers) × 100

• A contributor is considered active if they were assigned to an issue moved to Done.
• Low participation may indicate bottlenecks or uneven workload distribution.

A detailed list of all issues from the iteration appears on the right side of the page, grouped by delivery status.

• Click View more to expand any category.
• Click an issue to open it directly in Jira or Shortcut.

This enables teams to investigate delays, review scope changes, and prepare for retrospectives.

• Understanding Iteration Alerts
• Iterations Overview
• Connecting Your Project Management Tool