As per Scrum Guide, the purpose of the Sprint Retrospective
is to:
- Inspect how the last Sprint went with regards to people, relationships, process, and tools;
- Identify and order the major items that went well and potential improvements; and,
- Create a plan for implementing improvements to the way the Scrum Team does its work.
But Scrum Guide is silent about on How?
The question of how become more important as scale of Scrum
Agile increases in an enterprise.
To answer one part of How – “How and why something worked
well?” Fu Pan might be an answer.
Fu Pan concept has its origin in Lenovo and widely supported
by its chairman Liu Chuanzhi. The idea is to intentionally slow down and
analyze events - both successes and failures - in order to learn from them and
move ahead at a faster pace.
Goal: What had you originally set out to do?
Measure results: What
have you achieved and is it what you set out to do?
Brainstorm: Find
outcomes, highlights and lowlights of the final result
Analysis: Get to
the root cause of why the outcomes were achieved
Insights: Learnings
based on the analysis. Determine what to replicate in the future, what behaviors
to start, stop and continue
I am planning to use Fu Pan during Retrospective and also at
Program level.
Any ideas, pointers?
Reference:
Posts
