Scrum Sprint Review

[mabeldinga]

Best real life demo I have seen. Clear and to the point. Thank you!

[taariqh.]

Great content and insight on how ceremonies are actually ran in the real world. Great job!

[jideo.]

Hands down best tutorials I have seen online. Like a sniper; straight to the point and efficient! Thank you.

[folakeoteju]

Great Video, many thanks for making this video, the real practical video I have ever seen

[matthewhagen]

Well done Chek! I'm a PM that usually works in Corporate Universities and learning more about Agile methodology....your description and example of the meeting is very helpful as you put the viewer into the meeting room. Great Content!

[TamiloMadani]

Great video! Helps to have real life example to get a feel of the room in an efficient Sprint Review.

Speakpo at minute 02:46: User Stories agreed during the Sprint PLANNING (?)

[Oleg-mu]

But it seems that team can work very long over one user story. If each Sprint review will be some remarks from stakeholders.

[benlee]

Hi Chek, your video is fantastic as there aren't any videos showing real example. Are you able to share a real example of when and how testing in scrum is done? Such as Unit Testing, Integration Testing, System Testing to UAT.

[guneljafarli]

so useful video, so good explanation, keep going!

[matuspekar]

Great job! Did you mention that the result of the Sprint Review is a revised Product Backlog?

[tobiasfroehlich]

Hey Chek, thanks for the video! Like that you included real world footage. How long is your sprint review?

[salahuddinayubi]

Excellent explanation. Keep making these videos.

[theeyewearstore]

thank you! this has been very helpful!

[iambisola_aduloju]

Hi, what exactly do you say at the beginning as the scrum master

[pritihanda]

Soo good. Thankyou so much for this video.

[gouravrawat]

Does scrum master know any Program language.can Non IT background guy become scrum master..

[ruchikabiswas]

Sprint review is done by the stakeholders and sprint retrospective is done by the scrum team.

[CabrioDriving]

Good and interesting, but distracting music in the background.

[h.t.]

Inefficient initial delivery. Leaving at 40 secs. Maybe it’s being to cool. Have to go sorry.

[JonathanCrossland]

Scrum is bad.
The acceptance criteria, how stories are created, how estimates are done, the focus on features and lack of design, the terminology "sprint", " velocity" which is geared for speed. The increase in wasteful meetings. The awkward accountability model that results.
The opinions biases of feedback due to lack of experience with pm. The design by committee, lack of testing evaluators.

All of this can be done with a checklist and a tester.

Notice how the SM did nothing.