Chapter 22. The retrospective: working together to improve
Note
Insanity: Doing the same thing over and over again and expecting different results. | ||
| --Albert Einstein | ||
All agile methods, whether Scrum, Extreme Programming (XP), or custom, support stopping to reflect on the process on a regular basis. A project retrospective normalizes the team on the issues encountered and provides an opportunity for improvement, which everyone desires.
The inherent flaw with retrospectives and postmortems is they often turn into complaint sessions, and participants leave without a clear plan of attack. This chapter provides a process to eliminate these problems.
First, you'll give participants time to reflect on the project before the retrospective meeting. Second, ...
Get Becoming Agile now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
