Traditional SDLCs say how interactions within a team and between teams should happen; a prescription that doesn't always fit or isn't followed consistently. Rachel Davies explains how retrospectives allow teams to improve their processes by reviewing past events and brainstorming new ideas, and shows how to facilitate a retrospective for your team.
Agile relies heavily on discipline, rather than genius. We're told that average teams, even in the early stages, can achieve dramatic performance improvement if they are disciplined. As we do these things, the effects of our words and actions actively create, and re-create over time, the environment in which our teams and projects operate - for good or ill.
Project retrospectives help teams examine what went right and what went wrong on a project. Traditionally held at the end of a project, they're actually too late to help - no wonder we call them "post-mortems". Agile teams need retrospectives that are iterative and incremental, to find problems and design solutions to help teams improve early on, when improvement yields the most benefit.
David Spann introduces Jean Tabaka's book, in which she shares stories and facilitation techniques to make teams and entire organizations effective, and provides templates to get them started.