Sprint Retrospective

• When: Retro occurs at the end of each sprint.

• Why have a retro: For the team to reflect on its own
processes, inspect their behavior, and take action to
adapt it for future sprints.
• Who leads the meeting: A dedicated Scrum Master
with the psychological safety to ensure the discussion
doesn't avoid uncomfortable issues or deteriorate into
blaming and hostility.
• Where: A dedicated retrospective board
• What are the long-term benefits: Retro can often
expose organizational impediments. Once these are
resolved within the team's immediate influence, that
influence can be expanded in order to chip away at the
source of the problem.
What Impedes a productive Retro?

1. The presence of people who conduct performance reviews.

• This will prevent team members from sharing with full transparency and will
increase the likelihood that uncomfortable issues will be avoided.
2. The human tendency to jump to conclusions and propose actions
too quickly.
• Slow the problem-solving process down by breaking it into steps:
• Set the Stage
• Gather data
• Generate Insights
• Decided what to do
• Close the Retrospective
 Creating a Sprint Retrospective
• Azure DevOps
• https://marklowg.medium.com/creating-your-first-sprint-retrospective-with-azure-devops-41362e4
bac3b

• Confluence
• https://barbri.atlassian.net/wiki/spaces/TECHDEV/pages/2406088705/Retrospectives
• Reetro
• https://www.reetro.app/board/6269510b29a62e0017a58623/62695149987f810017a8ce2f
• MetroRetro
• https://metroretro.io/board/LB8UQ6DCJ61Z#
• GoRetro
• https://app.goretro.ai/dashboard/public-board/kLva3juwE5q6GUyC4YKXuEy2yFUKpBJ3HLJ0xulk7X
u004BTvG