{"id":23135,"date":"2023-07-10T17:43:11","date_gmt":"2023-07-10T15:43:11","guid":{"rendered":"https:\/\/scrum-master.org\/retrospective-keep-drop-start-the-complete-guide-to-boosting-your-scrum-team\/"},"modified":"2024-06-20T20:51:49","modified_gmt":"2024-06-20T18:51:49","slug":"retrospective-keep-drop-start-the-complete-guide-to-boosting-your-scrum-team","status":"publish","type":"post","link":"https:\/\/scrum-master.org\/en\/retrospective-keep-drop-start-the-complete-guide-to-boosting-your-scrum-team\/","title":{"rendered":"Retrospective Keep Drop Start: The Complete Guide to Boosting Your Scrum Team"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The “Keep Drop Start” retrospective<\/strong>, also known as “Keep Stop Start,” is a favored model among Scrum teams globally for its effectiveness in driving the continuous improvement process within teams.<\/p>\n

Excitingly, we have prepared a free Miro template<\/a> to streamline the implementation of this retrospective for your team!<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Why Use the Keep Drop Start Model?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This retrospective model is crafted to assist your Scrum team in pinpointing what’s currently working well (Keep), what should be ceased (Drop), and what enhancements or new practices should be adopted (Start) for the upcoming sprint. It excels at not only spotlighting the positives but also at uncovering areas ripe for improvement, thereby cultivating a culture of continuous learning and bolstering team cohesion.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

How to host a Keep Drop Start retrospective?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Facilitating a Keep Drop Start retrospective is straightforward and involves three key steps:<\/p>

Preparation<\/h3>

Set up a board with three distinct columns: Keep, Drop, and Start, before the retrospective. This can be easily achieved on a physical whiteboard, a wall with sticky notes, or via a digital Miro template.<\/p>

Discussion<\/h3>

Kick off the discussion with the “Keep” column, inviting each team member to reflect on and share the aspects they believe worked well and should be preserved for future sprints. Transition next to the “Drop” column to discuss what should be stopped or avoided. Lastly, in the “Start” column, encourage suggestions for new ideas or improvements to implement.<\/p>

Conclusion<\/h3>

Wrap up the retrospective by reviewing the compiled ideas and determining the actionable steps to be taken. It’s crucial to assign responsibility for each action to ensure they are followed through and effectively implemented.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

A Free Template for the \"Keep Drop Start\" Retrospective on Miro<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Ready to launch your “Keep Drop Start” retrospective? Miro, known for enhancing collaborative sessions, offers a dynamic template to effortlessly guide your team through this reflective process. Its whiteboard functionality not only promotes active participation but also ensures that every team member can contribute their thoughts and insights in real-time.<\/p>

The “Keep Stop Start” template on Miro is designed to facilitate structured discussions, creating separate spaces for each category: Keep, Drop, and Start. This organization aids in clearly defining areas of focus, making it simpler for your team to navigate through the retrospective. Additionally, the template incorporates point voting tools, allowing your team to collectively decide on priorities for the next sprint cycle.<\/p>

To access this template, simply visit the Miro template library. There, you’ll find the “Keep Drop Start” template ready for use in your upcoming session. Unlike downloadable resources, this template is directly accessible within Miro’s platform, providing an interactive and engaging environment for your team’s retrospective.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

If you’re seeking a versatile and straightforward approach for your next retrospective, exploring the Miro template library<\/a> is a great starting point. Miro’s array of templates, including the “Keep Drop Start” model, is designed to support Scrum Masters and their teams in fostering a culture of continuous improvement and collaboration.<\/p>

Embark on your retrospective journey with Miro<\/a> and discover the ease and effectiveness of using their templates to enhance your team’s agile practices.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Popular Variations of the Keep Stop Start Retrospective<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

While the “Keep Drop Start” model is invaluable for Scrum Masters, various adaptations can further stimulate your team’s continuous improvement journey:<\/p>

The “Start Doing, Continue Doing, Stop Doing” Retrospective<\/h3>

This variant mirrors the “Keep Drop Start” model closely, requiring team members to identify actions to start, continue, or stop doing. We’ll delve into why the “Keep Drop Start” sequence is preferred over “Start, Continue, Stop” or other variations.<\/p>

The “Mad Sad Glad” Retrospective<\/h3>

This approach prompts team members to reflect on their emotions during the sprint, identifying moments that made them mad, sad, or glad. It’s particularly effective for bringing emotional and psychological aspects into technical retrospectives.<\/p>

The “What Went Well, What Didn\u2019t Go Well” Retrospective<\/h3>

A straightforward model that asks team members to discuss the highs and lows of the sprint. The key difference from the Keep Stop Start model lies in its focus on team behaviors and practices evolution, as opposed to merely recounting positive and negative experiences.<\/p>

The Sailboat or Speed Boat Retrospective<\/h3>

Viewing the project as a boat, this retrospective examines the “anchors” (problems) slowing the team down and the “wind” (helpful factors) propelling them forward. For an in-depth look at this model, check out our article on the Speed Boat retrospective.<\/a><\/p>

Each retrospective variant has unique strengths, suitable for different team dynamics or situations. However, the simplicity and action-oriented nature of the “Keep Drop Start” model make it a popular and effective choice.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Why prefer the \"Keep Drop Start\" model to \"Start Stop Continue\"?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In the ‘Start Stop Continue’ model, the conversation culminates with ‘What should we continue to do?’ Conversely, in the variant ‘Start Doing, Continue Doing, Stop Doing,’ the dialogue ends with ‘What should we stop doing?’ This sequence may not optimally guide teams into the phase of proposing new actions.<\/p>

However, the ‘Keep Drop Start’ model shifts the focus, ending on ‘What should we start doing?’<\/strong> This subtle reordering prompts teams to proactively consider new actions for improvement<\/strong>, fostering a mindset geared towards innovation and yielding more effective outcomes.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Conclusion<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The “Keep Drop Start” retrospective is a pivotal tool for any Scrum Master seeking structured team development. It emphasizes identifying practices worth continuing, eliminating, and adopting anew, making it an essential mechanism for fostering team growth and efficiency.<\/p>

This guide has outlined the methodology behind this retrospective model and highlighted the advantages of using collaborative tools like Miro to facilitate online sessions. We’ve also explored various retrospective formats, emphasizing the constructive nature of the “Keep Drop Start” approach.<\/p>

In pursuit of continuous improvement, don’t hesitate to experiment with different models and tailor them to your team’s unique needs. The ultimate goal of any retrospective is to support your team’s evolution, enhancing collaboration and effectiveness.<\/p>

Utilize our free Miro template<\/a> to streamline your “Keep Drop Start” retrospective, and embark on a journey of happy retrospecting!<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

The “Keep Drop Start” retrospective, also known as “Keep Stop Start,” is a favored model among Scrum teams globally for its effectiveness in driving the continuous improvement process within teams. Excitingly, we have prepared a free Miro template to streamline the implementation of this retrospective for your team! Why Use the Keep Drop Start Model? […]<\/p>\n","protected":false},"author":4,"featured_media":22727,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[140,139],"tags":[142,145,144],"class_list":["post-23135","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tools-tests-and-reviews","category-scrum-en","tag-ceremonies","tag-retrospective-models","tag-team-building-en"],"_links":{"self":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts\/23135","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/comments?post=23135"}],"version-history":[{"count":0,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts\/23135\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/media\/22727"}],"wp:attachment":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/media?parent=23135"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/categories?post=23135"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/tags?post=23135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}