Sprint Conclusion: Recap and Next Steps

Core Method
Collected by Google

Once you have completed your validation sessions, bring the team back together to review the findings. Create a visual presentation of the Validation Sessions or compile the results into a document. The important thing is that the team reviews the findings together to absorb the learnings and discuss next steps for the project. Every Design Sprint should have actionable learnings that lead into the next round of product development.

STATS
Time
60 mins
Activity
Group
Sprint Type
All

Directions

A Design Sprint can have the following outcomes:

  • An efficient failure: The prototypes didn’t hit the mark, but you learned something (or many things) and saved your team four to six months of work building the wrong product. You might want to run a follow-up Sprint.
  • A flawed success: Some ideas met your user’s needs, but not all of them. You learned something and can now iterate and test again.
  • An epic win: The concept met your user’s needs; they were able to complete tasks easily and engaged with all the features you mapped out. You are ready to implement!
  • Closing the Sprint. The team has worked really hard, generated a broad range of ideas, and learned from their users. The Sprint Master should acknowledge all of this hard work and celebrate the learnings the team has achieved. A closing circle is a nice way to bring everyone together. Here you can ask people to share insights, what they will take away from the experience, and give people a sense of accomplishment. And perhaps discuss what problem you want to tackle next!