Man! you are awesome! every new video I watch from your cards are better than before! Im learning a lot with you! I hope you can keep creating more relevent content! thank you so much!
Hi. I was recently promoted to product owner at my company. If not during the sprint review, when do you suggest that demoing new functionality or user acceptance testing should occur? Is that just a separate meeting? I don’t know if you explained this in the other video you mentioned, as you pointed to the sky, but there was no link at the top of the screen.
Yes the acceptance testing or demoing functionalities is done before the Sprint Review. The developers can sit together with the user to do it. I think the link is not visible on television but it should be available on phone / mobile phone. Anyway, this is the video on “increment” th-cam.com/video/vXjJ58iksJQ/w-d-xo.html
Great video! "Sprint Review provides transparency about the outcome of the Sprint and also the current market.” That's a clear reason why Sprint Review is not just a demo session, right?
Hi Joshua , that's absolutely great explanation about sprint review , it would change my mind and spread this knowledge into my teams as well , but there's 1 thing that I need to ask , what if in 1 sprint cycle the developers couldn't made some deliverable product until the end of the sprint? maybe there's an obstacle or impediment occur during the sprint, what outcomes should we discuss on Sprint Review ?
The Scrum team and the management should live the Scrum values. Ask everyone in your company to watch this video th-cam.com/video/7fXXRCeJ1Ss/w-d-xo.html Be courageous to tell the audience why a releasable increment can not be delivered and why there isn't any outcome. The audience should respect and support the Scrum team. Afterwards define improvements during Sprint retrospectives so this won't occur again in the next Sprint.
Thanks for the sub! I used to blog here -->www.scrum.org/resources/blog?uid=168 But now I just focused on vlogging and podcasting. My podcast is --> podcasts.google.com/feed/aHR0cHM6Ly9hbmNob3IuZm0vcy8xYzJkY2VjNC9wb2RjYXN0L3Jzcw== But still ... I vlog more than podcasting.
Man! you are awesome! every new video I watch from your cards are better than before! Im learning a lot with you! I hope you can keep creating more relevent content! thank you so much!
Oh Joshua, you're getting better and better 😁
Thanks for your hard word Joshua!
Thanks for watching 🙏 Don't forget to spread the video around. 😀
Hi. I was recently promoted to product owner at my company. If not during the sprint review, when do you suggest that demoing new functionality or user acceptance testing should occur? Is that just a separate meeting?
I don’t know if you explained this in the other video you mentioned, as you pointed to the sky, but there was no link at the top of the screen.
Yes the acceptance testing or demoing functionalities is done before the Sprint Review. The developers can sit together with the user to do it.
I think the link is not visible on television but it should be available on phone / mobile phone. Anyway, this is the video on “increment” th-cam.com/video/vXjJ58iksJQ/w-d-xo.html
Great video! "Sprint Review provides transparency about the outcome of the Sprint and also the current market.” That's a clear reason why Sprint Review is not just a demo session, right?
That's right @Takuma. Sprint Review should not be about demoing but reviewing the market condition.
Hi Joshua , that's absolutely great explanation about sprint review , it would change my mind and spread this knowledge into my teams as well , but there's 1 thing that I need to ask , what if in 1 sprint cycle the developers couldn't made some deliverable product until the end of the sprint? maybe there's an obstacle or impediment occur during the sprint, what outcomes should we discuss on Sprint Review ?
The Scrum team and the management should live the Scrum values. Ask everyone in your company to watch this video th-cam.com/video/7fXXRCeJ1Ss/w-d-xo.html
Be courageous to tell the audience why a releasable increment can not be delivered and why there isn't any outcome. The audience should respect and support the Scrum team. Afterwards define improvements during Sprint retrospectives so this won't occur again in the next Sprint.
Excellent.. Subscribed.. In case you also do write blogs, I would like to know the link.. I work as a Scrum Master too.
Thanks for the sub! I used to blog here -->www.scrum.org/resources/blog?uid=168
But now I just focused on vlogging and podcasting. My podcast is --> podcasts.google.com/feed/aHR0cHM6Ly9hbmNob3IuZm0vcy8xYzJkY2VjNC9wb2RjYXN0L3Jzcw==
But still ... I vlog more than podcasting.
Is Sprint Review at your workplace only about "demoing" functionalities delivered? Well ... that's not what Sprint Review is all about.
If you did not watch that video, click on bla bla bla and watch that video. and after watching this video...
you are more knowledgeable than before watching this video 🙌
😂
Thanks Joshua 👍
You are welcome. Thanks for watching 🙏