Inspect and Adapt (I&A)
What is Inspect and Adapt (I&A)?
Inspect and Adapt (I&A) is the SAFe event at the end of each Program Increment where an Agile Release Train demos its work, reviews its metrics and runs a workshop to fix its biggest problems.
Updated November 2026 · 2 min read
The three parts of Inspect and Adapt
I&A takes half a day to a day and involves everyone on the Agile Release Train (ART), plus business owners and other stakeholders. It is the train-level equivalent of a team's sprint retrospective, but it also looks at the product and the numbers.
| Part | What happens | Output |
| PI system demo | The train shows the integrated solution built during the increment | Business owner feedback; scores for actual business value |
| Quantitative and qualitative measurement | The RTE presents metrics, including planned vs actual business value and flow measures | A shared view of how the increment went |
| Problem-solving workshop | Teams pick the biggest problems, find root causes and propose fixes | Improvement items for the next PI Planning |
How the problem-solving workshop runs
The workshop follows a familiar root-cause pattern:
- Agree the problem to solve, stated in specific, measurable terms
- Find root causes with a fishbone diagram and the "five whys"
- Vote on the most likely root cause, often using a Pareto analysis
- Restate the problem around that cause
- Brainstorm solutions
- Turn the best ideas into improvement backlog items for the next increment
This is the same logic as the PDCA cycle and kaizen: small, evidence-based changes, repeated every increment.
An example
At the end of an increment, a logistics train's metrics show it delivered 68% of the business value it planned. The demo goes well, but the workshop picks "late integration found defects in the final sprint" as the top problem. The fishbone points to one root cause: the shared test environment is only available two days a week. The improvement item, funded in the next PI Planning, is a second environment. Next increment, predictability rises to 84%.
The metrics reviewed
The core measure is ART predictability: the business value actually achieved against the value planned in the team PI objectives. SAFe suggests 80 to 100% as a healthy range. Trains also look at flow metrics such as flow velocity, flow time and flow load, plus quality and stability measures. Similar ideas appear outside SAFe as the say-do ratio.
I&A outside SAFe
The pattern works without SAFe. Any group of teams that plans together every quarter can end the quarter with the same three steps: show the integrated result to the people who asked for it, look honestly at planned versus delivered, and spend real time on one or two root causes. Organisations using big room planning or their own quarterly cycle often run exactly this under a different name, as a form of continuous improvement.
Keeping it useful
I&A loses value when it becomes a showcase with no hard conversation. Pick one or two problems and solve them properly rather than listing ten. Make sure improvement items actually get capacity in the next plan, and check at the following I&A whether they worked. Psychological safety matters: a blameless tone keeps people honest about what went wrong.
Frequently asked questions
How long does Inspect and Adapt take?
Typically three to four hours for an Agile Release Train, and sometimes a full day for a large or new train. The system demo takes about an hour, the metrics review 30 minutes or so, and the problem-solving workshop the remaining time. It is usually held during the innovation and planning iteration, just before the next PI Planning.
What is the difference between I&A and a sprint retrospective?
A sprint retrospective is held by one team every sprint and focuses on how that team works. Inspect and Adapt is held by the whole train once per increment. It covers the integrated product, train-level metrics such as predictability, and problems that cross teams, which no single team retrospective can solve.
Who attends Inspect and Adapt?
Everyone on the Agile Release Train: team members, Scrum Masters or team coaches, product owners, product management, system architects and the Release Train Engineer, who usually facilitates. Business owners attend to give feedback on the demo and score business value. Other stakeholders, such as shared services or customers, may join the demo.
Related terms
Agile Release Train (ART)
A long-lived team of agile teams that plans and delivers on one cadence.
Sprint Retrospective
The end-of-Sprint meeting where the team agrees how to work better.
PI Planning
The event where every team on a release train plans the next quarter together.
PI Objectives
What a team commits to achieve in an increment, scored for business value.