The retrospective takes place after the sprint review and before the next sprint planning session, and is the team’s regular opportunity to improve how it works. Use this approach after each sprint and at the end of the project to capture lessons learned from the entire project.
Schedule the retrospective after the sprint review and before planning the next sprint, so that responsibility rests with the project manager.
Adjust the meeting length to the duration of the sprint: typically 45 minutes for a one-week sprint, 1.5 hours for two weeks, 2.25 hours for three weeks, and 3 hours for one month.
Use the Retrospective extension in DevOps as a support tool to gather input from the team before and during the meeting.
Establish the goals for the meeting in advance—for example, improving stand-ups, communication with stakeholders, or operating rules.
Draw on everyone's experience and perspective from the sprint to create a shared pool of information.
Identify useful patterns in the information collected, and always ask why things happened the way they did.
Identify the problems and challenges the team needs to address, and create a concrete plan for how they can successfully tackle each one.
Summarize the meeting, thank the participants, and consider how future retrospectives can be improved.
Have each team member identify what went well during the sprint and what did not go according to plan—without looking for someone to blame.
Discuss what the team learned during the sprint that could improve the way they work.
Check whether the definition of “done” is still appropriate for the team, or whether it should be tightened as the team gains more experience.
At the end of the project, the knowledge gained by the project group is shared with all of ProsessPilotene as part of the final report.
Still et spørsmål eller del hva som hjalp deg.
Publisert 27.1.2026
ProsessPilotene er blant de første selskapene i Norge som er oppført på Microsoft FastTrack Portfolio Partners List - et kvalitetsstempel til leverandører som leverer komplekse Dynamics 365-prosjekter etter dokumentert beste praksis.
Les merHar du et spørsmål eller en erfaring å dele?
Bli den første som bidrar.
