next time. For a project that lasted a year, you'll want to spend more time. Short changing your retrospective means short changing your chance to do better next time. Improvement doesn't happen by hoping; teams need to dedicate time thinking and learning.
Successful organizations know how to evolve to meet ever-changing expectations, rather than holding onto what used to work. Becoming comfortable with change, learning how to try something new, and measuring how well it works are critical business skills. And retrospectives are a great way to learn those skills on a team level.
Pages
About the author
A regular StickyMinds.com and Better Software magazine contributor, Esther Derby is one of the rare breed of consultants who blends the technical issues and managerial issues with the people-side issues. She is well known for helping teams grow to new levels of productivity. Project retrospectives and project assessments are two of Esther's key practices that serve as effective tools to start a team's transformation. Recognized as one of the world's leaders in retrospective facilitation, she often receives requests asking her to work with struggling teams. Esther is one of the founders of the AYE Conference. She co-author of Agile Retrospectives: Making Good Teams Great. She has presented at STAREAST, STARWEST and the Better Software Conference & EXPO. You can read more of Esther's musings on the wonderful world of software at www.estherderby.com and on her weblog at www.estherderby.com/weblog/blogger.html. Her email is derby@estherderby.com.
