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 clear presentation. The important thing is that the team reviews the findings together, absorbs the learnings, and discusses next steps for the project. Every Sprint should have actionable learnings that lead into the next round of product development.

A Sprint can have the following outcomes:

• An efficient failure : The prototypes didn’t hit the mark, but you learned something (many things) and saved your team 4-6 months of work building the wrong product. You might want to run a follow up Sprint.
• A flawed success : Some of your ideas met users’ needs but not all of them. You learned something and can now iterate and test again.
• An epic win: The concept met your users’ needs; they were able to complete tasks easily and engaged with all the features you mapped out. You are ready to implement!

This is a good time to be sure there are clear owners to drive the concepts and learnings forward.

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 this hard work and celebrate the learnings the team has achieved. A closing circle is a nice way to bring everyone together, you can ask people to share insights, what they will take away from the experience and give people a sense of accomplishment.

Directions

Time: 10 min
Activity: Facilitator leads

1. Have everyone stand in a circle
2. Ask the group "does anyone want to share one thing they will take away from this Sprint?"
3. Encourage multiple people to share
4. Congratulate everyone and celebrate!