Mural template. Instructions for running this Play. Prep 15 MIN. For help, see templates above For in-person teams, find a whiteboard or large paper, and set out Post-It notes and markers in a meeting room. Example: Confluence Running this Play remotely?
Set the stage 5 MIN. Tip: Create a safe space Define how the information will be discussed after the Play. What we did well 15 MIN. What we can do better 10 MIN. Tip: Make sure all are heard If the discussion is dominated by one or two people, the facilitator should step in and call on others before moving on.
Actions 10 MIN. Have everyone brainstorm actions that can be taken to improve problem areas, one idea per note.
Tip: Update your workflows If any of the action items have corresponding Jira issues, include links to them on the page so it's easy to see their status.
Challenge takeaways Are follow-up tasks being completed, or forgotten? Past two-months map Create a timeline spanning the past two months and have team members call out significant events. Dot Voting If you need to find consensus on the ideas that emerge, use dot voting to guide the conversation. See example. Still have questions? What should we start doing in the next sprint?
What should we stop doing in the next sprint? What can we do to improve productivity? When is a sprint retrospective meeting held? Who should attend sprint retrospective meetings? How long should a sprint retrospective take? Sprint review vs. How to run a sprint retrospective effectively Studies show that a major complaint of the Agile methodology is the perception that there are too many meetings.
Instead, boil the discussion down to the few questions we listed earlier: What do we need to stop doing? What do we need to start doing?
What do we need to continue doing? Keep it short Meetings take time, and time means money. Stay focused Your retrospective meeting should not be a social gathering.
Change things up a bit Meetings can be really boring, and bored team members are less likely to participate. Learn more. Sprint retrospective examples A simple way to get your team more involved is through the following activities. Glad, sad, mad Use this activity to let your team express their feelings so you can understand their emotional health. Starfish This exercise goes beyond the typical three retrospective questions "What went well? Less: Activities that have been included in the past, but do not add any overall improvements to the process.
More: Activities that the team should focus on or perform more often. Start: Activities and ideas that the team believes will add value and will improve current processes. Sailboat This is a simple exercise that helps you and your team define where they want to go and identify any problems you may run into. Start, stop, continue The start, stop, continue retrospective technique is the process by which sprint team members come up with actionable items that they can incorporate into the next sprint.
During a start, stop, continue retrospective, scrum masters ask their team to identify items to: Start : Activities that the team should implement during the next sprint. These can include ideas that would potentially address current problems. Stop: Activities that the team should stop. These items may be steps within your process that cause unnecessary work or bottlenecks.
Gain a deeper understanding of how your team truly felt about the previous sprint and design solutions that answer their biggest concerns, resulting in a smoother collaboration during the next sprint. Achieve very specific goals in each scrum retrospective meeting. Fresh Sprint Retrospective Formats for Improvement We know—agile retrospectives are supposed to be a somewhat freeform, team-driven exercise. Strengths-Based or Winning Streak Retros Build on Success A strengths-based scrum retrospective provides a different approach to a familiar concept.
A strength-based retrospective includes two steps: Discovering strengths. Defining the actions that use those strengths.
Then ask themselves a series of questions: How did we do it? What did we do to make it successful? What helped us do it? Which skills made the difference? How did being part of a team help to realize it? What did team members do to help you? Then ask these questions: How can you use your individual or team strengths to solve this problem?
What would you do more frequently that would help prevent the problem from happening again? Which actions can you take, which you are already capable of? Mountain Climber Retrospectives Give the Team a Metaphor to Work With The Mountain Climber retrospective technique portrays your sprint and project as a situation similar to a long mountain hike. Continue until everyone has met everyone else in the room. Basketball Retrospectives Help Identify Roles on the Team The basketball technique revolves around the idea that an agile team is not all that dissimilar from a team of basketball players.
Have them write out the tasks they performed during the last sprint. Do they point at recurring responsibilities? What position do those responsibilities add up to?
Ask that your team write down one shared team goal. One built a house of straw, one built a house of sticks, and one built a house of bricks. Ask your team to reflect on: What is at risk of breaking? What needs more work? What is rock solid? Try running a Three Little Pigs retrospective for free in Parabol 6.
Try asking your team: What energized you? What took up the correct amount of energy? What drained you? What's your energy level going into the next sprint? Follow up with the team by asking: What would help you re-energize before the next sprint? Try running an Energy Levels retrospective for free in Parabol Sprint Retrospective Ideas to Facilitate Your New Techniques Now that we have covered some effective and interesting techniques for retrospective meetings, it only seems right to provide some no-nonsense sprint retrospective ideas that will help you execute those techniques and formats.
Remember: the only truly wrong way to do a retrospective is not to do one. When everyone finishes, address each item one by one to allow people time to share input.
At the end of the discussion, set up a vote to decide which items are most important. Give each team member a set number of items they can vote for usually three. Calculate which items got the most votes selecting the top few no more than three , and keep those items as your area of focus for the next Sprint. Review these areas of focus at the beginning of your next Retrospective to measure their success.
With a little tweaking for personalization, your team can use an agile retrospective format. To follow, break up your Retrospective into the following five stages:. Start with a game, like asking each team member to summarize the Sprint using only three words. Use the first few minutes of your meeting to establish an open and informal tone where people can feel comfortable bringing up ideas. Ask each team member to compile their observations about the Sprint onto cards.
To generate insights, lay out all the cards from your team and start organizing them by similarities. Other times people you may realize that all the cards seem to relate to a specific stage in development. Now is the time to pay attention to recurring themes, patterns, and issues that might cause one another.
0コメント