In this final course of the Agile at Work series, explore the singular value of conducting an agile retrospective at the conclusion of every sprint.
- 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 at 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 identify 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 the 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 the series from the very beginning. I hope you enjoy this final course in the series, Getting Better With Agile Retrospectives.
- 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