![]() Is a sprint retrospective meeting worth your team's time or will it end up being just another unnecessary interruption? That depends on how you run it. The unfortunate truth is, most meetings are a threat to your team's productivity rather than an opportunity to make progress. How to run a sprint retrospective meetingĪll meetings should be viewed with a dose of healthy skepticism. If done poorly, it can turn into a blame game or a just another repetitive, time-wasting meeting. If done well, a sprint retrospective meeting can highlight opportunities for meaningful sprint planning process improvements and move the team in the right direction. ![]() It is used to review and plan ways to improve the product, while the sprint retrospective is used to review and improve the processes used to create the product.Įssentially, the sprint review is a discussion about what the team is building, while the retrospective is focused on how they’re building it. Sprint retrospectives are often confused with sprint reviews, but they are not the same.Ī sprint review takes place before the sprint retrospective and is used as an opportunity to discuss what has been accomplished during the sprint and whether the sprint goal has been met. It works like a collective brain, allowing you to bring all your team's work together in one place and collaborate without the chaos of files and folders, context switching, or silos. ![]() Nuclino is a unified workspace where you can not only plan your sprints and run sprint retrospectives, but also build your internal knowledge base, collaborate on internal documentation, onboard new employees, take meeting minutes, communicate asynchronously, and more. Here's an example of what a documented sprint retrospective could look like in Nuclino: It's a practice that helps teams reflect on their way of working and continuously become better in what they do. To put it simply, a sprint retrospective should create a safe space for people to share their honest feedback on what's going well and what isn't, and to generate a discussion around what could be improved next time. Identify and order the major items that went well and potential improvements Ĭreate a plan for implementing improvements to the way the scrum team does its work. Inspect how the last sprint went with regards to people, relationships, process, and tools According to the Scrum Guide, written by the founders of Scrum Ken Schwaber and Jeff Sutherland, the purpose of a retrospective is to:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |