We are currently using Scrum but lack a formal, structured event for reflecting and implementing improvements at scale. In the Scaled Agile Framework (SAFe), what is the structure and specific goal of the Inspect and Adapt (I&A) event that occurs at the end of every Program Increment (PI)? What are the three main parts of the I&A, and how do the resulting improvement items (like an Improvement Story) actually get prioritized and executed by the Agile Release Train (ART) to achieve Relentless Improvement and higher Business Agility?
3 answers
That makes the link between inspection and action clear. Given that the I&A is a large event for the entire Agile Release Train, how does the Release Train Engineer (RTE) ensure that the Problem Solving Workshop focuses on the systemic issues (like cross-team dependency management or environment stability) rather than just local team-level problems that should have been solved in a regular iteration retrospective? How do they ensure the workshop drives Relentless Improvement for the whole ART?
The Inspect and Adapt (I&A) event is SAFe's formal, large-group retrospective held at the end of every Program Increment (PI). Its primary goal is Relentless Improvement of the solution, the process, and the entire Agile Release Train (ART). The I&A has three main parts: 1) The PI System Demo, where the integrated system increment is shown to all stakeholders; 2) Quantitative and qualitative measurement, where flow metrics (like predictability and velocity) are reviewed; and 3) The Problem Solving Workshop, which is a structured activity to identify root causes of the biggest problems and propose corrective actions. The actions identified are often captured as Improvement Stories or Enabler Features which are then fed back into the Program Backlog and prioritized alongside new business work, ensuring improvement is treated as a priority, not an afterthought.
The Inspect and Adapt (I&A) event concludes every Program Increment (PI) to drive Continuous Improvement and Relentless Improvement. It consists of the PI System Demo, metric review, and the Problem Solving Workshop to identify root causes. Improvement actions are added to the Program Backlog as prioritized work.
The use of the Problem Solving Workshop to create tangible, prioritized Improvement Stories is the most valuable part. It ensures that the desire for improvement translates into actual, funded work that the Agile Release Train executes, preventing process stagnation.
Jeffrey, the RTE is responsible for facilitating the Problem Solving Workshop to focus specifically on the top 1-3 problems impacting the entire ART's flow metrics or predictability, often identified from the quantitative review. They use structured root-cause analysis (like the '5 Whys') to ensure the identified problem is systemic. The resulting Improvement Stories must benefit multiple teams or the entire train, keeping the focus on process improvements that contribute to overall Business Agility and better Continuous Improvement at scale.