Learn what a retrospective is, how to run one, and the optimal retro structure with the Atlassian Agile Coach. Retrospectives are a time for your team to reflect on how things went during the last sprint and talk about ways you could improve the next one and are on of the most versatile scrum ceremonies.
This video goes into greater detail about retrospective’s four main purposes:
Evaluate how the last sprint went, specifically related to the team dynamic, processes, and even tools.
Create a shared understanding of the things that went well and things that didn’t.
Create a plan for improving the way your team works.
The retrospective occurs after the sprint review and before the next sprint planning meeting. It usually takes about 30 minutes per week of iteration, like 1 hour for a two-week sprint.
Every team member should attend the retrospective, with a facilitator leading the discussion. The facilitator can be the scrum master, the product owner, or it can rotate throughout the team. Feel free to pull in designers, marketers, and anyone else who contributed to the current sprint or iteration.
Watch our video to learn the 5 basic steps to running a retrospective.
1:19 5 steps to running a retrospective
1:30 How to prep for a retrospective
1:47 How to set the stage and establish the right meeting culture
2:46 What is crucial in the “what went well” discussion
3:54 What is key to the “what needs improvement” discussion.
Make sure to watch our full Agile Coach series for all things Scrum and subscribe to our channel to get the latest videos.
#YourAgileCoach
0 Comments