Scrum in 20 mins... (with examples)

Nice way explained

I get the odd typo but how can you ‘spring’ over this whole presentation and still upload it? I think you need to review your QA process. Perhaps your spring review needs some adjustment.

This is well explained, thanks! As I understand it, "scrum" is just a term carried over from rugby. It's not an initialization for anything ... funny how language changes though popularity and recognition—the zeitgeist! It reminds me of how Python was taken from Monty, not a snake! OK fine, so long as one knows when to shed the skin, lol.

Scrum is not about being faster. It's about being more flexible with shorter iterations called sprints. The example is badly chosen as there is only 1 person and 1 week. Scrum is supposed to have 3 roles and also several sprints. Writing all the boxes is totally distracting, especially as you write every second word wrong and the correct it many times. Consider to change that the next time. Overall the video is still useful. Thank you

Did you confuse spring with sprint repeatedly on purpose or what?

This was the video that made me understand. Thank you! :)

I enjoyed this a lot and for a waterfall PM, this gave me a high level walkthrough. Very useful. Question. How would you use this workflow for an enterprise project with 400 stories? How would you include EPICS into this workflow?

A lot of miss information in this video

Great video and gives me some insight as to what scrum is.

However, there are a few typos that made things confusing for a newcomer i.e. shouldn't it be sprint not spring? I found it very distracting to the point I had to search if spring is a term used in project management that I missed. My suggestion would be to fix this error as well as the other screen/audio differences, especially for newcomers such as myself. It might be worthwhile slowing down the narration; in parts I found it difficult to keep up with what you were saying and what was happening on the screen.

Let me start by saying, I'm NOT hating the video just pointing out a few anti-patterns. User stories is not part of SCRUM, a user story is one method of defining the work that need to be done - there are many others. In addition, it's Sprint Planning apposed to Spring Planning. There are many other terms (Project backlog vs Product Backlog, Burn down charts) and concepts here that are components of Jira and not Scrum. Scrum does not prescribe which tools to use and Jira is not Scrum, you can use Jira for Scrum but the choice is yours which tools you want to use. My suggestion is to anyone wanting to write the exam, stick to the Scrum terms and concepts in the Scrum Guide. This video does have some good guidance as far as method is concerned.

Artifact is misspelt in your video

How do product managers know what features to create?

Fantastic video. Commenting for the algorithm.

Spring, instead of Sprint ;-)

all that retyping just to still end up making typos...

I'm not sure if you're dislexic(nothing against it) but many times throuhout the video you mentioned a scrum term differently than you wrote it which makes it confusing. i.e spring/sprint review

thanks buddy

thanks mate!

Great pace and details - thanks very much!!!! Excellent presentation

Thanks for this amazinng video! Ive tried Bluehost and Hostwinds, but Cloudways with TST20 coupoon is the true money-saver.

where is scrum retrospective?

Well narrated but the spullung arrors ere innoing and make me wonder if you just slapped this together on the fly? That seems crucial to maintaining credibility, by just being able to spot and correct: sprint/spring or artifact (not artificats).. project/product.. That did detracted from it.. & was 100% distracting to say the least. ..Otherwise I did learn from it and appreciated the video!

You are the only person making videos on this without putting annoying music in the background

Could you provide new figma links? The above are not valid anymore (?) I got an error message

Great informative video!

It was very confusing when it showed 'Spring' instead of 'Sprint' on the visuals.

Thanks for the video! It's simple and very understandable

Very useful video descriped a whole stuff in a simple method 🎉

I still don't understand where the much vaunted "customer feedback" comes in. Once the sprint is done, the user story is done and goes into the burndown chart. Achievement checkmarks are put in checkboxes. Onto the next sprint. If a customer doesn't like it, it will happen weeks (?) later. Then you have the problem of "how many user complaints do we need to care?" So, an additional backlog item is generated. The backlog grows. Which messes up the velocity calculations. Eric Ries talks about a Build-Measure-Learn cycle that leads to validated learning. It is not done, until it is done, and the learning is achieved. The Scrum system is working in failure mode when there is actual customer feedback. Mangement will get all riled up. This seems like a poor method.

So much wrong its difficult to know where to start. Your opening definition "Systematic...blah blah" is just plain confusing. 16 years in Scrum (now a coach) and I've never heard that. Where you came up with that is beyond me. You seem to emphasize startups. It's used everywhere. Probably more so in Fortune 50 companies more than startups (I've worked in startups and they rarely have an appetite for process). It's not a "type of project management...". Project management infers individuals being managed...and Scrum is exactly the opposite. Teams are provided autonomy to make all of the decisions on their own, without management's interference. In my experience, project managers introduced to Scrum are lost right from the start because of the lack of "management." Scrum doesn't lead to a "potential product." That implies a big-bang release. A sprint results in an increment, which is definitely NOT an entire product. We want to emphasize incremental and iterative development...which is just an increment of the whole product. Sprint Burnup is not a Scrum artifact. In fact, the majority of the teams I work with don't use a Sprint Burnup/Burndown chart without any issues. The Sprint Review is definitely not to review what was completed. Its intended to show working software to your users and stakeholders in order to get feedback. THAT is the primary purpose. And...make any necessary adjustments to what was planned for the next sprint (are you always working on the highest priority functionality). While not completing something in the sprint is worth noting, it's definitely not why the Sprint Review exists. And that's as far as I watched...

I love this content, it helps for my capstone, thank you sir.

Now Scrum can be used widely in non software environments.

Scrum is product development which was initially created for software development.

Burndown chart is not one of the artifacts. Product increment is one of artifacts.

Scrum is not project management.

Wow, such a great content. I love it. Thank you

You made this so simple we're my teacher was dragging it out and confusing me

Great video but I'm twitching from the spelling typos. 🥴

do you now application lovevol for scrum?

PLEASE 🙏 ! make another video just like this one but for “SAFe 6.0 Safe Scrum Master” SSM. I would really appreciate 😬

I love the explanation and illustration, thanks man

This spring will be awesome :D

waterflow lol

I'm sorry, Adam. I'm having a very hard time keeping the terms straight. Your voiceover terms don't line up with your diagram and it makes it very hard to remember later.

How many times can you write spring instead of sprint?!

Great video, but you wrote "spring" like a hundred times.

The spelling errors are really annoying and I stopped watching after 2 mins, afraid that I will learn the wrong terms.😠