YDS: Where Are All of the Scrum Sprint Review Formats?

Where Are All of the Scrum Sprint Review Formats? 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

[Flyrev]

Here's a thank you that will help Todd stay caffeinated at his next Sprint Review!

[b.a]

Love the questions Ryan pulled and adding ebm in order to take it further in inspecting and ADAPTING our artefacts and commitments linked to those artefacts
I for one an a big fan of working with LStrctures such as impromptu networking to clarify expectations and using sprint bazzsar / shift and share to have the participants play with the product and share insights with a ux fishbowl structure.
Thanks Ryan for listing those questions
Great helping reminder

[tweetymr]

One of the last cents inspired me the most "If you don't get / discus feedback and re-prioritize the backlog, you basically doing waterfall" Thanks for the good input!

We have a 1h Sprint Review for two projects in a 2 week sprint.
That is basically enough EXCEPT if someone asks questions and brings in new ideas.
The entire team just cut that person and says: "this is not the place to bring in cosmetics and weird wishful thinking".
But I think IT ACTUALLY IS. Is has just to be clear, if those wishes needs to be implemented, the backlog needs a re-priorization and there has to be NOT A SINGLE "PARALLEL" Story afterwards.
Otherwise you end up with 500 Stories and all have the same urgency (NOW)

[JoseMendez-okbc]

How should the interaction be between an IT Product Owner and the Business Product Owner?

[hugodimadrid]

I have a big question, literally . main topic dev manager and SM relationship.
How should I work with a dev manager if I am a scrum master?
How does it fit the dev manager in scrum ?
how to avoid overlap with SM deciding who does what ?
is it recommended?
what would be their responsibilities as dev manager?
and how this position fits with every member of the scrum team(PO, SM, Development Team) example collaboration, resolving conflicts, improving, etc ?

[BaerTheBlader]

Please if someone can recommend a good video training on how to conduct an effective sprint review. We have all the stated problems. Our primary stakeholder just asked me to shorten the meeting from 1 hour to 30 min. They rarely have feedback or questions, and they don’t want me going over the backlog in that meeting.

I am also strongly discouraged from getting user feedback at all. My leadership has recently told me,

“Remember who is paying for this project. They are the ones you are ultimately building this for, not the end users, so if they ask for something, do it”

And

“No, I don’t think you need to get feedback from the end users. Steve Jobs never asked for feedback. He said that “customers don’t know what they want, I tell them what they want.”

So I am not really sure how to right the ship, so to speak. We don’t even have a Scrum Master anymore that I can ask, because he was too expensive. They say that we are an experienced enough team now that we don’t need it.

[Brettive]

So can we get this conversation as a format?

[tomaszniemiec]

🛫 Hmm, I didn't know there are standard formats for the Sprint Review, but rather goals, and we want to accomplish by having that meeting. So just as a reminder, the meeting's goal is to get feedback on what we've built during the sprint, the outcomes of the sprint, from our stakeholders, which can provide valuable feedback to the team, from customers to the CEO. It is not a demo session. And as a result, we should have more insight into how to direct our efforts next, i.e. collect updates for the team's backlog. It is also a good spot to update everyone on what (direction more than stories from JIRA) is coming from the team is upcoming, short period.
🛬 Exactly my thoughts were going into the same direction, while I like how Todd focuses on the 'product' in describing the thing we assess on the meeting – cool. The templates are not bad, but like you both said, you need to understand the goals for that meeting and reasoning we do it, and then come up or use formats that work for you. I would love to work at a company, that gets it one day ^^.