![]() What is the team member’s contribution that helped you accomplish it?.Which strong points of your team that made it happen?.Which strong point in you makes it happen?.Which training, skill, or knowledge contributed to the difference?.What did we do differently to make it a success?.The possible questions that can be asked, to understanding the reason behind a success in the iteration by asking ourselves what went well to acknowledge all the good things that have happened. What should we do differently in the next sprint?.Whether any team members are located remotelyĭuring the Sprint Retrospective, the team discusses:. ![]() The exact length of the sprint retrospective is influenced by factors such as: The following table illustrates this rule: Total Sprint Duration The thumb rule for the length of a sprint retrospective meeting is that it usually take no more than 45 minutes per week of sprint duration. Stages of Sprint Retrospective Length of Sprint Retrospective Meeting Close the retrospective – Clarify follow-up Appreciations Clear end How could the retrospectives improve?.Decide what to do – Pick a few issues to work on and create concrete action plans of how you’ll address them.Generate insight – Why did things happen the way they did? Identify patterns See the big picture.Gather data – Help everyone remember Create a shared pool of information (everybody sees the world differently).Set the stage – Set the goal Give people time to “arrive” and get into the right mood.Usually retrospectives are a little more sophisticated than that. 5 Steps for Conducting Sprint Retrospective Meeting Sprint CycleĪt the end of the Sprint a Sprint Review Meeting is conducted to allow the Scrum Product Owner to check if all of the committed items are complete and implemented correctly for deployment.Ī Sprint Retrospective Meeting is then conducted to check and improve the project execution processes: What was good during the Sprint, what should continue as it is and what should be improved for the next sprints. The combination of these two meeting are also defined as Sprint Planning Meeting. It features scrum tools like user story map, product backlog management, sprint backlog management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint retrospective tool, burndown, impediment, stakeholder and team management.Įach Sprint start with two planning sessions to define the content of the Sprint: the “What” – Part one of Sprint Planning Meeting and the “How” – Part II of the Sprint Planning Meeting. A powerful scrum software that supports scrum project management.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |