Rules on Electronics. In 2021, most people in our team come in with laptops. It's a fine line because they read off their laptops in meeting. instead of whiteboard we have a big TV screen and people connect to it and can move cards from their laptop.
The entire point is accountability. People hate it because it puts them on the spot. Any experienced software engineer knows this keeps up productivity and lights a fire under your ass. This was a great example of a good scrum meeting. Keep it productive and concise, that's the point. She kept asking questions because she's helping them not forget they are accountable for their tasks, and that nobody can just come along the next day with some big problem that nobody saw because he/she told nobody. This model makes sense, that's why it's used.
the point is that if you can do your job (both because you have the tools to do it - sw, previous knowledge of people working on that before you, team presence - and the abilities to do it) you don't need this. This is usually done because your boss doesn't know what it is going on and he/she is trying to have the control on it. Especially in start ups. In my experience I had endless standups (30-40 minutes) before going to lunch, with people talking for 10-15 minutes. This resulted in: ending too late for lunch, obliging me to have some snacks for not ending the shift late that day. In addition to this, no one was interested in talking with others before/after the standups so basically there was no team. But hey! The boss was happy and we gained a decent salary for the rest of the month. UhUh!
If your people need fire under their ass to work then you have hired the wrong people. For my part, I work very productively even without such nonsense meetings
i have both good and bad experiences as the video shows. the scrum master plays an very important role in this meeting, makes sure the members are following the bullet points discussed at the beginning of the 2nd part of the video. the meeting helps members focus on the stories, and your life is much easier. you will either like it when it's correctly implemented or hate it if it's poorly managed like the 1st part of the video.
Those criticizing agile based on this video are missing the point. Scrum is a framework and not a process. Your standups would likely be conducted a lot less formal and this example would likely not be implemented by an experienced team. It is meant to give an idea of the format to beginners and in that it succeeds. The purpose of this is to break complicated problems into tasks that each take less than a day to complete and have a clear definition of done. It also lets customers have something tangible every 2-4 weeks that they can provide feedback on. I'm finding more and more that the older model of development where the customer is required to provide an exhaustive specification, and then must wait months before they see anything, which might not match what the customer had in their head, results in poor products and strained business relationships.
What scares me is a LOT of this is common sense. I have experienced some folks doing some of these, once in a blue moon. The most common issue, Agile or not, that I have experienced: 1) Not having an update and reason 2) Not raising or escalating on a road block in a timely fashion 3) Not showing up for meetings on time or being engaged 4) Not working with the team but doing Ye' olde ME ME ME
Interesting perspective Mao. How about this? Agile is a good framework for competent software developers to take responsibility for the results of their work and be held accountable for it instead of passing that responsibility to mangers?
This reminds me what I hated most about the agile environment... the condescending attitude of managers treating professionals as if they were schoolchildren.
So true. I have been programming for over 20 years and we started doing this where I work. Hours of pointless, degrading meetings run by someone who doesn't have any understanding of our product or how to code.
Agile never been a good methodology. Agile is not new. The creators just changed the names. Stand up meetings are Check Point and you only do that when it is close to deployment or cutover. Sprints are releases. Scrum is the weekly status meetings where you review the issues, risks and project status. Many managers fall into this thinking it is a new methodologies. It is actually a way for the creators to make money. Standup meetings is just check points and the PM just go over quickly his check point list and get a quick status. No need for all this theatre.
Such a great agile coach. I wish I got this type of training. My organisation hired an agile coach. But he didn't do any of this. He just prepared a KANBAN board on JIRA instead of Agile sprints. Moreover he did not even classify our project in correct categories.
Some people seem to think these kinds of things do not happen ina professional work environment. Having worked in the IT world for decades, I can tell you that there is a whole generation that doesn't get "Professional" some seem to think its the same as being in school or in their own little social group.
I graduated college in 1982 with a degree in electrical engineering and worked as a contractor since 1990 working on commercial avionics products like air data computers, inertial navigation systems, windshear detection systems, as well as medical devices like implanted defibrillators and immunoassay systems. This agile scrum nonsense is dangerous considering how it puts time pressure on people to show that they accomplished something for the next infantile daily meeting and the distractions of the constant context switching. Agile scrum, more than anything else, makes me glad to be nearing retirement. Does anyone think they can implement a kalman filter from scratch in one of those infantile two week sprints?
Brilliant! but how come one of the guy assigns time duration(2 days) to a task while the sprint is going on? Should it not have already be done earlier in Sprint planning meeting?
That's not an estimation that he puts on the task. It's a commitment date. In Agile you estimate the "complexity of a task or user story". When you start working on that task or story, you can commit to finish it by a specific date. Writing the date on the sticky note helps visualize impediments easier, because if the task is not complete by the commitment date, the team members will be alerted and help out with completing that task. This commitment data at a task level is basically a facilitator that helps team members understand whether their initial estimation of complexity has been realistic or not. If a task proves to be less complex than what's estimated, it would hopefully be finished before the commitment date, and if it's proven to be more complex than the estimation, the team will be notified and run to help :)
Well, stand up is about synchronizing work within a team and scrum master is to facilitate the team. Reporting to scrum master instead of updating their colleagues about progress is wrong. So guys, you have learnt how a frame od stand up should look like, but you forgot to understand a purpose.
I'm still new to the concepts, though I feel more appreciative. Depends on the individual scrum master, of course... But I think the principle about respecting everyone's abilities is number ONE. Also, an SM could probably also be trained and given other responsibilities, or have one of the lead programmers do the meets.
Man so many of the responses seem to completely miss the point of Scrum Masters and who does what in the team, falling back into very old mindsets (Being old myself I can recognize it from as far back as the 1970's) I don't care much for the theatrics in some Scrum Stand ups but if you tone it down a bit to the appropriate age group (young Coders seem to get into the theatrics) I've seen it done right and wrong and it definitely can make a difference if done right and be an impediment if done wrong, and it isnt just the Agile Team that needs to be on board, the Outside managers, directors and executives need to know to allow the process to work and not to micromanage. I do agree that the whole agile concept has allowed a whole new group of people to make money, that does not mean this process does not work....even if you Coders and Developers are Old and have been doing this a long time. Inflexibility and inability to accept change will have you on the outside looking in. Keep the good, accept the new good and ignore the rest. My 3 cents.
How to make incompetents seem competent. Competent teams know how to do their work and just do. Problem is when you hire the wrong people and need to keep them in check. The issue is the competent people suffer and that's not fair.
It can. The scrum master is supposed to monitor that the meetings take place. Basically he/she steps in whenever he/she sees a violation of the scrum methodology.
If this nonsense ["Agile"] ever finds its way into embedded and safety critical software development then I'm quitting. Fortunately, engineers in those fields think a lot more scientifically and so are less likely to take this substanceless dross seriously.
Unfortunately, now that nine years have passed since your comment, it is being inflicted on engineers who design and test embedded safety critical software. I graduated college in 1982 with a degree in electrical engineering and worked as a contractor since 1990 working on commercial avionics products like air data computers, inertial navigation systems, windshear detection systems, as well as medical devices like implanted defibrillators and immunoassay systems. This agile scrum nonsense is dangerous considering how it puts time pressure on people to show that they accomplished something for the next infantile daily meeting and the distractions of the constant context switching. Agile scrum, more than anything else, makes me glad to be nearing retirement.
This kind of drama, I don't like in work. I hate scrum. Scrum is supposed to be a process of managing a project. But here people are talking about process to have this process. Unnecessary time waste and this is a way of getting some work for nontechnical people who usually don't find themselves busy in office. And when someone raise voice against it they say you don't actually understand scrum. What is the mathematics there that people don't understand, God only knows.
This Agile Scrum is one of the biggest bull shts I have ever seen. Well BitCoin is even bigger. But this Agile Scrum comes in close 2nd. I mean what real software project can actually be done in such a time wasting childish way!
this is just a business making money and people who are new in the industry think this is new. They created this methodology just to make money but it is now new
If you got kicked out of your local community theater's improv group then you are well on your way to becoming a certified agile coach.
Rules on Electronics. In 2021, most people in our team come in with laptops. It's a fine line because they read off their laptops in meeting. instead of whiteboard we have a big TV screen and people connect to it and can move cards from their laptop.
The entire point is accountability. People hate it because it puts them on the spot. Any experienced software engineer knows this keeps up productivity and lights a fire under your ass. This was a great example of a good scrum meeting. Keep it productive and concise, that's the point. She kept asking questions because she's helping them not forget they are accountable for their tasks, and that nobody can just come along the next day with some big problem that nobody saw because he/she told nobody. This model makes sense, that's why it's used.
An experienced software engineer doesn't need Agile Scrum to be accountable. And most I expect can be twice as productive without it.
the point is that if you can do your job (both because you have the tools to do it - sw, previous knowledge of people working on that before you, team presence - and the abilities to do it) you don't need this. This is usually done because your boss doesn't know what it is going on and he/she is trying to have the control on it. Especially in start ups. In my experience I had endless standups (30-40 minutes) before going to lunch, with people talking for 10-15 minutes. This resulted in: ending too late for lunch, obliging me to have some snacks for not ending the shift late that day. In addition to this, no one was interested in talking with others before/after the standups so basically there was no team. But hey! The boss was happy and we gained a decent salary for the rest of the month. UhUh!
@@sa3270 what is "Agile Scrum"? Scrum is about team work. 1 experienced SW eng =/= team.
If your people need fire under their ass to work then you have hired the wrong people.
For my part, I work very productively even without such nonsense meetings
Thank you for the simulation it helps better on what not to do during daily standup meetings.
i have both good and bad experiences as the video shows. the scrum master plays an very important role in this meeting, makes sure the members are following the bullet points discussed at the beginning of the 2nd part of the video. the meeting helps members focus on the stories, and your life is much easier. you will either like it when it's correctly implemented or hate it if it's poorly managed like the 1st part of the video.
Those criticizing agile based on this video are missing the point. Scrum is a framework and not a process. Your standups would likely be conducted a lot less formal and this example would likely not be implemented by an experienced team. It is meant to give an idea of the format to beginners and in that it succeeds.
The purpose of this is to break complicated problems into tasks that each take less than a day to complete and have a clear definition of done. It also lets customers have something tangible every 2-4 weeks that they can provide feedback on. I'm finding more and more that the older model of development where the customer is required to provide an exhaustive specification, and then must wait months before they see anything, which might not match what the customer had in their head, results in poor products and strained business relationships.
What scares me is a LOT of this is common sense. I have experienced some folks doing some of these, once in a blue moon.
The most common issue, Agile or not, that I have experienced:
1) Not having an update and reason
2) Not raising or escalating on a road block in a timely fashion
3) Not showing up for meetings on time or being engaged
4) Not working with the team but doing Ye' olde ME ME ME
Thanks for reminding me why I will never work for corporate America. Thank God I invested in real estate!
Thank you Naresh, I'm glad you found value for your offshore teams. We missed a few good practices but this gives a team a great start!
Late 2019 and still relevant. Thanks for the video ;-)
Agile is a good excuse for incompetent managers to pass accountability and responsibility to others.
Interesting perspective Mao. How about this?
Agile is a good framework for competent software developers to take responsibility for the results of their work and be held accountable for it instead of passing that responsibility to mangers?
Love your replies Molood!
@@molood6185 excellent reply
Wow, a corporate training video that I actually like!
This reminds me what I hated most about the agile environment... the condescending attitude of managers treating professionals as if they were schoolchildren.
There was no manager in this video.
you do not have manager in SCRUM. you have a SCRUM Master, which is there in the video
Then what you were doing was not Agile, no manager
So true. I have been programming for over 20 years and we started doing this where I work. Hours of pointless, degrading meetings run by someone who doesn't have any understanding of our product or how to code.
Agile never been a good methodology. Agile is not new. The creators just changed the names. Stand up meetings are Check Point and you only do that when it is close to deployment or cutover. Sprints are releases. Scrum is the weekly status meetings where you review the issues, risks and project status. Many managers fall into this thinking it is a new methodologies. It is actually a way for the creators to make money. Standup meetings is just check points and the PM just go over quickly his check point list and get a quick status. No need for all this theatre.
Such a great agile coach. I wish I got this type of training.
My organisation hired an agile coach. But he didn't do any of this. He just prepared a KANBAN board on JIRA instead of Agile sprints.
Moreover he did not even classify our project in correct categories.
Watching it after 11 years !!!
More of these simulations please!!
Great video. My team struggles with stand ups; will be viewing this at next PI Planning Iteration!
Some people seem to think these kinds of things do not happen ina professional work environment. Having worked in the IT world for decades, I can tell you that there is a whole generation that doesn't get "Professional" some seem to think its the same as being in school or in their own little social group.
stand-up scrum meeting? hold on a sec.. some folks are not standing :-)
Oh my God! I love this simulation!!!!! :)
could someone tell me where to find videos 4-17 because there seem to be only videos 1-3 and 18 & 20.Urgent
That was a great example, I learned a lot from this!
This is good exercise for those who believe and follow agile.
I graduated college in 1982 with a degree in electrical engineering and worked as a contractor since 1990 working on commercial avionics products like air data computers, inertial navigation systems, windshear detection systems, as well as medical devices like implanted defibrillators and immunoassay systems. This agile scrum nonsense is dangerous considering how it puts time pressure on people to show that they accomplished something for the next infantile daily meeting and the distractions of the constant context switching. Agile scrum, more than anything else, makes me glad to be nearing retirement. Does anyone think they can implement a kalman filter from scratch in one of those infantile two week sprints?
Hi Sally, Great Video. Made me laugh and Cry...Daily Standup so true.
I am not agreed with her methods bud she is out off date i am agreed with u Dave c.
Very good example of the Do's & Don'ts
Excellent. Thank you
Despite the second stand up being more focused it still felt like faux agile.
Brilliant! but how come one of the guy assigns time duration(2 days) to a task while the sprint is going on? Should it not have already be done earlier in Sprint planning meeting?
That's not an estimation that he puts on the task. It's a commitment date. In Agile you estimate the "complexity of a task or user story". When you start working on that task or story, you can commit to finish it by a specific date. Writing the date on the sticky note helps visualize impediments easier, because if the task is not complete by the commitment date, the team members will be alerted and help out with completing that task. This commitment data at a task level is basically a facilitator that helps team members understand whether their initial estimation of complexity has been realistic or not. If a task proves to be less complex than what's estimated, it would hopefully be finished before the commitment date, and if it's proven to be more complex than the estimation, the team will be notified and run to help :)
M Khan very good question and I'm really glad Molood responded with great clarity and precision.
Damn! I thought the daily scrum can be as they did the first time!
very funny, i would pay to see this guy!
This is real standup.. but never seen like this 😂
Well, stand up is about synchronizing work within a team and scrum master is to facilitate the team. Reporting to scrum master instead of updating their colleagues about progress is wrong. So guys, you have learnt how a frame od stand up should look like, but you forgot to understand a purpose.
Awesome video
I'm still new to the concepts, though I feel more appreciative. Depends on the individual scrum master, of course... But I think the principle about respecting everyone's abilities is number ONE. Also, an SM could probably also be trained and given other responsibilities, or have one of the lead programmers do the meets.
Love this video!
Aldo hilariuos it is a pretty god representation of reality...
Man so many of the responses seem to completely miss the point of Scrum Masters and who does what in the team, falling back into very old mindsets (Being old myself I can recognize it from as far back as the 1970's) I don't care much for the theatrics in some Scrum Stand ups but if you tone it down a bit to the appropriate age group (young Coders seem to get into the theatrics) I've seen it done right and wrong and it definitely can make a difference if done right and be an impediment if done wrong, and it isnt just the Agile Team that needs to be on board, the Outside managers, directors and executives need to know to allow the process to work and not to micromanage. I do agree that the whole agile concept has allowed a whole new group of people to make money, that does not mean this process does not work....even if you Coders and Developers are Old and have been doing this a long time. Inflexibility and inability to accept change will have you on the outside looking in. Keep the good, accept the new good and ignore the rest. My 3 cents.
Thank u Sally for bringing us to daily stand ups meeting
Very useful....Thank you
This was very helpful
perfect work scenario. thank you very much
We call an "interested person" a fly on the wall instead of chicken.
This is so helpful, funny and explanatory. Welldone guys
Amazing work. Where can I watch part 5 to part 19? They're not in this playlist.
Awesomne!
Whats the practice, if the done columm is filled and is getting messy?
A perfect example.
Oh wow... thanks a bunch.. this was very helpful!!
I can see this video has been released under creative commons i was looking for the correct attributions and CC license please can you provide :)
How dare John actually bring up legitimate concerns that will effect every aspect of the project. Dude just chill and get your paycheck lmao
Bc he's going on and on ..in technical DETAILS.
beautiful
Who is arranging the meeting ? Scrum master or Product owner ?
How to make incompetents seem competent. Competent teams know how to do their work and just do. Problem is when you hire the wrong people and need to keep them in check. The issue is the competent people suffer and that's not fair.
Vlad-Marian Marian agile is focused on Lean approach to quality delivery and collaborative team work
Very good thanks
what a great training video.
Great video but is this office located upstairs from a nightclub? What's with the doof doof music?
Okay this is fun, I like to be able to work in such environment!
What is the job of scrum master really? Do u think the meeting cant run without SM?
neotheone exactly, developers always see the big picture and are always so organised and great at planning
It can. The scrum master is supposed to monitor that the meetings take place. Basically he/she steps in whenever he/she sees a violation of the scrum methodology.
Both parts mean how not to do a Daily Stand Up Scrum Meeting....! Daily Scrum Meeting is not a STATUS REPORT Meeting!!!!
Is there any way I can get a transcript of the video?
The standup meeting of our dreams
great video
Why is there music all through the video?
Ha ha! Great video!
good video to understand stand up
I love the experience
TERAVEYYAKAH!!!!!!! KON KAH KAH KANT KAH KAH KAHHHHHHHHHH!!!!!!!
i liked it.
great
Standup meetings. The worse idea since Advertising.
Stand ups are actually fairly tolerable compared with backlog grooming, and retrospectives are the ultimate worst. I hate the retrospectives.
it is stupid. Standup is check point and you only do that when you are close to deployment and if needed.
The goal is to not use your phone for 15 minutes.
it's understood
is the scrum master in this meeting or he/she is just washing what is going on
You have to be silennt observer else if you talk your will be facing resistance and gossip will be there who speaks
Did someone delete my question/comment? Mhmm....
How are you five minutes late on the second minute of the video?
Hyb y ytau
susuior
XI VAJ
We have only kanban board in jira..😀 not like this, sticky notes
If this nonsense ["Agile"] ever finds its way into embedded and safety critical software development then I'm quitting. Fortunately, engineers in those fields think a lot more scientifically and so are less likely to take this substanceless dross seriously.
Unfortunately, now that nine years have passed since your comment, it is being inflicted on engineers who design and test embedded safety critical software. I graduated college in 1982 with a degree in electrical engineering and worked as a contractor since 1990 working on commercial avionics products like air data computers, inertial navigation systems, windshear detection systems, as well as medical devices like implanted defibrillators and immunoassay systems. This agile scrum nonsense is dangerous considering how it puts time pressure on people to show that they accomplished something for the next infantile daily meeting and the distractions of the constant context switching. Agile scrum, more than anything else, makes me glad to be nearing retirement.
gosh what is this waste of time >.< Does this thing really happen in bigger companies ?
cool vid
Ooluu
uulJu
HOW ABOUT STANDING FOR 15 MIN
Whats was the team leader doing except repeating the same question - ?
That was not the team leader. She was a scrum master. Her main role in this meeting was to facilitate the meeting.
yeah and she did a pretty bad job of it !
why angular2 team did not use agile ,scrum ? when you develop very complex software agile is not useful
Agile was designed for average developers, or lazy developers, not for intelligent, experienced and independent one.
Why not?
Just focus what it being told and do that
great thing!!
Good but need a covid update, that isnt considered a “healthy” standup anymore.
Why is that the case, can you please explain?
@@diogoleite8151 COVID-19 few million people dead and now these buddy team-building rituals have to be done online
Dont worry we are back to normal
Audio is very bad!!!
This kind of drama, I don't like in work. I hate scrum.
Scrum is supposed to be a process of managing a project. But here people are talking about process to have this process. Unnecessary time waste and this is a way of getting some work for nontechnical people who usually don't find themselves busy in office. And when someone raise voice against it they say you don't actually understand scrum. What is the mathematics there that people don't understand, God only knows.
Audio is VERY bad!!!!!!!
Does anyone really practice Agile at this level?
we have very good standups with three teams, so, yes, it's not rocket science
also, at some point no need for the SM here. They'll go smoothly on their own
literally less than 8 ft apart and cant even catch a ball thrown at 5mph at the most....how sad smfh
This is not realistic, this would never happen. This company is dysfunctional at the core!!!
What a waste of time. I refuse to work someplace that practices this bullshit.
Well why are u here watching this video
Lolz
what a waste of time
bS Bs bs. Obviously a SCRUM sales video.
NO
Standing up is not important people in wheelchairs do just fine
This Agile Scrum is one of the biggest bull shts I have ever seen. Well BitCoin is even bigger. But this Agile Scrum comes in close 2nd. I mean what real software project can actually be done in such a time wasting childish way!
the main reason for the bulshit is to make sure there is no greater bulshit when u roll out ur product. i guess that will be disastrous! lol.
this is just a business making money and people who are new in the industry think this is new. They created this methodology just to make money but it is now new