![]() Load up your toolbelt with the good stuff!ģ. Highlighting what works and what we want to continue to strengthen is as important as raising flags. Stop by the Gun Shop: Discuss the tools, techniques and processes that have proven to be useful for the team. It’s important to be honest here! Problems cannot be improved if they are not first named.Ģ. The Bestiary: Now is the moment to identify the enemies and challenges the team faced in the last Sprint. How to conduct the retrospective (5 steps):ġ. The team will need to discuss challenges encountered, the tools and processes that helped along the way, why some things did not happen as originally planned and of course, lessons learned for next time. The end of the world is nye, and the only way to survive is to fight off those pesky Zombies as a united group. Used as a Sprint retrospective activity, this exercise will help your team come to a general diagnosis of your last work cycle. This Sprint retrospective activity is a bit more complex but brings a high dose of creativity and energy to the table. The Zombie Apocalypse – for a fun and spooky Sprint retrospective! □ Learn more about the Rock Band retrospective idea here!Ģ. This is where your action items come in! Be sure to note them and assign owners for each item to ensure there’s accountability. The Setlist: Looking back on the performance overall, discuss how you can improve for the next Sprint. This will boost team morale and engagement.Ĥ. The Road Crew: Get human! Highlight who helped the group and be specific in how they made an impact. Everything leading up to the “big event” matters in making it successful, and there is always room to optimize.ģ. Backstage: What did you notice about what went on behind the scenes? For a band that might be equipment set up, and for your team, it might be team processes such as QA. Were goals reached, did everything go live on time, is the Sprint successfully done?Ģ. The Scene: describe how the band performed in the last “show” (your sprint). How to conduct the retrospective (4 steps):ġ. This exercise alone is sure to get people out of their shells, escaping the monotony of previous retros with an fun twist. Just like after any performance, the team needs to debrief! Give your team a band name (or even better, decide on one together) and dedicate roles to each member of the group. It’s also great for conducting events or project post-mortems. This retrospective idea is a perfect fit for agile teams working in sprints that hold recurring retros.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |