Thanks for all the support on this video. As one of my first videos on this channel, I know there are heaps of ways it could of been improved, and thanks for all the feedback which I am taking note of!
Generally an ok video, but there are a lot of mistakes in here, not just spelling errors. Just a couple examples from the first couple of minutes: the burndown chart is a tool but it is not a scrum artifact, the 3rd artifact is the increment, or working iteration of software. Additionally, the scrum guide outlines 5 events: the sprint, sprint planning, daily scrum, sprint review, and sprint retro. This video gives a decent baseline, but watchers should be aware that there are inaccuracies throughout.
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.
He also spelled “artifact” incorrectly and spelled “sprint” correctly at least a few times. I’m guessing he’s dyslexic, but does it really matter if you understood the video?
As someone who has learnt enough to start building larger projects, this is very useful. I'd like to get a job in web dev at some point, but most of my projects in the past have started out with me immediately typing out some code and moving on from there. People talk about the importance of planning, but no one has laid it out quite as well as this video. I'm just about to start a new project, so I'll see if I can put this into action.
Best tutorial I have seen in 2024, in general. Thank you so much for sharing. It was super well explained, the resources are top notch... This will literally help me nail an amazing job I have been pursuing for several months now.
00:00 Scrum is a project management method for startups and software development. 02:19 Scrum methodology involves three roles, three artifacts, and three ceremonies. 04:48 Scrum methodology is a more efficient way of creating a project compared to traditional waterfall development. 07:27 Understanding user stories and sprint planning 10:15 Scrum methodology for software development 12:44 Create pricing calculators using scrum methodology 15:08 Creating a project backlog with three main features for pricing calculations. 17:37 Creating a sprint using a Trello list Crafted by Merlin AI.
What I have learn in this videos is What is SCRUM, How we can use that method for Our projects and This Man is bad at Spellings(Jokes apart), By the way very good video and very helpful.
Please don't spread misinformation. Scrum is not an acronym and doesn't stand for what you seemingly made up to be. I would love to see the source where you got that from. It actually comes from the term Scrum that's used in rugby. The team comes together in what they call a scrum to work together to move the ball forward. In this context, Scrum is where the team comes together to move the product forward.
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.
Awesome video, thank you! This was a great primer for those unfamiliar with SCRUM/Agile processes. I don't think SCRUM is an acronym, it was named so due to a formation in rugby, called "scrum". The formation was used to restart play in the game, which highlights the collaborative features in SCRUM. Again, solid video overall
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.
Good overall explanation, but the errors are very confusing and are a huge distraction when trying to watch the video. Is it possible for you to remake this video without any errors to make every thing as clear as possible?
Agree. Having the word "Spring" instead of "Sprint" throughout the video multiple times (even after many cut-and-pastes) without catching the error made it look like a legitimate scrum term. No offense but it's a bit sloppy when the video generally had good content otherwise.
@user-zf1pl6wj4n What gives you that idea? Genuinely curious. Especially, since the user's homepage features a video with the same person show in this video that directly references his user/site name, so I was just wondering if there was any basis to this assertion that watchers should be aware of?
I wish there was consistency in term usage and proper attention given to presentation because the spelling errors make it unprofessional and confusing.
The three artifacts are Product Backlog , Sprint backlog and Increment. I highly doubt that Burn-Down Chart is an artifact. I would say it is definitely a tool for measurements, not an artifact
Although the burndown (or burnup) chart is not an official scrum artifact, many teams use it to communicate and track progress toward the sprint goal during the sprint
This video as good as it look and can see the effort you put in it, From the beginning display a lot of miss information it does has a lot of views so will be a good idea to update it with the correct info.
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.
For start-ups, the most effective agile Scrum tool that is also affordable would depend on various factors such as team size, specific project needs, and preferred features. However, tools like Trello, Asana, and Vabro are often considered effective choices for start-ups due to their user-friendly interfaces, customizable workflows, and reasonable pricing plans. These tools offer essential Scrum features such as backlog management, sprint planning, task tracking, and collaboration functionalities, making them suitable options for start-ups looking to implement agile methodologies without breaking the bank.
Hi, I have a question, according to your video the third artifact is a burn down but according to the scrum guide it is an increment. Can you explain please?
Very nice overview of the topic. Incompitence around me at work sometimes makes me think maybe I don't know how to manage a project, but this video made me sure that I know what I'm doing! The FigJam boards are really great, trying them out with my next project
Not clear on something -- in a regular project management scenario, you have the product, but you also have things that come before and after the development: requirements gathering, configuration, implementation, training, beta testing, regression testing, and so forth. Would these all be separate SCRUMs or do you include these phases in the SCRUM planning for the product. If they're all separate, then I don't understand how this method saves a company any time.
Traditional, Traditioanl. Artifact, Artificat. These kinds of mistakes make me question other information in your presentation. Are you using spring and sprint interchangeably or are they 2 different things?
Excuse me, the burn down chart is not an artefacts in scrum, its only a complementary tool for managing work in a team. The last artefact un scrum is the increment.
7:16 Before we address the product backlog item you mentioned, such as the login feature, at what point are we discussing the overall system architecture decisions?
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.
You begin with a MVP as lean as possible. For Example Citibank creating a mobile app for customers. The Customer Service discuss the customer feedback with the product owner. The product owner makes a product backlog for the scrum team to improve customer experience. And this keeps on repeating. After a few years the Citibank is a full fledged app with added investment, insurance possibilities
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!
Hi I have been looking to move IT sector from mechanical manufacturing at the age of 36 is that possible to changover ? If possible can I survive IT sector ?
Can you fix some of your spelling I wanted to promote this to my team to watch but it should be SPRIT not spring and some of the project and product confusion This is very informative and I love the information but some of the mistakes make it so I can’t share or recommend to other people
To be more accurate: it is neither “spring” nor “SPRIT”. “Sprint” is the right term. I think you have a good point on spelling issues which might confuse the ones new to scrum. Another typo with “artificats” which should be “artifacts”. Overall, a cool video fails to be perfect, so close though.
Thanks for all the support on this video. As one of my first videos on this channel, I know there are heaps of ways it could of been improved, and thanks for all the feedback which I am taking note of!
Thank you I have learned a lot from this video
Even though it was one of the first videos, there were mistakes, it is a great resource. I learned a lot from the video. Thanks a lot
Generally an ok video, but there are a lot of mistakes in here, not just spelling errors. Just a couple examples from the first couple of minutes: the burndown chart is a tool but it is not a scrum artifact, the 3rd artifact is the increment, or working iteration of software. Additionally, the scrum guide outlines 5 events: the sprint, sprint planning, daily scrum, sprint review, and sprint retro. This video gives a decent baseline, but watchers should be aware that there are inaccuracies throughout.
Thanks !
According to the scrum guide, absolutely true!
Exactly... I thought it was just me, it almost seemed like I was going nuts 😂
scrum withou the best tool is nothing .... ?P?
Much better than the 9 hour lecture we had in uni
Exactly, I've exam on tuesday
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.
100% agree, thank you for pointing out those details Riccardo.
This spring will be awesome :D
1-2 weeks seems like an unusually quick spring D:
Very useful. I love especially the practical part where you show it by example and not just theory.
completely agree
just started with Scrum training today and this video really defines the how-to's and what visually effectively. thanks for this
Great video, but you wrote "spring" like a hundred times.
He also spelled “artifact” incorrectly and spelled “sprint” correctly at least a few times. I’m guessing he’s dyslexic, but does it really matter if you understood the video?
also burn out, wrote burn own
@@username00009 the fact that he wrote Artificat absolves him of any wrongdoing
@@Chefrondon burndown i think he was saying idk
And kept saying ”waterflow”
It was very confusing when it showed 'Spring' instead of 'Sprint' on the visuals.
I thought it was just me, waiting for him to correct it.. 😅
I really liked that you included a real world example to solidify the concept. Thanks for the great content.
As someone who has learnt enough to start building larger projects, this is very useful. I'd like to get a job in web dev at some point, but most of my projects in the past have started out with me immediately typing out some code and moving on from there. People talk about the importance of planning, but no one has laid it out quite as well as this video.
I'm just about to start a new project, so I'll see if I can put this into action.
halo world
This is by far and I mean it, by far the best video that clearly explain what Scrum master is.. The best
Thanks for the video! man, this is the simplest, intuitive and the best video I have seen on Agile. Great storyteller!!
Best tutorial I have seen in 2024, in general. Thank you so much for sharing. It was super well explained, the resources are top notch... This will literally help me nail an amazing job I have been pursuing for several months now.
Best content i've seen on SCRUM. Simplified, yet detailed. Thanks
U haven’t seen anything bro.
Simplified, detailed and wrong in so many places.
00:00 Scrum is a project management method for startups and software development.
02:19 Scrum methodology involves three roles, three artifacts, and three ceremonies.
04:48 Scrum methodology is a more efficient way of creating a project compared to traditional waterfall development.
07:27 Understanding user stories and sprint planning
10:15 Scrum methodology for software development
12:44 Create pricing calculators using scrum methodology
15:08 Creating a project backlog with three main features for pricing calculations.
17:37 Creating a sprint using a Trello list
Crafted by Merlin AI.
What I have learn in this videos is What is SCRUM, How we can use that method for Our projects and This Man is bad at Spellings(Jokes apart), By the way very good video and very helpful.
Well made video, with real examples. As a web development student learning scrum work, this is best what I found in youtube. Thank you very much.
... which is exactly the problem. It is FULL of mistakes. The terminology is wrong, the artifacts are wrong, the events are wrong.
Please don't spread misinformation. Scrum is not an acronym and doesn't stand for what you seemingly made up to be. I would love to see the source where you got that from. It actually comes from the term Scrum that's used in rugby. The team comes together in what they call a scrum to work together to move the ball forward. In this context, Scrum is where the team comes together to move the product forward.
Noone cares
@@landsknecht_voranwe care
Correct
Pls Shit It.
Please i want to understand the difference between scrum and agile
What a fantastic video and a great effort in presenting! Thank you for sharing the Figma diagram, you are a legend.
wow! this video is not appreciated enough. This is GOLD! Thanks a lot
You are the only person making videos on this without putting annoying music in the background
SHARED to TechApart!
This was an EXCELLENT tutorial. Thank you.
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.
You did an excellent job here.
Wow Man, this is such an amazing way to explain the basic. Thanks for simplifying it. Cheers.
Thank you so much. You made it very easy to understand with real examples. Appreciate 👏
This whips through Scrum with alot of assumptions that the person viewing it will have any sort of inkling what you are doing and/or talking about
Awesome video, thank you! This was a great primer for those unfamiliar with SCRUM/Agile processes. I don't think SCRUM is an acronym, it was named so due to a formation in rugby, called "scrum". The formation was used to restart play in the game, which highlights the collaborative features in SCRUM. Again, solid video overall
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.
Good overall explanation, but the errors are very confusing and are a huge distraction when trying to watch the video. Is it possible for you to remake this video without any errors to make every thing as clear as possible?
Agree. Having the word "Spring" instead of "Sprint" throughout the video multiple times (even after many cut-and-pastes) without catching the error made it look like a legitimate scrum term. No offense but it's a bit sloppy when the video generally had good content otherwise.
@user-zf1pl6wj4n What gives you that idea? Genuinely curious. Especially, since the user's homepage features a video with the same person show in this video that directly references his user/site name, so I was just wondering if there was any basis to this assertion that watchers should be aware of?
@DarkTwistedLullaby i believe he means if he knew what sprint was he wouldnt call it by the wrong name
Very informative. Thanks for sharing. Have a great day. 👍
Great Tutorial. Concise and easily understandable lecture. Kudos.
Awesome explanation. Thanks for sharing.
I wish there was consistency in term usage and proper attention given to presentation because the spelling errors make it unprofessional and confusing.
The three artifacts are Product Backlog , Sprint backlog and Increment. I highly doubt that Burn-Down Chart is an artifact. I would say it is definitely a tool for measurements, not an artifact
Although the burndown (or burnup) chart is not an official scrum artifact, many teams use it to communicate and track progress toward the sprint goal during the sprint
That's right - formally speaking, the third Scrum artifact is the "increment", not the burndown. The material in this video is a bit misleading.
Very useful video! The information presented was clear and easy to follow.
Thank you so much for such great a explanation of SCRUM.
You really help me a lot.
Fantastic video. Commenting for the algorithm.
You made this so simple we're my teacher was dragging it out and confusing me
Thanks for creating this wonderful video. I’ve learned a lot!
Excellent Explanation !!.....Have subscribed to the channel...
Thank you for this amazing video! Very helpful for my exam in Agile Project Management. :)
This video as good as it look and can see the effort you put in it, From the beginning display a lot of miss information it does has a lot of views so will be a good idea to update it with the correct info.
thanks! it was a complete intro video in a short time!
Great video! Thank you. It's funny though how many times you typed "Spring" instead of "Sprint". Haha
I love this content, it helps for my capstone, thank you sir.
Great pace and details - thanks very much!!!! Excellent presentation
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.
A thousand likes!!! 👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽 this video should be the best scrum video explanation in the entire TH-cam !!!
Wow, such a great content. I love it. Thank you
For start-ups, the most effective agile Scrum tool that is also affordable would depend on various factors such as team size, specific project needs, and preferred features. However, tools like Trello, Asana, and Vabro are often considered effective choices for start-ups due to their user-friendly interfaces, customizable workflows, and reasonable pricing plans. These tools offer essential Scrum features such as backlog management, sprint planning, task tracking, and collaboration functionalities, making them suitable options for start-ups looking to implement agile methodologies without breaking the bank.
Such a nice video. Loved it!
Hi, I have a question, according to your video the third artifact is a burn down but according to the scrum guide it is an increment. Can you explain please?
Scrum is product development which was initially created for software development.
Very useful video descriped a whole stuff in a simple method 🎉
I appreciate you making this but I was looking for something exactly in line with the Scrum Guide and this deviated a bit.
Good example, easy to catch up what the basic knowledge of SCRUM. Thank you!
Very nice overview of the topic. Incompitence around me at work sometimes makes me think maybe I don't know how to manage a project, but this video made me sure that I know what I'm doing! The FigJam boards are really great, trying them out with my next project
Not clear on something -- in a regular project management scenario, you have the product, but you also have things that come before and after the development: requirements gathering, configuration, implementation, training, beta testing, regression testing, and so forth. Would these all be separate SCRUMs or do you include these phases in the SCRUM planning for the product. If they're all separate, then I don't understand how this method saves a company any time.
awesome explanation. Thanks Codex.
Very useful Scrum! Love this!
simple and easy to understand, thank you 10:10
Traditional, Traditioanl. Artifact, Artificat. These kinds of mistakes make me question other information in your presentation. Are you using spring and sprint interchangeably or are they 2 different things?
Burndown chart is not one of the artifacts. Product increment is one of artifacts.
Excuse me, the burn down chart is not an artefacts in scrum, its only a complementary tool for managing work in a team. The last artefact un scrum is the increment.
You do know your scrum burndown chart can't be an artefact. Some teams don't even use burndown charts
7:16 Before we address the product backlog item you mentioned, such as the login feature, at what point are we discussing the overall system architecture decisions?
This is amazing! Thank you so much for sharing.
So, what is the difference between spring and sprint? I noticed you pronounce spring as "sprint", even though you wrote it as spring. Why is that?
Did you confuse spring with sprint repeatedly on purpose or what?
Thanks for the video! It's simple and very understandable
Best Spring explanation
Genius video ..many thanks
Great stuff. Good overview and refresher.
This was fantastic. Thank you!
love this, very helpful :)
SCRUM: Suffering Continues Regardless of Useless Meetings
If a software team you're interviewing at practices this shit: RUN
How many times can you write spring instead of sprint?!
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.
You begin with a MVP as lean as possible. For Example Citibank creating a mobile app for customers. The Customer Service discuss the customer feedback with the product owner. The product owner makes a product backlog for the scrum team to improve customer experience. And this keeps on repeating. After a few years the Citibank is a full fledged app with added investment, insurance possibilities
awesome content , very helpful and goives good overiew of scrum
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!
Yea this was done on the fly since I was learning scrum, I'll try to update when I do my next 2023 Scrum video!
Good day how can I be trained as a scrum master?
great so far!
great great video, congratulations
i have a question, if we develop deliverable based on small story, how can we makes tables architecture optimum for overall product.
First time in my life I actually slow down a video 😅
PLEASE 🙏 ! make another video just like this one but for “SAFe 6.0 Safe Scrum Master” SSM. I would really appreciate 😬
Thanks I was a bit stuck on explaining this
At this point I became dyslexic. Hahaha, Great Video by the way
Hi I have been looking to move IT sector from mechanical manufacturing at the age of 36 is that possible to changover ? If possible can I survive IT sector ?
⭐⭐⭐⭐⭐ corto, claro y conciso 10/10 , thank you
Can you fix some of your spelling I wanted to promote this to my team to watch but it should be SPRIT not spring and some of the project and product confusion
This is very informative and I love the information but some of the mistakes make it so I can’t share or recommend to other people
To be more accurate: it is neither “spring” nor “SPRIT”. “Sprint” is the right term.
I think you have a good point on spelling issues which might confuse the ones new to scrum.
Another typo with “artificats” which should be “artifacts”.
Overall, a cool video fails to be perfect, so close though.
I love the explanation and illustration, thanks man
Great informative video!
Its very informative thank you!
Absolutely fascinating
I thought scrum is framework and scrum mindset is product delivery not project delivery
do you now application lovevol for scrum?
Could you provide new figma links? The above are not valid anymore (?) I got an error message
Nice explanation ❤