Sprint Review Meeting
Ending of each Sprint is marked with a significant gain of the product’s functionality. Moreover, it means that the code is complete, tested and a part or the whole product is ready.
Sprint Review Meeting is held at the end of each Sprint and used as an overview. During the meeting, the Team evaluates the results of the work, usually in a form of demo of newly implemented features.
Sprint Review Meeting shouldn’t be treated as a formal meeting with detailed reports. Sprint Review Meeting is just a logical conclusion of a Sprint. One shouldn’t spend more than 2 hours to prepare for the meeting. PowerPoint-like slides are also prohibited.
The Product Owner, the Development Team, the Scrum Master, Management, customers and developers from other projects usually take part in it.
During the Sprint Review Meeting, the project is being evaluated from the point of view of the previously described Sprint Goal. Ideally, a Team should have closed all the tasks from the Product Backlog, but the main thing is the Sprint Goal.
What does a customer pay attention to during the Sprint Review Meeting:
- If the product is complete;
- If the work of the Team is finished;
- Various project indicators (code completeness, etc.);
- Quality and performance of the finished tasks;
- Overview of the priorities for the next Sprints\iterations;
Duration of the Sprint Review Meeting
The duration of a Review Meeting can be calculated with the following formula: each Sprint week equals one hour of Sprint Review Meeting. Thus, if a Sprint lasted 4 weeks, then the Sprint Review Meeting will last 4 hours.
An example of a Sprint Review Meeting
The development of an online-store, mentioned in various articles of our Info Base, includes Sprints, and Sprints have Sprint Review Meetings.
Sprint Review Meeting during the development of an online-store
| Section | Name | Description | Status | Rating | Release |
|---|---|---|---|---|---|
| Catalog management | “Add a product” feature | Develop “add a product” feature, which includes the following field: Product Name, Product Image, Product Price, Discount or No discount. | In development | 2 | Release 1 |
| Catalog management | “Remove a product” feature | “Remove a product” feature, allowing the removal of a single product or several products using bulk selection | In development | 2 | Release 1 |
| Order | Payment | C.O.D. payment feature | In development | 10 | Release 1 |
| Order | Payment | Implement Visa & Mastercard payment support | In development | 10 | Release 1 |
| Order | Payment | Implement PayPal payment support | In development | 10 | Release 2 |
| Order | Sign Up | Sign Up via Facebook | In development | 1 | Not planned |
| Order | Sign Up | Sign Up via Google+ | In development | 1 | Not planned |
| ... | ... | ... | ... | ... | ... |
According to this Backlog, we see that some of the tasks from the first release were added to the Sprint:
- 1. "Add a product" feature.
- 2. "Remove a product" feature.
- 3. "C.O.D. payment" feature.
- 4. "Pay by VISA, MasterCard" feature.
So, during the Sprint Review Meeting such features as adding\removing a product to\from a database will be discussed. Besides, a demo of two types of payment features will be performed.
Sprint
The most important element of Scrum is probable Sprint. Everything revolves around it, because the products are created during Sprints.
Product Owner
A Product Owner is a link between the Client and the development Team. He has the authority to make final decisions withing a Scrum Team
Development Team
We tend to think that a 'work unit' means a single person, if we talk about human resources. But in Scrum it is a bit different: it is the Development Team which is a work unit.
Scrum Master
Let’s try understand once and for all what does the notion Scrum Master mean and what are the duties of a Scrum Master.
Management
The notion of management when talking about a Scrum Team is much more vague and less important if we compare it with traditional management of development teams. Some even think that it is the Product Owner who acts as a manager.
Product Backlog
A Product Backlog should be clear for everyone (and that is the Product Owner’s responsibility) It should be so clear that both the Team and the Owner could work with it without any problems.
