YDS: Why is Your Scrum Teams Sprint Review So Terrible?

Why is Your Scrum Teams Sprint Review So Terrible? Let's explore the options this situation presents. This and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.

Professional Scrum Trainers Todd Miller and Ryan Ripley built this course to help those interested in Scrum get up and running quickly using the Framework. They've partnered with Daria Bagina from ScrumMastered to bring valuable materials and guides to the course.

Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems.

For more information about Agile for Humans, visit:

For more information about Daria and ScrumMastered:

#ScrumMasterTraining #Scrum #ScrumFramework #ScrumMaster
#HowToBecomeAScrumMaster #ScrumMasterCertification #AgileForHumans #FreeScrumMasterCourse #FreeScrumTraining

[AlexandrosNtalachanis]

And here I am, asking, what could be good for a Sprint Review? How do you propose to leave the demos behind and make it more value-driven?

[Elmusiico]

“Other meetings in the week where things are talked about in pockets (silos).” 100% agree, love this SR focused videos.

[MyGodisfaithfulever]

Thanks Todd and Ryan. Looking forward to the episode on right format.

[Rekettyelovag]

One of my biggest headaches is clapping. If I remember correctly "DON'T CLAP" is in the PSM 1 training as this isn't an entertainment show, people rather should give feedback. When I tell this to them, they are super offended and upset. And now Microsoft added clapping button to Teams and people use that during Reviews and now I'm just...whatever man.

[ZacharySkaggs]

In AWC recently we were discussing reviews, and one of our members mentioned how much information there is on how to have effective sprints, retros, backlogs, etc...but there are very few resources on effective reviews. I thought this was an interesting (and rather true) observation. We also discussed that as the company/product scales and the number of stakeholders increases/moves up the corporate ladder, reviews seem to become simpler over time. Execs with lots of products don't seem to have the time for hours and hours of review meetings for things that aren't major updates, and the things that are major updates there is usually a push for separate meetings to "launch planning" sessions to coordinate all the other business functions around the release. I wonder what y'all's teaches you about reviews as the scale of the product/org changes, l and what resources you'd point people to for effective reviews? As an example, Esther Derby's book on Agile Restrospectives...is there something as comprehensive around the theory behind reviews?

[madzero]

You guys must have watched the Sprint review of one of my teams on how not tto on thuis one. I like the retrospective format idea. Been also trying my PO to get some liberating structuren in the review for more interactief, but hé thinks Thatcher doesn't work in a professional setting. Hé with little faith. So thanks for the ideas here.

[tomaszniemiec]

🛫 I would say the most problematic thing about my current team's review is the lack of feedback we get, and that our reviews serve more as a showcase of done features (with some addition of backlog current state and plans). I'm curious to your view on this.

🛬 I couldn't agree more with everything you both mentioned, while I would like to get your view the root causes of each of those antipatterns. Similar to how Todd explained the lack of conversation happening on the sprint review to be related to other meetings before it. So another thing could be: the team is not showing a live presentation of features, but recording them as video, because there is a problem with stable environments. Another example: the team is not updating their backlog, because they just need to know if they are 'on track', not customer feedback.