Agile expert Doug Rose outlines the steps for an agile retrospective. Use them to help the team continuously improve, apply lessons learned, and embrace an agile mindset.
- Many teams work hard, but they don't have any way to improve. Working harder is great, but you'll gain much more productivity by improving how you work. That's why the end of every sprint agile teams have a retrospective meeting. If you think about it, working harder without process improvement is like trying to keep a leaky boat afloat by rowing faster. In this course, you'll see how to help your team identity those leaks and start making real fixes. First, we'll set up your retrospective so that it's comfortable and productive.
Then you'll see how to gather insights with a starfish diagram or pancake retrospective. Finally, we'll see how to gather these insights and assign action items to help the team continuously improve. This course is the final course in the Agile at Work series. This series is designed to help your team increase the pace and quality of its work. If you're new to Agile or not familiar with some of the terms, then you may want to watch this series from the very beginning. I hope you enjoy this final course in the series, Getting Better with Agile Retrospectives.
Watch and learn agile project management techniques to assess your project today, and get back on track for tomorrow. Find more courses on agile project management in the Agile at Work series on Doug's author page.
- Five phases of retrospectives
- Choosing an ideal meeting space
- Identifying issues and improvements
- Working with a distributed team
- Encouraging discussions
- Setting goals using SMART criteria
- Asking good questions
- Making team decisions
- Closing out an agile retrospective