4.4 Sprint 2 Review Meeting
Last updated on 2026-03-19 | Edit this page
Overview
Questions
- How to choose a product name?
- How do we run Sprint Review meetings again?
Objectives
- Choose three candidate names for your software product
- Participate in a Sprint review meeting
- Verify sprint backlog against definition of done
What’s in a Name?
5 mins.
A product name is important because it shapes how people first perceive and engage with what you’ve created.
Take a few minutes as a team to decide on three candidate names for your product to suggest to the client.
The Software Sustainability Institute’s guide on naming projects and products may provide some helpful pointers.
Sprint 2 Review
Following our second sprint, as before, we now prepare for and hold a Sprint Review meeting for the client. You may find it useful to refer back to the material on sprint reviews.
Prepare for the Sprint Review
Take 30 minutes to prepare for the Sprint 2 Review.
- Prepare your demonstration and decide who will present each element
- Write a structure (or agenda) for the meeting (including a short item on deciding a product name from the candidates)
- Consider how your progress has moved the project toward the Product Goal
- Prepare any questions you have for the client
- Decide who will take on each role
Sprint 2 Review Meeting
Teams conduct the Sprint Review meeting with the clients (30 mins).
Update Product Backlog
Teams spend 15 minutes updating the Product Backlog (15 mins).
- Use a checklist for Sprint Reviews (and other meetings) to ensure you don’t forget anything.