Just finished reading the book Scrum from the guy who created the process. It was good but unnecessarily long and drug out. It could have been written in one chapter. This video was exactly what I would have hoped the book would be. No fluff, all info. Great job!
Just like in your 2nd sentence "unnecessarily long and drawn drug out" this... SCRUM method is absurd. It induces LARGE undue managemental overhead in an environment best kept lean and clean. Per the depiction in the video: it is a bunch of people running around the DEV environment at a speed that will increase failure rate: thus the "feedback" / Bug reports from users. By this method the burden of debugging is pushed to the users who as of now should NEVER encounter bug... when in fact there are no Bug... there are only sloppy mistakes created by DEVs... and more frequently by DEVs using this method. The bottom line is a bunch of people driving too fast for their abilities and/or working conditions... As of this post this video is 6 years old. Point being: Don't be quick Jump on Trends that are typically dead in a few years...
Brilliant and nice to see a Scrum guide that isn't software development centric. To those who commented on what things are called I would ask why that matters? It's Agile culture, mindset, values and principles that deliver results, not naming conventions associated with software teams.
The "team" you mentioned is actually called "Developers". Theres only one team i.e. scrum team which comprises of a product owner(owns the product backlog), developers(team responsible for developing the product by actually coding for it) and the scrum master(facilitation and process owner)
Nice video, I would recommend using defined names for things like the scrum team and scrum ceremonies which are in the scrum guide. For example, the scrum team consists of a product owner, scrum master and a development team. The ceremonies are, sprint planning, daily scrum, sprint review and sprint retrospective. I really like the example that you used for the design of a new car, which really showed the goal of a sprint which is an incremental delivery of “Done” product ensuring a potentially useful version of working product is always available.
Thank you for your comments and compliments Mitch! Fair point about the official names of the roles and ceremonies. Our main focus is to make Scrum understandable and easy to adopt for non-software/IT purposes. That is why some names are changed slightly from standard Scrum Guide terms.
Changing the names of Scrum roles and events doesn't make it easier to understand, it creates confusion 😊 The rules of Scrum are described in the Scrum guide. Everything else is not Scrum. Speaking the same language when using the same framework is important to prevent misunderstandings.
Sorry to be off topic but does someone know of a trick to get back into an instagram account?? I somehow forgot the password. I would appreciate any tricks you can offer me!
The first seconds imply that you can use scrum everywhere but I would love seeing you using an Agile methodology on a project where u have 8.000 people involved like a nuclear powerplant for example and if the end result will be better than with PMP. The rest looks OK to me.
Good and extremely simplified explanation of scrum, best suited to someone who has never come across it before. The first 30 seconds was not correct though and unnecessary. Scrum is not a replacement for project management. This is because scrum is a framework for developing complex products in complex environments, that can sit within a project methodology. I have done this myself quite successfully as a PM and Scrum Master. Scrum on its own doesn't bother with all the governance tasks of running a project, or the resource management, or the budget and risk management, or all the other project management tasks..etc. etc. Ken Schwaber's book, Agile project management with Scrum explains it quite well...
For those who want to get straight to the matter: Scrum explanations begin a little after 2 mins into the video. Also, simplification of something already very simple has resulted in misinformation. Scrum events aren't called meetings for a reason - participants in a Scrum environment need to align to mindset that differs from that of 'meetings'. Stand-ups aren't an "are we there yet?" session. I don't understand why random organisations insist on corrupting something as simple as Scrum - if you're really interested in knowing more about Scrum, there're much better videos ...and the Scrum Guide explains everything in a very simple manner.
This concept is very interesting. I have never heard of Scrum so I was very curious to learn more about what it is and why it helps with making projects more efficient. As a planner for both my personal and professional life it is so important to stay on target and that can be so hard to do on a team. I definitely think this concept can help many teams become more efficient and effective, allowing for more positive outcomes and help from keeping a team burnt out. Great video! I will be looking for more concepts like this one to use in the future.
Excellent presentation! I was able to understand the concept very easily...thank you very much for sharing...what is the software that you are using to animate? its wonderful
Why people spend too much time watching a lot o videos that increase nothing? Self-promotions, sales etc. This is the best video ever. I have PSM and PSPO, so I can confirm, this video was the best I’ve watched on RUclips.
So cute. This is just humanogogy in action. We learn and communicate naturally this way. It only works when teams are small and talented, it doesn't scale easily, as everyone needs to be aligned to the main goal. I've personally only seen tech companies adopt scrum. They should have quoted the source of the bridge... I can't imagine a bridge being half built, collecting feedback, and being built differently. Basically gaining perspective is your ally. You need to think of as much as possible and consider all variables before the final launch, that what this workflow promotes
As with all scrum explanations, it seems this is a happy-go-lucky approach. No, there has to be a plan and it needs to be followed. Of course, things can be broken down into a sensible number of scrums, which need to be defined and planned, with SIT, Training, UAT sign-off, Go live cutover, hypercare and handover to operational support.
Very professional video, great way to explain how Scrum works. However, there are a couple of big misunderstandings that are explained in this video that are incorrect and therefore can cause confusion. The Development Team, what's called team in this video is the team of development (software or otherwise) professionals. Most importantly the Scrum Master and Product Owner are also part of the Scrum Team. Each with their own responsibility. The Scrum Master focus on the process is an easy explanation, however runs the risk of just facilitating meetings. Professional Scrum Masters focus on making sure Scrum and it's empirical process control is understood by the team, organisation and acts in different stances on that. Making the way for change. Daily Scrum is often practiced standing, but not required, because that would exclude people with the inability to stand. The Scrum board is another practice not part of Scrum. The only requirement is that Development Teams create transparency on their Sprint Backlog. The definition of done does not state what exactly should be done. The way things are done is up to the Development Team, because that is their expertise. The Definition of Done creates transparency on what done means in terms of quality for the Development Team. Some of these things might seem small, but the right understanding of Scrum makes a big difference in the real world. Where teams and organisations struggle to make good use of empiricism, a solid understanding of Scrum is imperative.
I am sorry, Jasper, but the real world, does not need Scrum. All jobs i did so far, not office!, were..... consulting, planning, organizing, producing. No runs, no sprints, no masters, no nothing at all. Just normal common sense, and everything was fine.
great video! easy to follow and finally a native speaker who can be understood in comparison to some other RUclips videos... Question: if I worked as an apple care tech advisor for 26 months serving macOS, iOS and a tiny bit of android, WIN10, wifi routers, would I have sufficient IT knowledge to pass a scrum master course? and would I have sufficient IT knowledge to work in a scrum team for a tech company? thank you!
Probably useful. But these endless meetings are often what result in people being drained. Also instead of scrum actually being used as a method of maintaining flexibility and improving a product, it's often used to get more work out of employees. Not it's intended use at all. Honestly this is just for people who can't plan or take feedback properly so they need a "system" in order to conceptualise it.
Yeah, all the meetings are just one of the things that make scrum horseshit. Retrospectives, for example. I'd like to hear from anyone who's ever actually got any value from sprint retros. The assumption is that you'll make mistakes in your process in every sprint, that are within your control to solve, and so by having a meeting about it every 2 weeks or so, you can solve these problems. Well, if you find that after every sprint you had process problems, then there's something fundamentally wrong. Why do you keep making mistakes? Scrum pisses me off because it's a cult that many companies are following, and all it pretty much does is add huge amounts of admin overhead for no value.
I dont really get it. Are these terms like agile and scrum just another way of saying 'being organised and work as efficiently as possible to achieve a target on time'...etc etc??
yes, thats it. I started working in an office, for the first time of my life, and i am more than laughing. I was for decades in gastronomical business and in constructions as a welder..... when i got here, and they started with all this scrum and agile i just laughed my ass off. i was like...... ok, you have to plan and organize to get things done...i get that! ....but its fucking common sense. consulting, planning, organizing, producing. There is no need to have a meeting for a meeting to get a meeting....and sprints, and stand ups and all this wannabe sophisticated bullshit..... and all these managers, and support managers, and masters, and leaders..... maaaan, if we would do it like this in normal outside jobs, we wouldnt have any money to buy the materials we need.....lol
@@benraiti3398 this is wrong. It’s not a methodology. It’s a framework and technically if you’re not following scrum in all of its processes it’s not scrum. Most companies do not do this. Therefore they are agile but not scrum
So project managers took a basic logical concept and gave it a formal name. We have been doing this same process for a very long time, except we called it "The Daily 15 Minute Meeting". From all the hype, i thought that there was some new universal thought process. Kind of a big nothing really
This video tackled a big big issue folks have with adopting scrum. Too many people who promote scrum tend to be geeky “tech” types who use all of this strange vocabulary that sounds nothing like what is actually means (for example: user story sounds like a customer’s experience using a product or service- wrong). Business leaders and daily workers don’t have time to engage in all of this silly vocabulary that can easily be broken down into laymen terms (for example: user story should just be a customers experience with a product ie the “users” “story” about heir experience). As a result of this lack of common sense language for things people already understand (“daily stand up= morning meeting), I’ve seen executives, managers, and project leaders become frustrated with scrum and discard it. Being overly complicated and requiring people to learn completely new vocabulary that doesn’t match common sense language turns people off. I say keep the daily stand ups (daily checkins about successes and struggles) and discard the rest 👋
Good video, but with all the hype around working in Agile, I think that all in all it creates more chaos than order, and the finalized product half baked. There has to be a simpler, better, and more efficient way to work in teams.
For who ever will read this in future, you hold it usually at the end of the month so you can review what you've done and see possible improvements, etc. If you have more time you can have it every 2 or 3 weeks. Its basically 2 edge sword. If you hold them too close apart it will cost more money and time but if you have them too sparse apart you might run into troubles where something is going to be changed and you're in too deep so you have to do a lot of revisions.
i don't see any advantage in comparison to how a project has been delivered in the past, if you don't have committed resources, a common goal in mind, and clear communications - you will fail regardless.
My company had over 200 project managers and did a lot of internal research on this. They found that Scrum works better than Waterfall in a few specific circumstances. Projects where you don't know where you are going and you need to constantly evaluate the results work best with Scrum. It also worked well for poor performing PMs who struggled with Waterfall because it put many PM decisions on the engineers. High performing Waterfall PMs and engineers were slowed down by Scrum and several of our best people threatened to quit if Scrum was mandated. Low performers and new grads loved Scrum. In the end the company realized it was best to primarily utilize Waterfall and fire poor performing PMs. They had me do two $14m/18 month projects that were almost identical at the same time, one with Scrum and the other with Waterfall. Because we had similar projects in the past and we had a complete understanding of what the customers wanted the Waterfall project was 8% under budget and 3 weeks early. Due to all the meetings and unnecessary discussions generated by the Scrum process that project was 3% over budget and 2 weeks late. The Scrum process also stressed out several of our older engineers who did not like to constantly attend meetings. New grads liked it because it made them more involved in discussions, which wasted a lot of time shooting down bad ideas and scope creep. When the system was deployed significantly more engineering errors were found on the Scrum project and the startup took much longer. The scrum project had almost $400k in warranty claims and the Waterfall project had none, which was normal for similar projects. The Scrum project significantly lowered moral and wasted a lot of my time, so I felt like all my other Waterfall projects suffered because I was constantly distracted by the Scrum project problems. Although I could juggle about 8 Waterfall projects at a time, I could not handle more than 2 Scrum projects at once. A year later I did a research and development project using SCRUM that WORKED VERY WELL because we needed to constantly evaluate testing results and change direction. It worked out much better that previous R&D project that I did with Waterfall. The only people who say Scrum works better than Waterfall all the time either don't know how to use Waterfall or they are profiting off of teaching/certifying Scrum. My best engineer said something during the Scrum project that I will never forget: "Moral can't get any lower unless they make us go to the bus station and suck dicks in the bathroom".
Great video until you called the artifacts "lists" and said the Definition of Done is about what needs to be delivered in the Sprint. Definitely flawed.
For trying to "Simplify" the project process, you sure make your definitions and breakdown WAY too complicated. You didn't change a thing to the PM process, you just said in a convoluted way "break projects down into short bursts, track KPIs on a large and small scale, use a platform for tracking team progress, and have 4 meetings" all of this is already the BASIC understanding of the PM process. You basically just redefined the terminology.
Just finished reading the book Scrum from the guy who created the process. It was good but unnecessarily long and drug out. It could have been written in one chapter. This video was exactly what I would have hoped the book would be. No fluff, all info.
Great job!
💀
Just like in your 2nd sentence "unnecessarily long and drawn drug out" this... SCRUM method is absurd. It induces LARGE undue managemental overhead in an environment best kept lean and clean. Per the depiction in the video: it is a bunch of people running around the DEV environment at a speed that will increase failure rate: thus the "feedback" / Bug reports from users. By this method the burden of debugging is pushed to the users who as of now should NEVER encounter bug... when in fact there are no Bug... there are only sloppy mistakes created by DEVs... and more frequently by DEVs using this method. The bottom line is a bunch of people driving too fast for their abilities and/or working conditions...
As of this post this video is 6 years old. Point being: Don't be quick Jump on Trends that are typically dead in a few years...
@@RAZR_Channel Not sure how his second sentence could be any shorter and still give the information he wanted to get across honestly.
I appreciate the simplified explanation. Thanks
would you recommend this for beginners?
Brilliant and nice to see a Scrum guide that isn't software development centric. To those who commented on what things are called I would ask why that matters? It's Agile culture, mindset, values and principles that deliver results, not naming conventions associated with software teams.
Yapp i agree
so beautiful , this video should be a contestant for miss world
i did a 2-day product owner course and honestly this kind of summary would have been very helpful
The "team" you mentioned is actually called "Developers". Theres only one team i.e. scrum team which comprises of a product owner(owns the product backlog), developers(team responsible for developing the product by actually coding for it) and the scrum master(facilitation and process owner)
I've been on scrum teams in multiple companies and there were always more meetings with the process than with any other.
I just wanted to watch rugby but this is fine I guess
Jajajaja😂😂
🤣🤣🤣
Haha
😆😆😆😆😆😆
😅😅classically funny....😜
Nice video, I would recommend using defined names for things like the scrum team and scrum ceremonies which are in the scrum guide. For example, the scrum team consists of a product owner, scrum master and a development team. The ceremonies are, sprint planning, daily scrum, sprint review and sprint retrospective. I really like the example that you used for the design of a new car, which really showed the goal of a sprint which is an incremental delivery of “Done” product ensuring a potentially useful version of working product is always available.
Thank you for your comments and compliments Mitch! Fair point about the official names of the roles and ceremonies. Our main focus is to make Scrum understandable and easy to adopt for non-software/IT purposes. That is why some names are changed slightly from standard Scrum Guide terms.
Changing the names of Scrum roles and events doesn't make it easier to understand, it creates confusion 😊
The rules of Scrum are described in the Scrum guide. Everything else is not Scrum. Speaking the same language when using the same framework is important to prevent misunderstandings.
mitch coppins
Hindi
mitch coppins love your explanation, thank you!
Sorry to be off topic but does someone know of a trick to get back into an instagram account??
I somehow forgot the password. I would appreciate any tricks you can offer me!
The first seconds imply that you can use scrum everywhere but I would love seeing you using an Agile methodology on a project where u have 8.000 people involved like a nuclear powerplant for example and if the end result will be better than with PMP. The rest looks OK to me.
YESSSSSSSSS!!!!! 👍👍👍👍👍
Good and extremely simplified explanation of scrum, best suited to someone who has never come across it before.
The first 30 seconds was not correct though and unnecessary.
Scrum is not a replacement for project management. This is because scrum is a framework for developing complex products in complex environments, that can sit within a project methodology. I have done this myself quite successfully as a PM and Scrum Master.
Scrum on its own doesn't bother with all the governance tasks of running a project, or the resource management, or the budget and risk management, or all the other project management tasks..etc. etc.
Ken Schwaber's book, Agile project management with Scrum explains it quite well...
I'd love how this explained Scrum the easiest way. Thank you for the video!
For those who want to get straight to the matter: Scrum explanations begin a little after 2 mins into the video. Also, simplification of something already very simple has resulted in misinformation. Scrum events aren't called meetings for a reason - participants in a Scrum environment need to align to mindset that differs from that of 'meetings'. Stand-ups aren't an "are we there yet?" session. I don't understand why random organisations insist on corrupting something as simple as Scrum - if you're really interested in knowing more about Scrum, there're much better videos ...and the Scrum Guide explains everything in a very simple manner.
Thank you for this wonderful presentation!! You kept the video short, but it's very informative.
This concept is very interesting. I have never heard of Scrum so I was very curious to learn more about what it is and why it helps with making projects more efficient. As a planner for both my personal and professional life it is so important to stay on target and that can be so hard to do on a team. I definitely think this concept can help many teams become more efficient and effective, allowing for more positive outcomes and help from keeping a team burnt out. Great video! I will be looking for more concepts like this one to use in the future.
Most simplified video. Thanks
Great and easy explanation.....now everyone is certified :)
Excellent presentation! I was able to understand the concept very easily...thank you very much for sharing...what is the software that you are using to animate? its wonderful
Very good explanation
Then there is my boss, who likes to change his mind 20 times a day and gives us 'sprints' of 30 minutes.
Excellent presentation!
Nice video
Why people spend too much time watching a lot o videos that increase nothing? Self-promotions, sales etc. This is the best video ever. I have PSM and PSPO, so I can confirm, this video was the best I’ve watched on RUclips.
So cute. This is just humanogogy in action. We learn and communicate naturally this way. It only works when teams are small and talented, it doesn't scale easily, as everyone needs to be aligned to the main goal. I've personally only seen tech companies adopt scrum. They should have quoted the source of the bridge... I can't imagine a bridge being half built, collecting feedback, and being built differently. Basically gaining perspective is your ally. You need to think of as much as possible and consider all variables before the final launch, that what this workflow promotes
Well presented and simple.
simple and easy to understand, a very helpful explanation.
Excelent video!!
As with all scrum explanations, it seems this is a happy-go-lucky approach. No, there has to be a plan and it needs to be followed. Of course, things can be broken down into a sensible number of scrums, which need to be defined and planned, with SIT, Training, UAT sign-off, Go live cutover, hypercare and handover to operational support.
nice animation, it was fun learning
Very professional video, great way to explain how Scrum works. However, there are a couple of big misunderstandings that are explained in this video that are incorrect and therefore can cause confusion.
The Development Team, what's called team in this video is the team of development (software or otherwise) professionals. Most importantly the Scrum Master and Product Owner are also part of the Scrum Team. Each with their own responsibility.
The Scrum Master focus on the process is an easy explanation, however runs the risk of just facilitating meetings. Professional Scrum Masters focus on making sure Scrum and it's empirical process control is understood by the team, organisation and acts in different stances on that. Making the way for change.
Daily Scrum is often practiced standing, but not required, because that would exclude people with the inability to stand.
The Scrum board is another practice not part of Scrum. The only requirement is that Development Teams create transparency on their Sprint Backlog.
The definition of done does not state what exactly should be done. The way things are done is up to the Development Team, because that is their expertise. The Definition of Done creates transparency on what done means in terms of quality for the Development Team.
Some of these things might seem small, but the right understanding of Scrum makes a big difference in the real world. Where teams and organisations struggle to make good use of empiricism, a solid understanding of Scrum is imperative.
We appreciate your nuances on the story Jasper. Agree, we also find it important that the community is involved in the further development of Scrum :)
I am sorry, Jasper, but the real world, does not need Scrum.
All jobs i did so far, not office!, were.....
consulting, planning, organizing, producing. No runs, no sprints, no masters, no nothing at all.
Just normal common sense, and everything was fine.
great video! easy to follow and finally a native speaker who can be understood in comparison to some other RUclips videos... Question: if I worked as an apple care tech advisor for 26 months serving macOS, iOS and a tiny bit of android, WIN10, wifi routers, would I have sufficient IT knowledge to pass a scrum master course? and would I have sufficient IT knowledge to work in a scrum team for a tech company? thank you!
What do you mean by native speaker? This channel is based in the Netherlands.
I think he meant native English speaker and not someone who speaks it as a second language@@bajabl
Great job. Thank you so much
So it is a project message board with milestones and dedicated administrators as I recon.
Eventually it's all about the agile mindset, not about the board.
1:10 Is the bridge still standing?
Thank you. Great video!
wonderful explanation
Thank you🙏
Thank you!
Great video! It felt like I was being entertained while learning
Best video representation for the explanation of Scrum.
best explained...
this is amazing
wow thank you, finally i got it
Hey
Probably useful. But these endless meetings are often what result in people being drained. Also instead of scrum actually being used as a method of maintaining flexibility and improving a product, it's often used to get more work out of employees. Not it's intended use at all. Honestly this is just for people who can't plan or take feedback properly so they need a "system" in order to conceptualise it.
Yeah, all the meetings are just one of the things that make scrum horseshit. Retrospectives, for example. I'd like to hear from anyone who's ever actually got any value from sprint retros. The assumption is that you'll make mistakes in your process in every sprint, that are within your control to solve, and so by having a meeting about it every 2 weeks or so, you can solve these problems. Well, if you find that after every sprint you had process problems, then there's something fundamentally wrong. Why do you keep making mistakes? Scrum pisses me off because it's a cult that many companies are following, and all it pretty much does is add huge amounts of admin overhead for no value.
Thanks
I appreciate that this video doesnt have a picture of an arm flying all over the screen.
Absolutely brilliant. Thanks for sharing 😍
This is so straight to the point...love it! Thanx
Beautiful video.. I like the animation and simplicity in the presentation. What platform did you use to make the content?
Thank you! We have our own animator who makes these kind of videos for us :)
I dont really get it. Are these terms like agile and scrum just another way of saying 'being organised and work as efficiently as possible to achieve a target on time'...etc etc??
It's a certain methodology for completing projects. The idea is essentially breaking down a bigger project into smaller ones to help finish it.
It is another way of saying that kinda but there's a certain process you need to follow.
yes, thats it.
I started working in an office, for the first time of my life, and i am more than laughing.
I was for decades in gastronomical business and in constructions as a welder.....
when i got here, and they started with all this scrum and agile i just laughed my ass off. i was like......
ok, you have to plan and organize to get things done...i get that!
....but its fucking common sense. consulting, planning, organizing, producing.
There is no need to have a meeting for a meeting to get a meeting....and sprints, and stand ups and all this wannabe sophisticated bullshit.....
and all these managers, and support managers, and masters, and leaders.....
maaaan, if we would do it like this in normal outside jobs, we wouldnt have any money to buy the materials we need.....lol
@@benraiti3398 this is wrong. It’s not a methodology. It’s a framework and technically if you’re not following scrum in all of its processes it’s not scrum. Most companies do not do this. Therefore they are agile but not scrum
@@matthoffman6962 Thanks for clarifying, yeah poor response on my part. I understand it better since a few years back.
So project managers took a basic logical concept and gave it a formal name. We have been doing this same process for a very long time, except we called it "The Daily 15 Minute Meeting". From all the hype, i thought that there was some new universal thought process. Kind of a big nothing really
het is zondag ochtend en ik moet dit kijken
How can scrum deliver a bridge? That is waterfall project if I ever saw one. You can't deliver 1/4 of a bridge and take 'iterative feedback'...
Agile is only applicable to software development, because real-world projects need to be fully functional at release.
This video tackled a big big issue folks have with adopting scrum. Too many people who promote scrum tend to be geeky “tech” types who use all of this strange vocabulary that sounds nothing like what is actually means (for example: user story sounds like a customer’s experience using a product or service- wrong). Business leaders and daily workers don’t have time to engage in all of this silly vocabulary that can easily be broken down into laymen terms (for example: user story should just be a customers experience with a product ie the “users” “story” about heir experience). As a result of this lack of common sense language for things people already understand (“daily stand up= morning meeting), I’ve seen executives, managers, and project leaders become frustrated with scrum and discard it. Being overly complicated and requiring people to learn completely new vocabulary that doesn’t match common sense language turns people off. I say keep the daily stand ups (daily checkins about successes and struggles) and discard the rest 👋
"With Scrum, it's possible for more and more people can have a phone in their car." -Kung Fury
This is so helpful. I didn’t realize that scrum masters built all the new tech I use. I thought it was engineers. I’m stupid. Lol!
well made thank you
Maybe sometime during the process you can even find time between meetings to actually do work!
What were they doing with Rory's Story Cubes?
4:25
They forgot to mention that 20% of your week will now be dedicated to meetings.
How we can use in construction industry?
that was pretty good
Amazing explanation thank you! Do you know an accredited website that provides with certification of scrum?
Scrum.org
What's best for me
Hi can a HR non technical person learn scrum agile thru online courses and get a job ?
Good video, but with all the hype around working in Agile, I think that all in all it creates more chaos than order, and the finalized product half baked. There has to be a simpler, better, and more efficient way to work in teams.
agile and scrum is for people who cant get organized, cant plan, actually for people who are missing common sense, yes. You are right.
can you please give this presentation PPT I want this
When do you hold certain meetings?
For who ever will read this in future, you hold it usually at the end of the month so you can review what you've done and see possible improvements, etc. If you have more time you can have it every 2 or 3 weeks. Its basically 2 edge sword. If you hold them too close apart it will cost more money and time but if you have them too sparse apart you might run into troubles where something is going to be changed and you're in too deep so you have to do a lot of revisions.
i don't see any advantage in comparison to how a project has been delivered in the past, if you don't have committed resources, a common goal in mind, and clear communications - you will fail regardless.
dunno about the car example...
I can only imagine this scrum master position doesn't exist in China
I didn't understand, what does media has to do with this????
So basically, 'Work step by step.'
My wife left me. Can Scrum fix that?
"Review" phase should be termed "implement" instead.
No, review is the correct name for that scrum ceremony.
Music in background is too loud
More expensive, more stress, less successful end product, drained team - is there any evidence AT ALL for these claims?
My company had over 200 project managers and did a lot of internal research on this. They found that Scrum works better than Waterfall in a few specific circumstances. Projects where you don't know where you are going and you need to constantly evaluate the results work best with Scrum. It also worked well for poor performing PMs who struggled with Waterfall because it put many PM decisions on the engineers. High performing Waterfall PMs and engineers were slowed down by Scrum and several of our best people threatened to quit if Scrum was mandated. Low performers and new grads loved Scrum. In the end the company realized it was best to primarily utilize Waterfall and fire poor performing PMs.
They had me do two $14m/18 month projects that were almost identical at the same time, one with Scrum and the other with Waterfall. Because we had similar projects in the past and we had a complete understanding of what the customers wanted the Waterfall project was 8% under budget and 3 weeks early. Due to all the meetings and unnecessary discussions generated by the Scrum process that project was 3% over budget and 2 weeks late. The Scrum process also stressed out several of our older engineers who did not like to constantly attend meetings. New grads liked it because it made them more involved in discussions, which wasted a lot of time shooting down bad ideas and scope creep. When the system was deployed significantly more engineering errors were found on the Scrum project and the startup took much longer. The scrum project had almost $400k in warranty claims and the Waterfall project had none, which was normal for similar projects.
The Scrum project significantly lowered moral and wasted a lot of my time, so I felt like all my other Waterfall projects suffered because I was constantly distracted by the Scrum project problems. Although I could juggle about 8 Waterfall projects at a time, I could not handle more than 2 Scrum projects at once.
A year later I did a research and development project using SCRUM that WORKED VERY WELL because we needed to constantly evaluate testing results and change direction. It worked out much better that previous R&D project that I did with Waterfall.
The only people who say Scrum works better than Waterfall all the time either don't know how to use Waterfall or they are profiting off of teaching/certifying Scrum.
My best engineer said something during the Scrum project that I will never forget: "Moral can't get any lower unless they make us go to the bus station and suck dicks in the bathroom".
Great video until you called the artifacts "lists" and said the Definition of Done is about what needs to be delivered in the Sprint. Definitely flawed.
Can you explain how you see this and what you mean Luciana?
Explain how to build a bridge, not a lame ad campaign for a car.
2:28 only one girl... that's sad
bier drinken
sCrummy.
Not very useful explanation.
A very misleading video.
For trying to "Simplify" the project process, you sure make your definitions and breakdown WAY too complicated. You didn't change a thing to the PM process, you just said in a convoluted way "break projects down into short bursts, track KPIs on a large and small scale, use a platform for tracking team progress, and have 4 meetings" all of this is already the BASIC understanding of the PM process. You basically just redefined the terminology.
Rubbish explanation
title says 'scrum in 5 min' and video is of 4:31 mins .........lol
It says under 5 minutes you illiterate fuck
"under 5 minutes." bruh wtf you even complaining about. Read first...
It says under 5 minutes
Nice video