It allows development teams to adapt Scrum to their particular circumstances. Its purpose is to:Įxamine how the just-completed sprint went as far as people, relationships, processes, and tools.ĭo the same with things that didn’t go well.Ĭreate a plan for implementing improvements to the way the Scrum team accomplishes its work.Įverything that affects how the Scrum team develops the product is open to discussion and improvement, including processes, tools, artifacts, environment, and so on. The Scrum sprint retrospective is a timeboxed meeting that takes place after the sprint review and before sprint planning. What is the purpose of a sprint retrospective?
Whitepaper: Agile Marketing for Creative Teams
Whitepaper: How to Become an Agile Agency So, it’s important for teams to consciously apply the lessons learned in each retrospective to upcoming sprints. That said, continuous improvement requires continuous effort. Since the early 1990s, Scrum has been used to develop:Ĭontinuous, iterative improvement is a core goal in Scrum product management, and the Scrum retrospective meeting is an official opportunity to achieve this at defined, consistent intervals-when teams have wrapped up a sprint and have a space to reflect and improve how things are done. The Agile sprint retrospective is an essential part of the Scrum framework for developing, delivering, and managing complex projects.
The sprint retrospective is a recurring meeting held at the end of a sprint used to discuss what went well during the previous sprint cycle and what can be improved for the next sprint.