9/3/2023 0 Comments Sprint retrospective template![]() If you plan a face-to-face meeting, appoint a moderator to guide the conversation. If someone's work is going to be discussed, they should have the opportunity to express their perspective. Make sure every stakeholder contributes to the shared document. Team members might be more hesitant to bring up touchy subjects during a face-to-face meeting. ![]() There are several ways to encourage your team to be honest and direct in their retrospectives:Įncourage everyone to write up their thoughts in advance. No one likes to point fingers, but if problems go unmentioned, the team won't improve as quickly as they could. While it's easy to talk about what went well, what went wrong can be a sensitive topic. Establish a safe environment for feedback Instead, allocate more time to issues that actually require a discussion. Most information can be shared asynchronously and read by every member at their own pace – don't waste time reading it out loud for everyone to listen and nod. Some suggest setting the length of a retrospective meeting based on the length of the sprint – for example, a 30-minute retrospective after a weekly sprint and a 3-hour at the end of a monthly sprint.īut not every issue requires a synchronous discussion. If you do decide to shift to a synchronous discussion, don't take longer than you need. While you shouldn't default to a meeting for every sprint retrospective, in some cases it's the fastest way to work through a particularly tough problem. Keep face-to-face discussions short (and optional) They will have enough time to absorb each other's contributions and provide feedback.Įveryone will have an opportunity to contribute and document their experiences.Įvery sprint retrospective will be automatically documented in your internal wiki. Your team will be able to write down their retros in a thoughtful, structured manner. Instead, ask your team to write up their individual retrospectives and reserve real-time, face-to-face communication for particularly challenging issues.Īsynchronous sprint retrospective in Nuclino Most of the time, retrospectives can be done without meetings or video conferences. Synchronization is always a bottleneck when it comes to team communication, but the good news is – in most cases, it's not needed. Prepare asynchronouslyĪsynchronous retrospectives are not just for remote teams, and just because you can bring your entire team together in the same room at the same time, doesn't mean you should. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |