Start/ Stop/ Continue Restrospective Template
Get feedback on what your team wants to Start, Stop, and Continue doing.
About the Start Stop Continue Template
What is Start Stop Continue?
Giving and receiving feedback can be challenging and intimidating. It’s hard to look back over a quarter or even a week and parse a set of decisions into “positive” and “negative.” The Start Stop Continue framework was created to make it easier to reflect on your team’s recent experiences. It’s a simple but powerful tool that empowers individuals and teams to decide what to change going forward.
To use the Start Stop Continue framework, teams or individuals divide their activities and decisions into three categories: things they should start doing, things they should stop doing, and things that should continue to form a part of your processes.
Why use the Start Stop Continue template?
The Start Stop Continue Retrospective allows everyone to review the actions they've taken in the past, and determine which ones are worth stopping or continuing. Also, people can think about new actions they should begin doing. Each item results in behavioral change.
When should you use the Start Stop Continue template?
Many teams use the Start Stop Continue Retrospective template at the end of an agile sprint, but others find it is most useful at the end of an entire project, quarter, or event.
The 3 elements of Start Stop Continue
1. Start - What should you start doing? These are activities and behaviors that might improve your processes, reduce waste, and have a positive impact on the way your team functions. Think about technical and behavior elements that might fall into this category. What tools should you start using? Is there a communication style that might work better for your team?
2. Stop - What should you stop doing? These activities and behaviors might be inefficient, wasteful, or have a negative impact on the way your team functions. Again, it’s important to consider both technical and behavioral elements. Is your team using a tool that doesn’t work for you? Is there a meeting style or a communication method that isn’t working?
3. Continue - What should you keep doing? These are activities and behaviors that you’ve tried out and liked, but that aren’t yet part of your core processes. Take stock of the tools and methods you’ve experimented with since the last review cycle. What would you like to continue?
A team charter is a document that outlines your team’s purpose and objectives, as well as steps you will take to reach your goals. The team charter illustrates the focus and direction for all team members. When created collaboratively, the team charter is a great way for individuals to feel even more connected to one another within the group. A team charter template is useful when you’re first establishing a new team, adding new members to an existing team, or when you need to better align regardless of your team’s tenure.
At some point during your career, you’ll probably have to give a presentation. Presentations typically involve speaking alongside an accompanying slide deck that contains visuals, texts, and graphics to illustrate your topic. Take the stress out of presentation planning by using this presentation template to easily create effective, visually appealing slides. The presentation template can take the pressure off by helping your audience stay focused and engaged. Using simple tools, customize a slide deck, share slides with your team, get feedback, and collaborate.
User Story Map Framework
Popularized by Jeff Patton in 2005, the user story mapping technique is an agile way to manage product backlogs. Whether you’re working alone or with a product team, you can leverage user story mapping to plan product releases. User story maps help teams stay focused on the business value and release features that customers care about. The framework helps to get a shared understanding for the cross-functional team of what needs to be done to satisfy customers' needs.
When you’re working on a new feature that solves a problem for your users, it’s easy to dive right in and start looking for solutions. However, it’s important to understand the initial user problem first. Use the Feature Canvas template to do a deep-dive into the user’s problems, the context in which they will use your feature, and the value proposition you will deliver to your users. The template enables you to spend more time exploring the problem to anticipate any potential blind spots before jumping into solutions mode.
When your meeting is a success (and Miro will help make sure it is), participation will run high, brilliant ideas will be had, and decisions will be made. Make sure you don’t miss a single one — use our meeting notes template to track notes and feedback in a centralized place that the whole team can access. Just assign a notetaker before the meeting, identify the discussion topics, and let the notetaker take down the participants, important points covered, and any decisions made.
Part of the popular Agile framework, an Agile Board is a visual display that allows you to sync on tasks throughout a production cycle. The Agile Board is typically used in the context of Agile development methods like Kanban and Scrum, but anyone can adopt the tool. Used by software developers and project managers, the Agile Board helps manage workload in a flexible, transparent and iterative way. The Agile template provides an easy way to get started with a premade layout of sticky notes customizable for your tasks and team.