![]() This article was inspired by Retrospective anti-pattern: continuous improvement should not feel like constantly failing, posted at . a meeting held by a project team at the end of a project or process (often after a certain number of iterations) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects. Every once in a while, go out as a team and enjoy a nice retrospective lunch. Deriving hypotheses from analysis and coming up with experiments involves creativity, and it can be taxing. There are no "iteration police." Take breaks as needed.Ask how you are enabling the team's search for improvement, and be prepared to act on any feedback. ![]() By reflecting back on a specific project or time period, the team can focus on. ![]() This might seem a bit meta, but it works: Continually improving the retrospective is recursively improving as a team. Retrospective meetings are a great opportunity for a team to learn and grow. End each retrospective by asking for feedback on the retro itself.Retromat is a great free retrospective tool to help vary your methods. When we say retrospective, heres what we have in mind: a special meeting where the team gathers after completing an increment of work to inspect and adapt. If every time you do a retrospective you ask, “What worked, what didn’t work?” and then vote on the top item from either column, your team will quickly get bored. If you’re not analyzing how to improve, ( 5 Whys, force-field analysis, impact mapping, or fish-boning), you might be jumping to solutions too quickly.If the retrospective doesn’t make you feel excited about an experiment, maybe you shouldn’t try it in the next iteration.Thinking about a problem deeply instead of trying to solve it right away might be a better option. Amplify the good! Instead of focusing on what didn’t work well, why not begin the retro by having everyone mention one positive item first? Dont make it personal, dont take it personally Listen with an open mind Everyones experience is valid Set the time period youre discussing (last sprint.The result? You don’t get an experiment or a potential improvement to pull into the next iteration. There is no data gathering and research, no hypothesis, and very little deep thought. The anti-pattern is where retrospectives become dreaded sessions where we look back at the last iteration, make two columns-what worked and what didn’t work-and quickly come to some solution for the next iteration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |