Ideally, tasks related to process improvement accumulated from the team’s conversations during retrospectives will make their way into the team’s next sprint commitment. To make sure the team respects the retrospective and looks forward to the outcomes it can result in, facilitators have a responsibility to the team to ensure actionable next steps are articulated, assigned owners and supported over the course of the next team sprint. Without follow-up, the insights generated during a retrospective meeting can lose their value quickly after the team connects.
This approach gives team members a chance to feel connected to the retro, its structure and arrive prepared, instead of being caught off-guard. To make the best use of the scheduled time, team members might appreciate understanding the retrospective format as well as the focal topic, if such will be surfaced.
TEAM RETROSPECTIVE FULL
With calendars chock full of meetings, syncs, connects and check-ins, most team members benefit from receiving a short retro agenda before the event itself. There are a number of ways to ensure your teams feels prepared for upcoming retrospectives in their calendar. To make sure your team is excited for this meeting and you’re leading the team down the path of actionable takeaways, keep these following best practices at bay when you are planning or hosting your upcoming retrospectives. In order to keep your team retrospectives productive in the long-term, there are a couple of proven tactics you can use as a facilitator (but also as a team member).
Many of the best practices that governed successful team retrospectives got dropped along the way and, for many teams, retrospectives became just a slot in the calendar. However, somewhere down the line, as team retrospectives became a more and more intrinsic part of Agile processes, even outside of IT… they lost some of their charm. They became the forum through which team members could voice concerns, celebrate successes and propose ideas for future improvements. Retrospectives arrived on the scene to change all of that. In traditional ways of working, teams had, sadly, become accustomed to keeping up the pace of work and never stepping back to reflect on the way they were actually working together. When Agile ways of working first emerged in knowledge work, development teams were, honestly and truly, thrilled about hosting their recurring retrospective meetings.
0 kommentar(er)
