What is a Sprint Review in Scrum?
The Sprint Review meeting (event) is one of four Scrum events. The article describes real example situations from the point of view of the Scrum Master role and describes their exemplary most adequate reactions to the mentioned problems and cases.
The article is inspired by the original publication “Scrum Sprint Review meeting Questions and Answers” by the PolicyMatters magazine (2020 Vol. 2, Scrum Sprint Review meeting Questions and Answers By Marta Cooper, June 15, 2020, PolicyMatters ISSN: 1941-8280, 1941-8272). We have used the same questions and topics but give different points of view and answers.
Your colleague, a beginner Scrum Master, asks you a question. He asks you if for their 3 week sprints, they can accept the Sprint Review event lasting 2 and a half hours.
Scrum Master’s answer: The duration may be a little insufficient for such a long sprint, especially if the scrum master is insecure and can hardly lead the discussions effectively and concisely. I would recommend him to plan about 3 hours, maybe even a little more, if there will be many outsiders whose participation cannot be effectively controlled in terms of duration. Reference: Professional Scrum Master vs Professional Scrum Developer, stc-montreal.org
You gather at the usual place for your Sprint Review event. Attendees are: You as the Scrum Master, the Development team without a new budding colleague, the Project Manager from the client, their Product Manager, Business Analyst, and a hired external usability consultant.
Scrum Master’s answer: There is no Product Owner, and it is extremely important in the adaptation of Product Backlog Items, and probably has specific information and competencies, without which the review of the sprint could be completely ineffective. Outsiders may be too much for the meeting, but could be admitted if deemed necessary by the Product Owner. Reference: What makes a good Product Owner and what do they do?, scrumtime.org
A project manager from your organization came to your Sprint Review event. He listens carefully and watches. He is pleased that the work is going well. Finally, he turns to you and asks you when you expect as a guide to release the latest finished developments to a real product in a living environment.
Scrum Master’s answer: This is a good reason to initiate a discussion with team members about when we will have a plan to launch the product to end customers or business stakeholders, if the project is in a sufficiently advanced phase, and we can implement in the upcoming sprints. sufficiently complete and effective increment.
The Sprint Review event begins. Shortly after greeting each other, the customer’s product manager opens a topic about the project budget. He is not sure if his organization’s resources will be enough to continue working on the product for another 6 months. Ask your Product Owner for comment and advice on their Roadmap.
Scrum Master’s answer: The Scrum Master should intervene and point out that the discussion of additional issues will be done at the end of the meeting after the review of the sprint and review of the development of the product increment, when all participants in the meeting will have more a good idea of what needs to be done, adjusted or supplemented in order to have an effective product, and it will be possible to make a more adequate forecast of the time needed for this. eference: Scrum problems, causes of failure and mistakes, phron.org
At the Sprint Review event, business people and all representatives outside your Scrum team review what has been achieved and let you know that they have no questions or any other comments or suggestions, and prepare to leave the meeting.
Scrum Master’s answer: The admission of outsiders is done in order to obtain effective feedback and adapt the product to the stated needs of customers, and their changes, as well as changes in market circumstances and other changes. If we have already received all this data, there is no problem in the withdrawal of outsiders, but if we have not – we should try to initiate a discussion on these issues.
Your client’s Account Manager will contact you and ask if you can demonstrate your product one day before the end of your sprint because they need to prepare presentations.
Scrum Master’s answer: The product demonstration is part of the sprint review, which has a specific day and includes many participants. The demo itself without the discussions related to its consideration and evaluation of the items may not provide sufficiently reliable information about the client, but this request must be considered with the product owner, who is responsible for the relationship with external stakeholders and be resolved by him. Reference: Problems of the Scrum Master role with the Sprint Review and Scrum Sprint Retrospective meetings, nebraskasocialstudies.org
Your customer’s product manager disapproves of Definitions of Done for one of your User Stories and refuses to accept work on it. Everyone is staring at you, including your product owner.
Scrum Master’s answer: The approval of the items from the backlog is done only by the Product Owner, and this should be clarified to the participants of the meeting. Since even a product owner looks at Scrum Master, it means that we have not explained this function to him, but we must transfer the question to him as kindly as possible, and if he shares the opinion of the customer’s product manager, take into account the corrections and transfer performance according to the new requirements of the particular user did to the next sprint.
One day before your Sprint Review event, your client’s Account Manager contacted you and explained that they were working with the Marketing Department to prepare new plans. He asks you to send him the items that your team will complete during the sprint.
Scrum Master’s answer: We must refer to the Product Owner as the person responsible for the interests of outsiders and consumers. If he has no problems with the customer’s request, we can provide him with a list of completed items that will be discussed at the sprint review anyway and approved or corrected by Product Owner. Reference: Product Owner role in Scrum and real problem situations, vbprojects.org
You have already presented your increment at the Sprint Review meeting. Product Backlog items have been officially announced as completed. There is no work left unfinished. Everyone looks happy. Business people offer, as everything is fine, to discuss possible promotions of team members who have performed well, and then want to take you for a drink.
Scrum Master’s answer: Outsiders have nothing to do with the development team’s pay, and in my personal opinion, they should never meet in an informal setting. Communication with external business people is left to the Product Owner, who may try to satisfy many Agile and Kaizen principles and have the opportunity to convey customer satisfaction from senior management developers, but this is beyond the competence of Scrum Master and such discussions should not be allowed to be part of the sprint review. Every Scrum Master must know the Kaizen principles, wikipedia-lab.org
Shortly before the Sprint Review event, a team member told you that User Story covers all definitions of completeness, but the finished work visually differs from the sketches included in the Product Backlog item.
Scrum Master’s answer: If a given Product Backlog Item is accepted and approved by a Product Owner, it means that we have met its requirements, which may have changed from the originally defined sketches, but it is good to specify it further with it in order to we are sure that there are no omitted and unclear elements in the product that would be a problem in the future. We have to agree with Marta Cooper from PolicyMatters that Scrum is now Kamban and we are sharing the same reference. Reference: Kanban methodology vs Scrum framework, libraryofmu.org
While browsing the Product Backlog items, the customer project manager interrupts the conversation and asks a question to your Product Owner. He asks him why two very similar items are rated Story Points 3 and 13. The Product Owner looks at you.
Scrum Master’s answer: It will be explained to the outsider that the two items probably look similar at first glance, but in detail the professional developers have found enough differences and specifics between them to give them different points based on practical experience. , the technology used and the available information for their implementation. Reference: Real Scrum problems of the Scrum Master role during the Daily Scrum meeting, mpmu.org