Sprint Review + FREE Cheat Sheet

We're looking at Scrum piece by piece. Today it's the turn of the SPRINT REVIEW.

= = = = = = = = = = = =

New for 2024: my best-ever training:
"How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout"

= = = = = = = = = = = =

-------------------
136. Sprint Review + FREE Cheat Sheet
#SprintReview #AgileScrum #DevelopmentThatPays

We’re dissecting Scrum to take a look at it piece by piece Today it’s the turn of the Sprint Review. TLDR: It’s NOT JUST A DEMO! Empirical process control. Empiricism Ring any bells Empiricism is the thing on whichScrum is founded. It says so right in the Scrum guide Here’s the definition: “Empiricism asserts that knowledge comes from experience and making decisions based on what is known.” It also goes on to talk about the 3 pillars of Empiricism: Transparency, Inspection and Adaptation. And the Sprint Review is all about those last two pillars At the end of every Sprint, we inspect… and we adapt. What do we inspect and what gets adapted Simplistically, the INCREMENT is inspected, and the PRODUCT BACKLOG is adapted.

[freedom-is-the-key]

Thank you for this video, you are so good in providing simple explanations for not so trivial things! We usually consider three things during sprint review: 1) what's done; 2) the demo; 3) what to plan for the next sprint. We've got separate meetings (once a week) to discuss backlog features, we call them 'backlog refinement'. And problems we faced we discuss on retros :)

[boriseduardosanabriaperez]

I have a very respectful Comment for You Master: It looks a lot like Sir Wiston Churchil, but you are thinner, but you have the same air, clarity, firmness in your explanal presentation and that ironic sense of humor

[ArchimedesTrajano]

4:36 I think because our is actually more informal, those seven points just naturally come up. Perhaps some projects prioritize processes over people which may be useful for audits, but it does dehumanize the team dynamics.

[azanten]

During sprint review we definitely do 1, 3 and 4 is presented. 4 is discussed during the sprint planning meeting and a separate stakeholder meeting.
During the stakeholder meeting 6 and 7 are also discussed.
2 and 5 are never discussed.

[niclin]

Is there anyone could try to answer if the point two overlaps with sprint retrospective mentioned at 3:18? I have been confused for a long time.

[gopalashetty]

sir please make videos on PMBOK guide 7edition

[niclin]

Hi Gary, I have been watching your channel from the first episode to this one. I appreciate greatly and really enjoy the videos. 4:58 you present 'a daily stand up is just a series of updates' and 'there is no adaptation', whereas the Scrum Guide states 'This is a key inspect and adapt meeting' in the section of daily scrum. And this time I would disagree with your point, because the purpose of daily scrum is not just to update the progress or do kind of status report, more importantly, is to plan the next work based on inspecting the done work. This plan should take adaptation something toward the Sprint Goal into account, even if there is rather small adaptation. So in my point of view, the daily scrum could be seemed as a very small sized inspect and adapt meeting conducting every single day.

[maloseevanschaba]

All the cheats sheet are not accessible 😭😭

[BRubin]

I'm curious about the first (1) Item "The Product Owner explains what Product Backlog items have been “Done” and what has
not been “Done”;
"
We tend to have the DEV TEAM clarify what it has done during the Sprint. This generally adds up to an approximate "done" for most of the items on the Product Backlog that were taken on during the Sprint. In the Scrum Guide the PRODUCT OWNER performs this function (more or less). Any ideas on why, or what we might be misunderstanding? Thank you

[md.sahaibmridha]

oops !
I don't understand anything,
Previous video was awesome.

[yare]

2, 3 some of 4, 5 no really any 1, 6, 7