![]() As I mentioned earlier, agile retrospectives help regulate the crucial process of failing fast and singling out what no longer moves us forward. ![]() But focus too much on speeding ahead and, naturally, you forget to reflect. Inform: In part, agility is about speed.Given the chance to own their decisions, teammates are more likely to embrace than resist anything that needs to change–the very attitude agile teams need to thrive. Empower: Retros should foster a culture of ownership.Think of them as a team-building exercise and a way to get everyone excited about finding new solutions to old problems. Energize: Retros should be positive, supportive, rewarding experiences.But there’s even more potential than that. Why do retrospectives?Īt their core, agile retrospectives help us avoid the age-old trap of repeating the same thing and expecting different results. Bear with me, because they absolutely are. At this point, you might be wondering where you’ll find the time for agile retrospectives–or if they’re even worth your time. Retrospectives work best at set intervals.īut I know it’s just as difficult to justify spending more time in more meetings when you’re busy enough as it is. Without regularly checking in on how things are going and making small improvements, it’s pretty difficult to make big things happen. “ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” They’re also the last, but by no means the least, of the twelve principles of agile development: Agile retrospectives come at the end of the larger scrum process and inform the next sprint. First up in the inspect and adapt cycle, sprint planning is when the team picks items from product backlogs to address in an upcoming sprint. This isn’t to be confused with sprint planning. Through this analysis, agile retrospectives follow the principles of kaizen: finding ways to continually improve. They’re a great opportunity to pause, step outside the work bubble, and assess what’s working and what’s not. What is an agile retrospective?Īlso known as a sprint retrospective or sprint retro, agile retrospectives are meetings held to recap each iteration of an ongoing project. Anyone can benefit from the payoff.īy the end of this post, you’ll have a better idea of what that is, plus examples and tips to try in your first meeting. But in recent years, agile retrospectives have worked their way out of development and into all facets of the business, from marketing right up to management. Perhaps you’ve only heard these mentioned in a development context. If you find your company struggling to separate what should be scrapped from what’s worth pursuing, you might be skipping an important step in your agile journey: agile retrospectives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |