Teams: Iterations
The central entry point for understanding Iterations in LinearB. Learn what Iterations is, how teams use it during the sprint lifecycle, and where to go for deeper analysis and configuration.
Iterations is the primary sprint-level view in LinearB. It connects project management issues (Jira, Shortcut, or Azure Boards) with real Git activity (branches, pull requests, commits, merges, and releases) to help teams understand how work is planned, executed, and delivered.
This article serves as a starting point for the Iterations feature. From here, you can explore detailed views, metrics, alerts, and configuration guidance in the linked articles below.
Summary
- Iterations is a team-level sprint view in LinearB.
- It shows how planned work maps to actual Git execution.
- The feature supports current execution, retrospectives, and trend analysis.
- Each team has its own Iterations view based on connected boards and repositories.
What you can do with Iterations
Teams typically use Iterations to:
- Track progress and scope changes during an active sprint
- Review delivery results and planning accuracy after a sprint completes
- Analyze longer-term trends in execution, capacity, and investment
- Identify stalled work, review bottlenecks, and unlinked Git activity
Iterations views and related articles
The Iterations feature is documented across a small set of focused articles. Use the guide below to find the right place to go next.
| If you want to… | Read this article |
| Understand what Iterations shows and how to navigate it | Iterations Overview |
| Analyze completed sprints and delivery metrics | Iterations: Retroactive View |
| Understand alerts related to stalled reviews and pull requests | Iterations: Alerts |
| Ensure Git work is correctly linked to issues | Iterations: Naming Conventions |
How Iterations fits into the sprint lifecycle
- During the sprint – Use Iterations to monitor progress, added scope, review bottlenecks, and unlinked work.
- After the sprint – Review delivery outcomes, planning accuracy, and participation using retroactive metrics.
- Over time – Use trends and historical data to improve predictability and planning discipline.
Before you start
- Your team must be connected to a supported project management tool.
- Repositories must be connected so Git activity can be analyzed.
- Branches and pull requests should follow supported naming conventions.
How did we do?
Iterations: Naming Conventions
Understanding Iteration Alerts
