Actually, the sprint review IS a sign-off meeting in a lot of cases. Whilst the team should not expect glowing praise on their work or that all demonstrated items will be accepted as done, those items which are indeed 'done' will receive formal acceptance during this meeting (in most cases).
There was a bit of a scare with the ownership of the product, which had us scrambling to find a replacement, I switched to zentao which helps me get things done and it has more features.
As you have said that post review meeting, the scrum master updates the minutes of meeting to the development team, new backlog item to the scrum team and the project manager, so my question is that how the updation happens, does it happen via mail where we put CC to the scrum team and the product manager. Kindly clarify. My second question is that how do a product manager or scrum master invites the stakeholders before sprint review, does it also happen via mail. Kindly through some light on it.
Question but not related to this what are schedule assessment and case studies that can be brought up in scrum master interview? I feel this "schedule assessment and case studies" is more for waterfall PM your thoughts?
Very practical explanation. I have one question. If we committed to a user story and we couldn't complete it, do we need to include it in scope of demonstrate document or do we need to discuss it in reviews meeting??
Another question. At 13:38 its mentioned, that the SM has to make the meeting happen, but at 6:24 its mentioned that the PO is inviting for the meeting. Can you please clarify who has the lead in the Review meeting?
The SM has to ensure that the meeting happens, as SM is the protector of the scrum process he/she can help the PO to invite stakeholders. This meeting can be scheduled by Scrum Master, however PO is the best person to invite business users and Stakeholders.
Hi Niladri, I have a questions, If Sprint review is not a meeting for demonstration by developer or user story acceptance by product owner, then in which ceremony PO accept the produce by DOD?
Product Owner is the scrum team member, Product owner should review the completion during the sprint and accept the user story. Its a practice of taking the activity as part of each story and does not required any ceremony.
As shown in 12:22 , the review meeting does not include story acceptance by the PO. Does that mean, the user story acceptance, which I assume is the same as the user story "Done" acceptance, is held latest a day before the review meeting, so that only the "Done"&"Accepted" User stories will be shown on the review meeting? If so, then it confuses me that its mentioned at 12:25, that the user story acceptance meeting by the PO, is done after the review meeting. Can you please clarify?
User Story "Moving it to Done" is primarily job of product owner, user stories does not need to wait for the last date to get accepted, PO is the part of the scrum team, he/she can accept it as and when its getting completed and ready to verify. at 12:25 I have mentioned its "Not" a user story acceptance meeting.
Thanks for another well described video Niladri. I have two questions here - 1. Is UAT a part of sprint cycle or it will be initiated after DevOps moves the increment to Test Box ? 2. Considering today is Sprint Review and tomorrow is next sprint planning, if new business items are identified today and need to be prioritized in next sprint, there is no time left for Grooming. Can we consider that new identified backlog items are not meant for "at least the immediate next sprint" ?
Answer 1 : Ideally sprint execute by Scrum team, where scrum team consist of three roles, PO/SM and Dev Team. During Sprint Planning the Team commits to the number of Product backlog items, that they think they will able to complete it before Sprint Time box ends. Complete means the PBIs (Product Backlog items) should meets the definition of Done. Here Scrum Master Facilitate, Developers Develop, Testers Teste and PO verify to move the PBI to Done. PO who owns the Product, User Who Use the Product. The Traditional UAT (User acceptance test) can not fit in, or at least I don’t suggest to adjust UAT with in Sprint Time Box. Agile works on Trust with self-organize team members, and the end of the sprint, they should deliver shippable increment. But, if it the case that your organization needs UAT as must and you need to do a UAT within Sprint Duration, make sure You DOD is appropriate, Don’t Extend the Sprint Duration, UAT has to be completed and fixed with in Sprint time box. Its better to identify the users who will do the UAT during sprint planning. Initiate the UAT for as on when each PBI is ready (try to adopt finish first start later approach), Don’t wait for the sprint to end. Share your teams testcases to end users to expedite the UAT. Any PBIs that does not meets the DOD because of UAT, move them back to backlog at Sprint closure. Many organization do have a practice of doing System Testing or Integration Testing manually or as a Part of DevOps pipeline. On those case, your sprint should be done at when the Backlog items ready to join the DevOps pipeline. UAT will be after that if required. Answer 2 Our primary focus is to add most valuable increment first. If there are some very high importance work item evolved during review, and only grooming is sufficient to start the work, then definitely you will groom the stories during beginning of the Sprint Planning. Product Owner understand the priority of delivery items. So its better to follow the priority set by your PO. But if there are some external dependencies may block the PBI to get completed on the sprint, don’t commit. You need to commit only those PBIs that you are sure that you will able to complete. To keep PO’s priority in mind, You can keep some buffer capacity to accommodate that later (That will create a Scope Creep), if all dependencies and risks got resolved. Again those cases and solutions are varies on organizations and practices to maturity levels and other scenarios. The explanation mentioned above may not perfectly fits in to your case.
Imtiaz, There are purpose for all the agile ceremony. Please don't conduct those meetings just for any formality. Many Team conducts these meeting because they think we need this meeting to run our project on agile. All the ceremonies prescribed by the framework has a purpose to solve, to make the agile way of development more mature. In your case you can decide if there are no stakeholders or Business manager or Management participates on your sprint review, what you will do at that meeting, that you can not do during your sprint duration between your team. Remember Product owner is the Part of your team.
Wonderfully explained. Very detailed information on Sprint Review. Thank you for sharing.
Great video! Excellent explanation of the process!!
Thank You
One of the best videos i have ever watched on scrum
This set of videos are so informative, clear and detailed. Well done, keep you the good job!
Truly excellent explanation. Thank you!
You're very welcome!
Absolutly clear, crisp and knowledagble presentation. Keep up the good work!!
Awesome.
Proud of you Sir.. very nice video.. Thanks
Very well explained.. Thanks for the video.
You are welcome!
Nice explanation of the concept
Keep watching
Great Explanation....Cleared the concept
Very informative video Niladri..Thank You !!
Thanks
very good, thank you
Good Job. Thank you.
Actually, the sprint review IS a sign-off meeting in a lot of cases. Whilst the team should not expect glowing praise on their work or that all demonstrated items will be accepted as done, those items which are indeed 'done' will receive formal acceptance during this meeting (in most cases).
There was a bit of a scare with the ownership of the product, which had us scrambling to find a replacement, I switched to zentao which helps me get things done and it has more features.
As you have said that post review meeting, the scrum master updates the minutes of meeting to the development team, new backlog item to the scrum team and the project manager, so my question is that how the updation happens, does it happen via mail where we put CC to the scrum team and the product manager. Kindly clarify.
My second question is that how do a product manager or scrum master invites the stakeholders before sprint review, does it also happen via mail. Kindly through some light on it.
Question but not related to this
what are schedule assessment and case studies that can be brought up in scrum master interview?
I feel this "schedule assessment and case studies" is more for waterfall PM your thoughts?
I need to understand you question in bit more details. Please email me.
Great video with crystal clear and to the point explanation!
Could you include/share sample for minutes of meeting and closure report ?
Thank you. Please drop us an email. we will try to share with you.
Hello, Is this still available? can i get this ?
Very practical explanation. I have one question. If we committed to a user story and we couldn't complete it, do we need to include it in scope of demonstrate document or do we need to discuss it in reviews meeting??
If the story is not completed, You can not demonstrate it right ?
True! I meant, as a PO, do we need to inform to stakeholder that we could not complete it?
Niladri, can you also do a video on SAFE PI planning.
I want to, Lets see when time permits.
Another question. At 13:38 its mentioned, that the SM has to make the meeting happen, but at 6:24 its mentioned that the PO is inviting for the meeting. Can you please clarify who has the lead in the Review meeting?
The SM has to ensure that the meeting happens, as SM is the protector of the scrum process he/she can help the PO to invite stakeholders. This meeting can be scheduled by Scrum Master, however PO is the best person to invite business users and Stakeholders.
Hi Niladri, I have a questions, If Sprint review is not a meeting for demonstration by developer or user story acceptance by product owner, then in which ceremony PO accept the produce by DOD?
Product Owner is the scrum team member, Product owner should review the completion during the sprint and accept the user story. Its a practice of taking the activity as part of each story and does not required any ceremony.
As shown in 12:22 , the review meeting does not include story acceptance by the PO. Does that mean, the user story acceptance, which I assume is the same as the user story "Done" acceptance, is held latest a day before the review meeting, so that only the "Done"&"Accepted" User stories will be shown on the review meeting?
If so, then it confuses me that its mentioned at 12:25, that the user story acceptance meeting by the PO, is done after the review meeting. Can you please clarify?
User Story "Moving it to Done" is primarily job of product owner, user stories does not need to wait for the last date to get accepted, PO is the part of the scrum team, he/she can accept it as and when its getting completed and ready to verify. at 12:25 I have mentioned its "Not" a user story acceptance meeting.
Do you plan to do a video on scrum of scrums?
Good idea, I should , Let me see when time permits.
Thanks for another well described video Niladri. I have two questions here - 1. Is UAT a part of sprint cycle or it will be initiated after DevOps moves the increment to Test Box ? 2. Considering today is Sprint Review and tomorrow is next sprint planning, if new business items are identified today and need to be prioritized in next sprint, there is no time left for Grooming. Can we consider that new identified backlog items are not meant for "at least the immediate next sprint" ?
Answer 1 :
Ideally sprint execute by Scrum team, where scrum team consist of three roles, PO/SM and Dev Team. During Sprint Planning the Team commits to the number of Product backlog items, that they think they will able to complete it before Sprint Time box ends. Complete means the PBIs (Product Backlog items) should meets the definition of Done. Here Scrum Master Facilitate, Developers Develop, Testers Teste and PO verify to move the PBI to Done.
PO who owns the Product, User Who Use the Product. The Traditional UAT (User acceptance test) can not fit in, or at least I don’t suggest to adjust UAT with in Sprint Time Box.
Agile works on Trust with self-organize team members, and the end of the sprint, they should deliver shippable increment.
But, if it the case that your organization needs UAT as must and you need to do a UAT within Sprint Duration, make sure You DOD is appropriate, Don’t Extend the Sprint Duration, UAT has to be completed and fixed with in Sprint time box. Its better to identify the users who will do the UAT during sprint planning. Initiate the UAT for as on when each PBI is ready (try to adopt finish first start later approach), Don’t wait for the sprint to end. Share your teams testcases to end users to expedite the UAT.
Any PBIs that does not meets the DOD because of UAT, move them back to backlog at Sprint closure.
Many organization do have a practice of doing System Testing or Integration Testing manually or as a Part of DevOps pipeline. On those case, your sprint should be done at when the Backlog items ready to join the DevOps pipeline. UAT will be after that if required.
Answer 2
Our primary focus is to add most valuable increment first. If there are some very high importance work item evolved during review, and only grooming is sufficient to start the work, then definitely you will groom the stories during beginning of the Sprint Planning. Product Owner understand the priority of delivery items. So its better to follow the priority set by your PO.
But if there are some external dependencies may block the PBI to get completed on the sprint, don’t commit. You need to commit only those PBIs that you are sure that you will able to complete. To keep PO’s priority in mind, You can keep some buffer capacity to accommodate that later (That will create a Scope Creep), if all dependencies and risks got resolved.
Again those cases and solutions are varies on organizations and practices to maturity levels and other scenarios. The explanation mentioned above may not perfectly fits in to your case.
♥️♥️♥️♥️🙌🏽🙌🏽👏🏽👏🏽
What will happen if stakeholders are not present..can you say Sprint Review is done or not
Imtiaz, There are purpose for all the agile ceremony. Please don't conduct those meetings just for any formality. Many Team conducts these meeting because they think we need this meeting to run our project on agile. All the ceremonies prescribed by the framework has a purpose to solve, to make the agile way of development more mature.
In your case you can decide if there are no stakeholders or Business manager or Management participates on your sprint review, what you will do at that meeting, that you can not do during your sprint duration between your team.
Remember Product owner is the Part of your team.
I can't understand him its while he talks I have concentrate on his words so much I can't understand what I need to learn or keep track of