Agile Retrospectives – Making Good Teams Great
A really informative Google Tech Talk by Diana Larsen and Esther Derby, authors of .
For some strange reason, the Agile Retrospective is the most commonly ‘skipped’ meeting in the Scrum Meeting Schedule.
The two main excuses I hear for not holding a Retrospective are:
- We didn’t have time – we had too much work to do
- Our team is fine – we don’t have any problems
For those of you who aren’t quite sure…Agile Retrospectives are really Important!
The Key Benefits of Holding Agile Retrospectives
- Improved Capacity
- Improved Quality
- Improved Capability
- Improved Productivity
- Higher Trust and Morale
Agile Retrospective Themes
- Learning from Experience
- Collaborative working
- Self-organisation
For those of you who haven’t got a copy of yet, I can highly recommend it. In the interim, take a look through an electronic copy of the book here.
This seminar elaborates upon the main topics discussed in the book. The Abstract is as follows:
Google Tech Talks January 25, 2007 – Agile Retrospectives
ABSTRACT: Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as “post-mortems”) are only performed at the end of the project — too late to help.
In organizations where teams develop using iterative, incremental methods, Agile retrospectives at the end of each iteration or increment stimulate continuous improvement throughout the project. Exceptional software process and project improvement grows out of solid data and good planning.
Esther Derby and Diana Larsen, authors of Agile Retrospectives: Making Good Teams Great, will introduce you to a framework for effective retrospectives, provide tips and pointers for sustaining interest in retrospectives throughout the project, and suggest ways to maintain the relevance of improvement to the work of your team
Enjoy!
See more Videos from Agile 101.net
Subscribe to the to be notified when I upload new Articles, Videos, Templates and Tips!
Hi Tara,
I agree that the Retrospective is an important part of the Sprint process. We work entirely with distributed teams, normally in different time zones, so quite often many of the retrospective actions revolve around improving the communications process (we can always do something better!). The team members love it because they get to see positive improvements; the client benefits and we all get to do achieve more (and our life is easier!).
Here’s a link to a blog I wrote about one of our live Retrospectives, which I throw in to the ring to share knowledge: http://blogs.sixninjas.com/paul15/?p=73.
PS – where do you find the time to write so many great blogs!
Regards,
Paul