Learn SCRUM in Under 10 Minutes (HD - PRO)

[arbassiddi]

Hamid, Thanks for the great video! It is very Clear, Concise and Correct (easy to understand). I found it helpful and a perfect starting point. Thank you,

[rajemon]

Good information, but the music is disturbing. Would have been nice without the background music.

[tejten1]

excellent video

[LMPereira3398]

Great video. I found it to be informative, tothe point and helpful. We're applying SCRUM in my organization! :)

[hooversom]

I do not call 8 minutes Short :\

[SuperMarcBot]

Scrum destroying products since 1995

[veekay304]

Excellent..!!

[wishkah256]

Great video!

[TheAerodynamicFrog]

lol, i thought this was a rugby video :P

[redspot357]

I think your video is extremely dangerous, because you miss central concepts like the sprint retrospective. And you misuse some of the tools and show disturbing graphics. It is very nice from a graphical point of view, but it is dangerous in concerns of the information.

[3RCable]

Thanks for the video

Would you please change the back music it's stressfu :)

[jsakakib]

Can you tell me if you contracted a partner to help you produce this video or you did it by yourself? Congratulation for the quality of the video.

[aidilgoh]

Bases on the vid, SCRUM is a framework, and theres no hard n fast rules for it.

So the basic idea is to get a complete list of features> break down to bitesize chunks> feast on those chunks in sprints (cleanup the crumbs/bugs as you go :) > repeat till done. Am I thinking straight here?

I personally have experienced breakdowns in our standups, so I understand where Hamid is coming from suggesting that the standups can be omitted if there is another better way.

[gregreynoldsjr]

I liked the pace and presentation of the video. However there are three problems I feel compelled to point out, and I hope the author can remedy.

1. Every sprint is potentially releasable. Requiring 4+ per release is wrong.

2. Proposing 1 or 2 bug sprints is a bad idea. Defects are a form of technical debt, and should be worked off when found, not accumulated.

3. Suggesting that holding daily scrum could "lower morale and backfire" is just wrong, you're running your standup incorrectly

[hshojaee]

1. While the goal of each sprint is to have a ship-ready product, it would be foolish to PLAN only 1 sprint per release.

2. Defects that are found during the creation of a new feature should always be dealt with immediately. However, you can not simply drop everything to address defects from past released products. You would never finish a sprint that way.

3. You should listen to the daily standup part again. The video suggests that you could omit the daily if you have better communication.

[michaelstum]

Excellent!

[funkymonk42]

Great video, thanks! I'd like to request you make a companion video where you walk through that process in OnTime! From nuts to soup. I use OnTime, but would love to see that sample scrum demonstrated.

Thanks

Ben