banner image for Retrospective Showdown: Start Stop Continue vs. Drop Add Keep Improve

Retrospective Showdown: Start Stop Continue vs. Drop Add Keep Improve

by Eric on September 22, 2024

Retrospectives are a crucial part of any agile team’s continuous improvement process. They provide a structured opportunity for teams to reflect on their work, identify areas for improvement, and celebrate successes. Two popular retrospective techniques that have gained traction in recent years are the “Start Stop Continue” and the “Drop Add Keep Improve” methods. In this article, we’ll dive deep into both approaches, comparing and contrasting their features, benefits, and potential drawbacks.

Start Stop Continue: The Classic Approach

The Start Stop Continue retrospective is a straightforward and intuitive method that encourages teams to reflect on their practices in three distinct categories:

  1. Start: What new practices or behaviors should the team begin implementing?
  2. Stop: What current practices or behaviors are hindering progress and should be discontinued?
  3. Continue: What existing practices or behaviors are working well and should be maintained?

This method is particularly effective for teams that are new to retrospectives or those looking for a simple, easy-to-understand format. Its clear-cut categories make it easy for team members to contribute their thoughts and ideas without getting bogged down in complex frameworks.

Drop Add Keep Improve: The Evolved Alternative

The Drop Add Keep Improve (DAKI) retrospective is a more nuanced approach that builds upon the Start Stop Continue method. It offers four categories for reflection:

  1. Drop: What practices or behaviors should be eliminated entirely?
  2. Add: What new practices or behaviors should be introduced?
  3. Keep: What existing practices or behaviors are working well and should be retained?
  4. Improve: What current practices or behaviors have potential but need refinement?

This method provides a more granular approach to reflection, allowing teams to identify areas that require fine-tuning rather than outright elimination.

Comparing the Two Approaches

  1. Simplicity vs. Nuance

Start Stop Continue is prized for its simplicity. The three categories are easy to understand and remember, making it an excellent choice for teams new to retrospectives or those with limited time. This simplicity can lead to quicker discussions and more straightforward action items.

On the other hand, Drop Add Keep Improve offers a more nuanced approach. The addition of the “Improve” category allows teams to identify practices that have potential but need refinement, rather than simply discarding them. This can lead to more thoughtful discussions and a more iterative approach to improvement.

  1. Decision-Making Process

In Start Stop Continue, teams are essentially making binary decisions: either start something new, stop something entirely, or continue as is. This can lead to quicker decision-making but may oversimplify complex issues.

DAKI allows for more gradual changes. The “Improve” category encourages teams to consider how existing practices can be enhanced rather than abandoned entirely. This can lead to more sustainable, incremental improvements over time.

  1. Positive vs. Negative Framing

Start Stop Continue has a relatively balanced approach to positive and negative feedback. The “Stop” category explicitly focuses on negative aspects, while “Continue” highlights positives.

DAKI tends to have a slightly more positive framing. While “Drop” is similar to “Stop,” the addition of “Improve” allows teams to approach shortcomings with a growth mindset rather than outright rejection.

  1. Depth of Analysis

Start Stop Continue can sometimes lead to surface-level analysis, as team members might feel pressure to come up with items for each category, even if they don’t have substantial insights.

DAKI’s four categories can encourage deeper analysis. The “Improve” category, in particular, prompts team members to think critically about the nuances of their practices and how they can be refined.

  1. Time and Effort Required

Start Stop Continue is generally quicker to execute, making it ideal for teams with limited time or those conducting frequent, short retrospectives.

DAKI may require more time and mental effort from participants due to its additional category and the more nuanced thinking it encourages. However, this additional investment can lead to more comprehensive insights and actionable improvements.

Choosing the Right Approach

Both Start Stop Continue and Drop Add Keep Improve have their merits, and the choice between them often depends on the team’s specific needs and circumstances. Here are some factors to consider when deciding which method to use:

  1. Team Experience: For teams new to retrospectives or agile methodologies, Start Stop Continue might be the better choice due to its simplicity and ease of understanding.

  2. Available Time: If time is limited, Start Stop Continue can provide quick insights and action items. For more in-depth reflection, DAKI might be more appropriate.

  3. Project Complexity: For complex projects with many moving parts, DAKI’s nuanced approach might be more beneficial in identifying areas for incremental improvement.

  4. Team Dynamics: If the team struggles with negative feedback, DAKI’s more positive framing might be more conducive to constructive discussions.

  5. Frequency of Retrospectives: For teams conducting frequent retrospectives, alternating between the two methods can provide fresh perspectives and prevent stagnation.

Hybrid Approaches and Variations

It’s worth noting that these retrospective techniques are not mutually exclusive. Many teams have found success in creating hybrid approaches that combine elements of both methods. For example, a team might use the Start Stop Continue framework but add an “Improve” column to incorporate the nuanced thinking encouraged by DAKI.

Some teams also incorporate additional elements into these frameworks, such as:

  1. Prioritization: After generating ideas in each category, teams vote on the most important items to focus on.
  2. Action Planning: For each selected item, the team creates specific, measurable action plans.
  3. Review of Previous Actions: Teams start the retrospective by reviewing action items from the previous session.

Conclusion

Both Start Stop Continue and Drop Add Keep Improve are valuable tools in the agile team’s retrospective toolkit. Start Stop Continue offers simplicity and quick insights, making it ideal for teams new to retrospectives or those with limited time. Drop Add Keep Improve provides a more nuanced approach, encouraging deeper reflection and incremental improvements.

Ultimately, the most effective retrospective technique is the one that resonates with your team and drives meaningful improvements. Don’t be afraid to experiment with both methods, create hybrid approaches, or even develop your own variations tailored to your team’s unique needs and culture.

Remember, the goal of any retrospective is to foster continuous improvement and team learning. Whether you choose Start Stop Continue, Drop Add Keep Improve, or a hybrid approach, the key is to create an environment where team members feel safe to share their thoughts, reflect honestly on their work, and commit to positive changes.

By regularly engaging in thoughtful retrospectives, teams can enhance their processes, strengthen their relationships, and ultimately deliver better results. So, choose your method, gather your team, and start reflecting – your next big improvement might be just one retrospective away!

Agile methodologies Continuous improvement Team reflection