Love how you are clear and to the point! And how you share actionable insights that encourage not just sticking to the book. I recently saw few videos from another channel with much more views... of an eye-rolling thickly accented lady who apparently seems to have 'mastered' scrum, but is sadly not able to say anything useful other than just beating around the bush. Glad I stumbled upon your channel!
@MountainGoatSoftware10 ай бұрын
Thanks. I try hard to keep my videos short and to the point.
@Praizion8 ай бұрын
Haha! You were just checking there at the end Mike? I see what you did there! Brilliant. Ken and Jeff make it clear in the guide, but I wonder where the term demo came from? A different framework? Anyway, not important. 😂
@MountainGoatSoftware8 ай бұрын
I think it's just easy to call it a demo since that's the most obvious aspect of the meeting.
@MountainGoatSoftware10 ай бұрын
If you need help with creating a sprint review agenda that goes far beyond just a demo, I've got a new video out that will help: kzfaq.info/get/bejne/a8maY92W2qnWgmw.htmlsi=b_78Km5SXTt8KL2M
@sandraganguly49010 ай бұрын
I loved the phrase conversation not presentation that really resonated with me. I often have seen these run as PowerPoints and demos without much conversation at all never mind feedback - so good tips on how to guide towards a conversation based sprint review.
@MountainGoatSoftware10 ай бұрын
Glad you liked it
@jyotsnasharan961510 ай бұрын
Thank you so much for posting mentorship videos!
@MountainGoatSoftware10 ай бұрын
You're welcome.
@Saumil510 ай бұрын
Wonderful Thought! Your videos are always excellent 👌👍
@MountainGoatSoftware10 ай бұрын
Thank you very much.
@jonathangarrison10 ай бұрын
Love these videos! Such good advice and guidance!
@MountainGoatSoftware10 ай бұрын
Thanks for watching!
@rapra4024Ай бұрын
Sir , who record feedback in a sprint review? PO or a Scrum Master?
@MountainGoatSoftwareАй бұрын
I think of that as the product owner's responsibility since they'll be the main user of the feedback notes. However, product owners are usually way too busy during the review to also be taking notes. So I coach the Scrum Master or a team member to offer to help out. Almost every team has someone who is super detail-oriented and is quite willing to help out. A lot of times, a tester is the most organized and will do the best job at taking those notes.
@rapra4024Ай бұрын
@@MountainGoatSoftware Sir, PO acts like a stake holder or the end user in a review and provides feedback along with the stakeholders.Scrum master shall record it and take these as inputs for retrospective.This is what our agile coach guides us, Please correct me if my understanding is correct.
@MountainGoatSoftwareАй бұрын
@@rapra4024 In some organizations, the PO is a recipient of the demo given during a sprint review. In others, the PO is a more engaged participant and may give the demo. I'm sure your coach has recommended the right approach for your organization.
@emilykalinowski60559 ай бұрын
If your team creates, manages, and maintaines over 40 web applications and counting, would sprint reviews still be conducted this way? Would there be certain aspects that would need a larger focus or different items that would need focusing on?
@MountainGoatSoftware9 ай бұрын
Most teams in that situation do feature reviews for anything small. As a feature is done, it's demonstrated to the 2-3 people who need to see it / requested it. Often there will be a final review for the main things done. The smaller things (already done in feature reviews) will be mentioned but no feedback sought from that audience. And, to be clear, when I've seen teams responsible for that many products, they definitely don't touch all of them in a given sprint. One or two will be 80% of the work. The remaining 20% of the sprint effort goes to a handful.
@BugTheRoot6 ай бұрын
I have been banging this drum for a while now. The trend seems to have taken off after a certain scaled agile model became popular. I've always tried to not only discuss what we successfully completed for the PO and customers, but also what we couldn't complete (with a very brief mention of what stood in our way). I have considered this output from Review as Input for Retro. Thoughts?