![]() Keep: Things that have become essential to the process and delivery for upcoming Sprints.Add: Things to add or replace to meet the needs of team members.Drop: Things to remove completely from previous Sprints because it’s damaging or distracting to the team’s work and productivity.Team members get hyper-focused on processes, Agile tools, and resources so it’s best after they’ve worked through multiple Sprints. The DAKI (Drop, Add, Keep, Improve) Sprint Retrospective is a powerful model for Agile teams to get detailed takeaways in their retros. Lead the discussion starting with a certain column or urgent item.Ask each team member to contribute at least one item in each column focusing on the emotional journey of the previous Sprint.Add a few colored sticky note placeholders to represent an item for its respective column (Glad=Green, Sad=Blue, Mad=Orange).Separate your digital board into three columns and label them Glad, Sad, and Mad.What monotonous tasks are slowing you down?.Is a person overwhelmed by one or more steps in the workflow?.Do you feel more or less prepared to get started on work after planning meetings?.What are actionable ways processes can be adjusted for a frictionless experience?.These types of questions give insight into internal or external sources affecting the team. Scrum Masters and agile leaders are responsible for removing barriers to increase productivity. The Mad Sad Glad Sprint Retrospective explores the process blockers, stressors, and overall team morale in the way they worked individually and together in the previous Sprint. We encourage you to test a few formats to find what works best for your team’s DNA and meeting culture. We’ll walk through how to use each model through the lens of a remote team using a digital collaboration tool to perform the Scrum retrospective. The examples are for both novice and experienced Agile teams. To highlight any processes, tools, or people that made completing tasks and meeting deadlines easier To facilitate an activity-based retro for onboarding or general team building To dedicate a shared space to publicly celebrate one another To customize its format for any situation Good and bad experiences with current processes To expedite the top-of-mind discussion points after a Sprint To reflect after a difficult or long Sprint project To record insights and assign action itemsĭeep reflection on individual and team success To understand the stressors and overall team dynamic ![]() Sprint retrospective examples describing their main focus and best use case Sprint Retrospective Example Learn more about the Sprint Review meeting! The Sprint Retrospective happens after a Sprint is completed to share what worked, what didn’t work, and what could be improved so the team makes the right adjustments for future Sprints. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |