This was so great. I spent hours sitting through boring lectures without cartoons and this made it so much easier to compartmentalize and digest. Thanks!
Didn't understand a thing in my 3 hours class, but you just made everything crystal in few minutes. you are a legend! thank you so much for the great work you r doing
I appreciated just how brief and thorough you were. In particular using the example of comparing scrum with rugby as well as explaining why the terms sprint and iteration are interchangeable. Thank you,
I plan on using your videos as discussion starters in our IT learning series. Love how your videos always provide different analogies such as the music and sports, it makes it easier to relate to the topic at hand. I love dynamic content that actually keeps the learner in mind. Less is more by making it simple, short, and entertaining. You're a great educator!
Thanks. Glad to hear you like them. I've got some new videos coming in 2023 where we make a video about each principle, so be watching for those. I'd love to hear what your team thinks of the videos!
Mark, Amazing Videos!! The topics are presented so well in just right words, music and animation. Small duration videos keep me focussed and still so informative. Great job and can't thank you enough! Also , thanks very much for the free book - much appreciate it!
Mark, appreciate your time and work on explaining what SCRUM is. It was very insightful and explained in simple terms. I also enjoyed your AGILE video and learned about the values and principles of software development based on the agreed manifesto. Keep up the good work.
Best demonstration Mark. Now I am fully clear. First I saw your agile video and now Scrum video. Both are well discussed. My huge confusion is gone and now I can easily differentiate them. Thank you.
Thank you so much ! I have been looking for a clear and simple video as I am barking upon my new role as a Scrum Master, and your videos are the best. Thank you!
I can see the value of Agile but scrum is interesting. With some scrum masters, the team spend a lot of time following the rituals rather than doing the actual work. Some stake holders get really annoyed with the meetings upon meetings but they have to attend to be seen as embracing the agile way! We have a joke: Confucius says "Talking doesn't get the rice cooked!" There is a point with which the amount of time spent on figuring out ways to improve things in the past far outweighs the benefits of the returned improvements. Sort of like a dog chasing its tail. I am only sharing this because of some scrum masters who are so rigids in their rituals that the process becomes bogged down in the mechanics of getting things done, which contradicts what being agile is all about! Great video, by the way, and thank you very much!
Love this, so easy to use and very understandable for those not familiar with SCRUM. I like the fact that it is still visually office based even though we are mostly working for home, makes me feel nostalgic ;-)
Thanks Mark! I really appreciate the human generated captions. My grad diploma lectures don't have captions, so I've been using alternative sources. (I'm a first wave covid long hauler with tinnitus.)
Appreciate your videos, nice and concise and the cartoon style helps with sharing it. Would like to see you cover some more specific agile techniques and pros/cons
Mark - I can't offer improvements because frankly, your videos are one of the top videos available today regarding the topics you touch on. I would love to know what carton/animation software you use. I hope to do some similar but not on the same topics, obviously!
*overwhelmed project management student* Ooooh, okay that makes some sense. Thanks. (We don't do software development, but I can see some value in these ideas for workshop development too...) And thanks for explaining where Scrum comes from. See, I'm a former journalism student, and it's also the word you use for when a whole bunch of journalists sort of chase someone around in a little mob to get answers, like after a session of parliament or something. I would never have thought rugby. LOL
Nice video! You might have mentioned the 5 values: Commitment, Focus, Openness, Respect, and Courage. Being a cartoon, it might have been useful to point out the accountability and responsibility of each role in a way that would be remembered for good.
Thank you Mark. Great high-level. In your future videos, could you please touch on: a) Roles (PO, PM, SM, Dev Team) and b) Scenarios (e.g. scope creep...who handles it? SM? PO? DevTeam cannot deliver the originally planned increment...what are the right options? etc...something along the lines of SM certification type of questions. Many thanks for your work.
Do your best to make sure everyone is using the same definition of success. If working code that the users can do something with is success, then make sure you don't have a few team member who think that success means producing many lines of code.
Funny you should mention that. I was working with a team a few weeks ago that basically said the same thing. Personally I prefer Kanban to Scrum, but that isn't because Scrum is bad. It is just what I see teams typically evolve to when they're really focused on becoming more efficient and effective. I would really ask the team what they feel they're getting value out of and what they don't. For example if they aren't paying attention in the daily face-to-face meetings they probably aren't getting much value out of it. If they aren't paying attention because the meetings go on too long, maybe it's an opportunity to change up the way you're doing them so they're more focused. For example instead of going around the room and asking three questions, You might work through the board and just have everybody speak to the state of each story. The team I was working with decided that the board was actually hampering them from having real conversations around the state of all the work. So they decided to forgo showing the board on the screen and just talk through what was happening and make sure that the different pairs of programmers knew what was going on in every other group. They still bring the board up from time to time, but it was a good example of a team adapting to try to make the meeting more valuable.
@@MarkShead It's also a good example of what's wrong with scrum - although only a tiny little one of many. IMNSHO there's nothing agile about scrum. - but you can of course start not doing it and instead do as self-organizing technicians would naturally do to make it more agile. There's nothing wrong with having an issue-tracker or having a special subset of it where you have tasks you focus on. The Open Source community has been doing projects like that for ages. But all the ceremonies and formalism where you can only discuss and share thoughts on the issues in a superficial manner simply forgets one of the most important parts of actually being agile: "technical excellence". ... and I think many of the original signers of the agile manifesto would agree with me.
So how does the team know which objectives are achievable within 2-4 weeks? Writing software is not like plowing a field. There are too many unkowns before starting the task. Not to mention bugs, miscommunication between team members, etc.
Very good point. I find teams usually do better by focusing on the cycle time of each story because this pushes them to deliver the smallest thing possible. The very first one might indeed take more than 2 weeks, but most teams can start delivering all the way through in 2 to 4 days if they have the support they need. Once you start delivering these very small increments, you'll probably have a better idea of how many can be done in 2 weeks. Not because you are particularly accurate on any individual item, but because the ones that go faster and the ones that go slower will somewhat average out. However, and this is where I probably differ from hard core scrum users, once you start really focusing on cycle time the value of trying to figure out how much you can do in 2 weeks goes down. You might want to still demo every 2 weeks, or do a retrospective every 2 weeks, but if every days is spent focused on finishing the next small piece of work you'll likely move beyond the value of trying to plan how much you can fit into a sprint.
Hi Mark Nice videos. Wondering that if you can put sequence of all of your videos so that it's easy to know for beginners which video to watch first and which video to watch next something like What Is Agile? Video # 01 What is Scrum? Video # 02 What is Agile Methodology? Video # 03 so on... Appreciate in advance. Thanks
i want to thank you all the videos you made , it's help me a lot . but to be honest i have been stilling i couldn't get the hole idea of it . because these days preparing for PMP , so that why i'm still need time to understand all hole idea of it
Hi Mark, your videos are very good and simple for understanding, but please, could you talk a little bit slolier, cause some of your audience might be not English native speakers, so I am. Thank you.
Thanks for your feedback. I actually had a bunch of people complain I was going too slow early on. :) If it is too fast, You Tube will let you slow it down in the settings under the gear menu.
I liked those sounds they made me really pay attention to the bulleted points, so I actually recalled the info better! Different learners ! Great videos !!
The name Scrum comes from Rugby so it isn't my analogy. It is literally why it is called Scrum--because that is what the daily meeting was named after. But I do agree it is a bit weird. Thanks for commenting.
I just have one suggestion, Please make the video more technical. I am sure the daily guy is not interested on scrum. This video was more for people who have no clue of SDLC.
I read my book, no clue. Googled scrum at various sites, still no clue. Watching your clip = a light bulb goes off in my head. Thank you, Mark!
I'm so glad it was helpful and thank you for taking the time to comment. So what do you think of Scrum?
This was so great. I spent hours sitting through boring lectures without cartoons and this made it so much easier to compartmentalize and digest. Thanks!
Didn't understand a thing in my 3 hours class, but you just made everything crystal in few minutes. you are a legend! thank you so much for the great work you r doing
Me too! He just explained everything in 8 minutes that I learned in 2 classes
I appreciated just how brief and thorough you were. In particular using the example of comparing scrum with rugby as well as explaining why the terms sprint and iteration are interchangeable. Thank you,
You are such an amazing simplifier and teacher, Mark🌹
This is it!!!!!! the best video ever...Thank you Dear Mark
The best video I watched explaining scrum so far.
I plan on using your videos as discussion starters in our IT learning series. Love how your videos always provide different analogies such as the music and sports, it makes it easier to relate to the topic at hand. I love dynamic content that actually keeps the learner in mind. Less is more by making it simple, short, and entertaining. You're a great educator!
Thanks. Glad to hear you like them. I've got some new videos coming in 2023 where we make a video about each principle, so be watching for those.
I'd love to hear what your team thinks of the videos!
Mark, Amazing Videos!! The topics are presented so well in just right words, music and animation. Small duration videos keep me focussed and still so informative. Great job and can't thank you enough! Also , thanks very much for the free book - much appreciate it!
Mark, appreciate your time and work on explaining what SCRUM is. It was very insightful and explained in simple terms. I also enjoyed your AGILE video and learned about the values and principles of software development based on the agreed manifesto. Keep up the good work.
Thanks! Glad to hear it is useful.
Best demonstration Mark. Now I am fully clear. First I saw your agile video and now Scrum video. Both are well discussed. My huge confusion is gone and now I can easily differentiate them. Thank you.
Thank you so much ! I have been looking for a clear and simple video as I am barking upon my new role as a Scrum Master, and your videos are the best. Thank you!
The scrum loops visual is really cool. Sums it up in a few minutes!
I can see the value of Agile but scrum is interesting. With some scrum masters, the team spend a lot of time following the rituals rather than doing the actual work. Some stake holders get really annoyed with the meetings upon meetings but they have to attend to be seen as embracing the agile way!
We have a joke: Confucius says "Talking doesn't get the rice cooked!"
There is a point with which the amount of time spent on figuring out ways to improve things in the past far outweighs the benefits of the returned improvements. Sort of like a dog chasing its tail. I am only sharing this because of some scrum masters who are so rigids in their rituals that the process becomes bogged down in the mechanics of getting things done, which contradicts what being agile is all about!
Great video, by the way, and thank you very much!
Your videos make learning so easy and natural- love them!
Mark, You made my the Complex to understand it in a Simpler form.
Love this, so easy to use and very understandable for those not familiar with SCRUM. I like the fact that it is still visually office based even though we are mostly working for home, makes me feel nostalgic ;-)
Glad it was helpful!
Mark ,I can not thank you enough for the fun and clear information, Subscribed already!
I'm now subscribed. Signed up and got your book (PDF). Well done mate.
I can't tell you how much I enjoyed this video and several others I watched of yours. Thank you!
So glad to hear it's useful.
You are scrumming through our comments. Love it😁
Nice presentation, the content was narratored concisely and clearly. The animation is of high quality and spot on with the context.
Hey Mark, just discovered you today and I just wanted to thank you for the way you explain things so simple and clear. Subscribed already!
That was an amazingly succinct presentation of the scrum.
Very well illustrated
Thanks Mark for explaining in simple way.. Best wishes for creating new VDOs.
Good and clear definition of terms and concepts.
Thanks Mark! I really appreciate the human generated captions. My grad diploma lectures don't have captions, so I've been using alternative sources. (I'm a first wave covid long hauler with tinnitus.)
Glad it was helpful!
Appreciate your videos, nice and concise and the cartoon style helps with sharing it. Would like to see you cover some more specific agile techniques and pros/cons
Fantastic explanation as a new agile coach
Easy to understand. The animations are helpful and appreciated.
Thank you for ALL of your videos. They help me a lot.
Mark - I can't offer improvements because frankly, your videos are one of the top videos available today regarding the topics you touch on. I would love to know what carton/animation software you use. I hope to do some similar but not on the same topics, obviously!
We use Vyond to make the videos. I'll send you some more info on LinkedIn.
*overwhelmed project management student*
Ooooh, okay that makes some sense. Thanks.
(We don't do software development, but I can see some value in these ideas for workshop development too...)
And thanks for explaining where Scrum comes from. See, I'm a former journalism student, and it's also the word you use for when a whole bunch of journalists sort of chase someone around in a little mob to get answers, like after a session of parliament or something. I would never have thought rugby. LOL
so very helpful, I'm new to this and after watching the video, I feel like it all makes sense now .
Nice video!
You might have mentioned the 5 values: Commitment, Focus, Openness, Respect, and Courage.
Being a cartoon, it might have been useful to point out the accountability and responsibility of each role in a way that would be remembered for good.
Love your videos! Will you be doing any videos explaining the difference between scrum and kanban and waterfall?
Excellent as always!!!
Amazing video... thanks Mark, my question, is Increment the same as Value in this video?
Thanks. This video was very helpful to understand Scrum.
Simple and Clear , ,thanks for the good content Mark.
Love the animations
Thanks! Are there any other topics you'd like to see covered?
Great video. I like the cartoons..
Thank you 🤗
Do you use toonly? Great video, what software did you use?
Quite informative
Really appreciated
I really like your videos and the way things are made understood...Keep it up Sir
Great presentation. Ez to understand
it was great! thank you so much. if you had explained more about the connection between every increment and sprints, it would have been better.
this is a very good video,sooo informative.keep them coming.... Great Stuff Buddy
Thank you Mark. Great high-level. In your future videos, could you please touch on: a) Roles (PO, PM, SM, Dev Team) and b) Scenarios (e.g. scope creep...who handles it? SM? PO? DevTeam cannot deliver the originally planned increment...what are the right options? etc...something along the lines of SM certification type of questions. Many thanks for your work.
Thanks for the comments and suggestions!
Great video! Very well explained
Thanks sir you make my day ❤️
Excellent explanation
Thankyou Mark This was so helpful
Hey Mark, just discovered you today and wanted to thank you for all these succinct videos that gives a great overview and explanation of things!
Awesome, thank you!
Love your channel mark, this is great work. Appreciate the effort.
Thank you Mark, it was so beneficial for me.
what the difference between sprint meeting and sprint planning meeting ?
Extremely useful. Thanks.
excellent video, thank you
How have you developed this awesome video ? Can you share the details.
Varun - These videos are done with Vyond.
Mark. What would you suggest I do on my first day with my team?
Do your best to make sure everyone is using the same definition of success. If working code that the users can do something with is success, then make sure you don't have a few team member who think that success means producing many lines of code.
beautiful video ❤
very good!
Thanks! And thanks for taking the time to leave a comment.
Dude awesome video mark thank you for the breakdown!!
Honestly....thank you. I subscribed as well
I love your videos. They really help me!!!
Great presentation.
great stuff Mark
You are great!
Could you reflect on the situation where the output from the reflection on how to become more efficient is: "less scrum" ?
Funny you should mention that. I was working with a team a few weeks ago that basically said the same thing. Personally I prefer Kanban to Scrum, but that isn't because Scrum is bad. It is just what I see teams typically evolve to when they're really focused on becoming more efficient and effective.
I would really ask the team what they feel they're getting value out of and what they don't. For example if they aren't paying attention in the daily face-to-face meetings they probably aren't getting much value out of it. If they aren't paying attention because the meetings go on too long, maybe it's an opportunity to change up the way you're doing them so they're more focused. For example instead of going around the room and asking three questions, You might work through the board and just have everybody speak to the state of each story.
The team I was working with decided that the board was actually hampering them from having real conversations around the state of all the work. So they decided to forgo showing the board on the screen and just talk through what was happening and make sure that the different pairs of programmers knew what was going on in every other group. They still bring the board up from time to time, but it was a good example of a team adapting to try to make the meeting more valuable.
@@MarkShead It's also a good example of what's wrong with scrum - although only a tiny little one of many.
IMNSHO there's nothing agile about scrum. - but you can of course start not doing it and instead do as self-organizing technicians would naturally do to make it more agile.
There's nothing wrong with having an issue-tracker or having a special subset of it where you have tasks you focus on. The Open Source community has been doing projects like that for ages.
But all the ceremonies and formalism where you can only discuss and share thoughts on the issues in a superficial manner simply forgets one of the most important parts of actually being agile: "technical excellence".
... and I think many of the original signers of the agile manifesto would agree with me.
Well done 😊
Can you make videos explaining the PMBOK guide please?
I'm probably not the most knowledgable person about PMI topics beyond some training I did with them two decades ago. Sorry. :(
So how does the team know which objectives are achievable within 2-4 weeks?
Writing software is not like plowing a field. There are too many unkowns before starting the task. Not to mention bugs, miscommunication between team members, etc.
Very good point. I find teams usually do better by focusing on the cycle time of each story because this pushes them to deliver the smallest thing possible. The very first one might indeed take more than 2 weeks, but most teams can start delivering all the way through in 2 to 4 days if they have the support they need.
Once you start delivering these very small increments, you'll probably have a better idea of how many can be done in 2 weeks. Not because you are particularly accurate on any individual item, but because the ones that go faster and the ones that go slower will somewhat average out.
However, and this is where I probably differ from hard core scrum users, once you start really focusing on cycle time the value of trying to figure out how much you can do in 2 weeks goes down. You might want to still demo every 2 weeks, or do a retrospective every 2 weeks, but if every days is spent focused on finishing the next small piece of work you'll likely move beyond the value of trying to plan how much you can fit into a sprint.
Thank you Mark!
Very effective and educational
Hi Mark
Nice videos. Wondering that if you can put sequence of all of your videos so that it's easy to know for beginners which video to watch first and which video to watch next something like
What Is Agile? Video # 01
What is Scrum? Video # 02
What is Agile Methodology? Video # 03
so on...
Appreciate in advance.
Thanks
This is probably a reasonable sequence to start with:
ruclips.net/p/PLBUu5aGDLKnbeEx8U-5r436bw6p9wv1rS
@@MarkShead Thanks
Great stuff
Great job. Thank you
i want to thank you all the videos you made , it's help me a lot . but to be honest i have been stilling i couldn't get the hole idea of it . because
these days preparing for PMP , so that why i'm still need time to understand all hole idea of it
Glad they are helpful. How is your PMP preparation going?
nice, keep it up
Can you do a video of scrum vs kanban? 😊
Is this training based on the Scrum Guide Nov 2020?
It is pretty high level so I don't think you'll find anything that really aligns it with any particular version of the Scrum guide.
Thanks..big help in my class
Awesome 🌟
Great video :) Feedback: Your microphone (or my headset) could be better.
Great job, i gave it to you
🤔 So scrum is shorter version of waterfall method to produce the product immediately to be scrutinized until it is made perfect then repeat.
you are a genius, man))))
Very clear
Hi Mark, your videos are very good and simple for understanding, but please, could you talk a little bit slolier, cause some of your audience might be not English native speakers, so I am. Thank you.
Thanks for your feedback. I actually had a bunch of people complain I was going too slow early on. :) If it is too fast, You Tube will let you slow it down in the settings under the gear menu.
very good
IN the end is all about common sense and managing.
Really useful videos that you make. Thanks a lot! But there's one little thing: I found those sounds at 1:01, 1:14, 5:37 a bit annoying
Noted! Thanks for the feedback.
I liked those sounds they made me really pay attention to the bulleted points, so I actually recalled the info better! Different learners ! Great videos !!
Thanks soo muchh
nice
Really good video, poor sports analogy really threw me off.
The name Scrum comes from Rugby so it isn't my analogy. It is literally why it is called Scrum--because that is what the daily meeting was named after. But I do agree it is a bit weird.
Thanks for commenting.
@@MarkShead I really appreciate your video as it helps me to understand scrum better, which appears to be part of a project management process.
I just have one suggestion, Please make the video more technical. I am sure the daily guy is not interested on scrum. This video was more for people who have no clue of SDLC.
🗽
This is why all software developed nowadays sucks and it is buggy.
What is scrum? The stupidest possible way to run software development.