Let me add if I'm not mistaken at this meeting I guess in the video there is a review of the "roadmap" to see if we are on track or are we going to have to adjust something. I think it's important to know why stakeholders or users need the initiative or feature or whatever.... Maybe important to check the next feature or US for the next sprint (so the devs have been able to write some notes about missing information, understanding, etc to resolve, to put light and reduce uncertainty).
Your thanks has been passed on to the team and they are glowing! We are so grateful for your words! Anyway, good luck with your career change. Pretty sure you're going to love it and will soon start wondering how anyone got anything of value delivered in 'the old ways'.
Just transitioned into scrum. Although I am still in apprenticeship this was very helpful in me gaining a better understanding on what a Sprint Review looks like in simplest terms. Thank you so much
Planning on giving our PO some advice on how to make our Sprint Review better, looked up "sprint review meeting" to look for on-hands examples not just theory, got this video as my first result. Awesome! It really helps a lot!
This video is INSANELY helpful! Thank you for providing this, there's so much more value created by describing, showing, and then breaking down this content. A whole chapter on this wouldn't be as meaningful. Thanks!
Thank you for the nice words, Sourya Majumdar 🙏 Currently we are working on a video illustrating the importance of "A Real Stakeholder". A Real Sprint Planning (and a Real Sprint Retrospect) are also on our Product Backlog but it's a bit more complex to keep these real and relevant for all our viewers. We're definitely going to experiment with these though!
Thank you for sharing this! I have learned a lot from this. I just recently began learning about Agile and Scrum. This video is the "review" after a Sprint has been complete, right? Do you have a video of a "Daily Scrum"? A sample of the daily meeting the team has? Kiitos!!
Indeed, this review was done at the end of a two-week Sprint. Where we inspected, together with the stakeholders of YLE, what the team managed to complete, where the obstacles are etc.. Using this input to collaborate with the end user on how we can maximize value in the upcoming sprints. We do not have a "real daily" yet sorry. It's good to know that you would find it valuable, I'll discuss the priority with our Product Owner.
It is very helpful! Thank you! I see that some Scrum Masters prepare a power point for Sprint Review putting stats such as velocity, throughput, bugs, satisfaction, and so on. What do you think about it? Honestly, it seems more a project management thing. Which metrics should the stakeholders know?
Stats can be very useful in a review meeting ... IF those stats tell you something about the desired outcome! I don't have the context of your environment but I haven't seen any situation where 'velocity' or 'throughput' tells you anything about the desired outcome, so I wouldn't show them in a review meeting. Personally, I would show these metrics only in a Retrospective and ask the team if these values are in line with what they expected (any answer is accepted: it's about the conversation, not the number). The other metric you mention, the 'satisfaction' metric, sounds very much as a desired outcome metric. This one can be very useful in a review meeting. This metric will likely give you information that could help your team update the product backlog to maximize value. I would even recommend experimenting with a 'statistics only' review: customer satisfaction, usage numbers of our product, end-user time per session, most popular features, never used features, etc. Whatever makes sense in your context that informs you about the outcome you are trying to achieve. ~ Bram De Block, Global Agile Lead @ Skyline Communications
Currently we are working on a video illustrating the importance of "A Real Stakeholder". A Real Sprint Planning (and a Real Sprint Retrospect) are also on our Product Backlog!
Gotcha, thanks. We work with a 30 minute time window for three teams. We typically don’t get much feedback then. But I showed this video to my team today and they came up with some great ideas to open up other lines of communication with our users. So thanks a lot!
