The document outlines the 'Inspect and Adapt' workshop within the Scaled Agile Framework, where teams evaluate a demonstrated solution and identify areas for improvement. It describes four key events in the process: a system demo, evaluation of program increment performance, a retrospective to prioritize problems, and a problem-solving workshop for larger issues. The overall goal is continuous improvement to enhance future program increments.

1. Kendis
Inspect and Adapt in the
Scaled Agile Framework

2. Inspect and Adapt is a problem solving workshop
where the solution created by the Agile Release Train
or the Solution Train is demonstrated and evaluated
by the teams.

3. It is an event where the teams identify the pain
points or any aspects of the solution that can be
improved for the upcoming program increments thus
guaranteeing continuous improvement.

4. The
Participants Program Stakeholders
Product Management
Business Owners
1
2
3
Agile Teams
4
5
6
Release Train Engineers
System and Solution
Architect

5. The Inspect and Adapt event consists
of 4 key events

6. System Demo
1
The solution is demonstrated with proper staging
Led by the product management and facilitated by the Release
Train Engineer
The performance of the Program Increment is evaluated by the
Program Increment Performance Report
This report has the objectives that had to be achieved in the
Program Increment
Business owners assign a value to each objective
The values then can be used to calculate the Achievement
Percentage

7. Quantitative Measure
2
The Program Predictability Matrix is used to convey the
percentage of what was actually delivered
By using the achievement percentage for each objective, a graph
is plotted
The trend of the achievement percentage is compared with the
trend of the original planned value
This report has the objectives that had to be achieved in the
Program Increment
The value has to be between 80-100% to ensure optimum flow

8. Retrospective
3
Problems of the Program Increment are addressed, selected by
the teams and prioritized
A time limit is set for discussing the problems

9. Problem Solving Workshop
4
If the problems that need to be discussed in the retrospective
exceed the set time limit, then a Problem solving workshop is held
Led by the Release Train Engineer
Using Root Cause Analysis Method to handle large problems
Problem is stated and Root Cause Analysis is applied
With the problem identified, a solution is thought of by brain
storming
Once a solution is reached, items in the backlog are updated and
improved for the next Program Increment

10. "If you always do what you’ve
always done, you’ll always be
where you’ve
always been." T.D. Jakes

11. For more information
Contact us at: team@kendis.io
Or visit us: www.kendis.io