The document discusses conducting retrospectives after projects to learn lessons for future projects. It emphasizes understanding what people knew at the time and not blaming others for past outcomes. Retrospectives involve discussing what went well, opportunities for improvement, and providing input to prioritize for future sprints. The goal is learning from experience to do better next time rather than assigning fault.

1. Learning from
the past for
the future

2. Disappointment
of
expectations

3. Blaming
stops Learning!

4. Timeline

5. “Regardless of what we discover, we
understand and truly believe: that
everyone did the best job they could,
given what they knew at the time, their
skills and abilities, the resources
available, and the situation at hand.”
-- Norman Kerth , Project Retrospectives

6. Timeline
Text
telling the tale

7. WHAT WENT WELL?

8. IMPROVE!

9. SCRUMMASTER
PRODUCT OWNER
TEAM MEMBER
ORGANISATION

10. SORTING
PRIORITIZING
RANKING

11. INPUT FOR SPRINT PLANNING