Hi mbuhnici! Wow, thanks for catching that un-edited moment :) gota love video editing! glad you liked it, trust me it takes a long time to put all these together and thank you very much for letting me know about that clip!
Hey! Thanks for the videos. I have a question. Do we required stakeholders in the Sprint Review? If not, when do we actually connect with the stakeholders?
Yes, they must be present. You are showing them what value you have created for them that sprint, and the product backlog will be examined to see whether all items are still relevant. That's what's in the scrum guide... but by all means: interact with your stakeholders whenever you feel you need to. Typically the PO will do that, but there's no rule prohibiting the development team to do it as well. The shorter the line of communication, the better.
There's alot of really great concepts in scrum, but the one I have to call out as completely rediculous is the "all must stand for daily scrum" garbage. Its a "good on paper only" triviality (that people be threatened with discomfort, in order to manipulate the meeting into a short time-frame), and it completely breaks down into the farce that it really is when someone on the team has a physical condition that causes significant pain when forced to stand for 15 minutes. Even fairly "routine" discomfort, such as is present with people that may be overweight or have some arthritis, destroys the efficacy of a forced-15-minute time frame, with everyone in pain focusing on how to get the hell out of the meeting, rather than what's supposed to be accomplished in the meeting. Let people be comfortable - if you can't get people to abide by the intent of the meeting and its implied timing, then you've lost the battle already, anyway.
Did you try it? From your comment, I can say no with confidence because you have missed the point. Scrum framework is not about strict rules that should be followed as laws. Scrum is useful in development projects because it emphasizes collaboration and self-organization among team members. Of course, if a member can sit down if he/she has a physical problem.
You are sadly and grossly mistaken - I have intensive and prolonged experience with many variations on scrum/agile-like methodologies, including the popular ones in widespread use. While its absolutely true that scrum/agile-like methodologies call out to "use what works, not insisting on strict rules", that isn't at all what I was talking about - I specifically referred the particular fixation on the 15-minute "everyone stands" thing ... it has never worked in the multitudes of scrum/agile-run projects I've participated in, despite the insistence upon it by those in the roles of "leading the project the scrum/agile way". There's no way to get around the "elephant in the room" (the "I have to stand even though I don't want to" obligation). The minute you allow "flexibility", everyone wants to utilize the option to sit - and in particular, once someone gets to sit, then everyone else resents it unless they get to sit, too. The ONLY way to get people to NOT choose to sit is to MAKE the no-sit-for-15-minutes a MANDATE - and then that itself breaks down for the other reasons mentioned. Getting rid of that practice (the "15-minute-stand" one) is how most of the projects I've participated in dealt with it, and the ones that didn't should have.
I think you should do what proves to be the most effective for your team. If sitting down has a positive impact, I don't see why you shouldn't allow it. I'm sure "Scrum police" will not chase you.
Bassilio Dahlan you pretty much missed every point I made - OF COURSE I agree that we should do what works ... the problem I point out is the whole notion of the "mandatory 15-minutes of standing" that TONS of scrum/agile advocates INSIST should be exactly that (mandatory). Further, a "softer" rule (like a "suggestion") to stand for the daily is meaningless/pointless. What actually works is to ditch the whole notion of "everyone stands for the daily" altogether - why its still called out as a "best practice" in scrum/agile circles is dysfunctional, IMHO.
***** well, my point is that the "everyone must stand" aspect is neither particularly reflective of "openness and courage" (i.e. has nothing to do with it), nor effective. Why *anyone* has to cling to either calling it a "stand-up meeting", or the policy of insisting that everyone stand, seems aggressively irritating to me. That said, I feel that I can agree with what you say (concerning openness and courage), and still hold what I said to be true, with no contradiction.
I am enjoying the explanation. I am learning a whole lot from the videos. That gives me a clearer understanding about Scrum Master.
Well done. people who are engaged to find mistakes will always look to that side and who are really to learn here will focus on learning only.
Getting clearer and clearer ! I'm totally going to start using this system even just for my own personal projects.
This is the finest video series I've seen so far on Scrum training!
True
Its so hard to get started and stay until the terms become familiar- thanks for this video, its starting to make sense now
Very clearly explains the process. One of the best videos
Well done! Highly informative!Thank you.
i am really impressed. very straight forward and simple way to explain whole process... thumbs up from my side
Your videos are all great 👍
Thank you for sharing this information and explaining it.
Liking the way you explain, much thanks
Thanks for such a great explaination
Very useful
Thank you 🙏🏽
Well explained. Thank you.
very informative as it goes in MNCs
Is it adaption or adaptation? Which one please?
i am a big fan of yours mam
Hi mbuhnici! Wow, thanks for catching that un-edited moment :) gota love video editing! glad you liked it, trust me it takes a long time to put all these together and thank you very much for letting me know about that clip!
This is excellent
How long have you been in SCRUM and what do you like about it the most?
I like these videos. But: what was that at 4:51 ?
A nose-picking would have lightened the moment...LOL!
Hey! Thanks for the videos. I have a question. Do we required stakeholders in the Sprint Review? If not, when do we actually connect with the stakeholders?
Yes, they must be present. You are showing them what value you have created for them that sprint, and the product backlog will be examined to see whether all items are still relevant.
That's what's in the scrum guide... but by all means: interact with your stakeholders whenever you feel you need to. Typically the PO will do that, but there's no rule prohibiting the development team to do it as well. The shorter the line of communication, the better.
Yes
Thank you!
There's alot of really great concepts in scrum, but the one I have to call out as completely rediculous is the "all must stand for daily scrum" garbage. Its a "good on paper only" triviality (that people be threatened with discomfort, in order to manipulate the meeting into a short time-frame), and it completely breaks down into the farce that it really is when someone on the team has a physical condition that causes significant pain when forced to stand for 15 minutes.
Even fairly "routine" discomfort, such as is present with people that may be overweight or have some arthritis, destroys the efficacy of a forced-15-minute time frame, with everyone in pain focusing on how to get the hell out of the meeting, rather than what's supposed to be accomplished in the meeting.
Let people be comfortable - if you can't get people to abide by the intent of the meeting and its implied timing, then you've lost the battle already, anyway.
Did you try it? From your comment, I can say no with confidence because you have missed the point. Scrum framework is not about strict rules that should be followed as laws. Scrum is useful in development projects because it emphasizes collaboration and self-organization among team members. Of course, if a member can sit down if he/she has a physical problem.
You are sadly and grossly mistaken - I have intensive and prolonged experience with many variations on scrum/agile-like methodologies, including the popular ones in widespread use.
While its absolutely true that scrum/agile-like methodologies call out to "use what works, not insisting on strict rules", that isn't at all what I was talking about - I specifically referred the particular fixation on the 15-minute "everyone stands" thing ... it has never worked in the multitudes of scrum/agile-run projects I've participated in, despite the insistence upon it by those in the roles of "leading the project the scrum/agile way".
There's no way to get around the "elephant in the room" (the "I have to stand even though I don't want to" obligation). The minute you allow "flexibility", everyone wants to utilize the option to sit - and in particular, once someone gets to sit, then everyone else resents it unless they get to sit, too. The ONLY way to get people to NOT choose to sit is to MAKE the no-sit-for-15-minutes a MANDATE - and then that itself breaks down for the other reasons mentioned.
Getting rid of that practice (the "15-minute-stand" one) is how most of the projects I've participated in dealt with it, and the ones that didn't should have.
I think you should do what proves to be the most effective for your team. If sitting down has a positive impact, I don't see why you shouldn't allow it. I'm sure "Scrum police" will not chase you.
Bassilio Dahlan you pretty much missed every point I made - OF COURSE I agree that we should do what works ... the problem I point out is the whole notion of the "mandatory 15-minutes of standing" that TONS of scrum/agile advocates INSIST should be exactly that (mandatory). Further, a "softer" rule (like a "suggestion") to stand for the daily is meaningless/pointless. What actually works is to ditch the whole notion of "everyone stands for the daily" altogether - why its still called out as a "best practice" in scrum/agile circles is dysfunctional, IMHO.
***** well, my point is that the "everyone must stand" aspect is neither particularly reflective of "openness and courage" (i.e. has nothing to do with it), nor effective.
Why *anyone* has to cling to either calling it a "stand-up meeting", or the policy of insisting that everyone stand, seems aggressively irritating to me.
That said, I feel that I can agree with what you say (concerning openness and courage), and still hold what I said to be true, with no contradiction.
Thanks
excellent. thank you.
Just an FYI, the word is adapTAtion, not adaption...
I am not thinking of our trainer in a pron video. Nope. really, not.