Retrospectives with Easy Agile TeamRhythm

Purpose and objective of retrospectives

Retrospectives are a staple of many agile processes. The purpose is to encourage reflection, continuous improvement, and team growth. It enables the team to learn from past experiences, adapt their practices, and enhance their collaboration and performance for future sprints or iterations. The team should end the retrospective feeling positive, engaged and empowered to make changes and improvements based on the insights and discussions during the retrospective.

Key users (roles & responsibilities)

• The entire Agile team: anyone who is involved in designing, testing, or building should attend.They contribute their insights, experiences, and suggestions for improvement based on their involvement
• Scrum Master: It is their role to facilitate the retrospective and help the team identify improvement opportunities and prioritize action items.
• Product Owner and Product Manager: While the primary focus of the retrospective is on the development team, the Product Owner and/or manager may also be involved in the retrospective, especially when it comes to discussing collaboration, communication, or any areas where their input can contribute to the team's improvement.

Agile retrospectives with Easy Agile TeamRhythm

User goal

So that we can improve the way we work together, as an agile team we want to share and discuss our thoughts, feedback and learnings from the previous sprint/version, and draw conclusions that we can implement.

Scenario

The team meet for the Sprint 2 retrospective. The Scrum Master uses the timer to provision time for the team to comment and vote on items. The team add comments, up vote and downvote retro items, and then work through their feedback. At the end of the retro, they complete a mood survey.

• Start/stop timer

• Retro item comment added

• Retro up vote clicked

• Retro item category added

• Retro item description edited

• Retro mood changed