Thank you, this actually represents what happens in most traditional organizations. This is partly because there is a gap in understanding among management on what Agile really is and what a scrum master does. Can you please refer to the other video you mentioned about Agile going wrong? Much appreciated, thanks.
Hi, the other video in the series of "when agile goes wrong" talks about change requests. You can find the video at the following link: ruclips.net/video/fCjzcgy0Fzs/видео.html
The Scrum Master likely also does not have the authority or power in an organization to make this happen and higher ups may have to get involved frequently to help when the 'self organizing' team gets stuck or cannot resolve conflict.
I'm still baffled as to how on Earth anti-agile process like Scrum got to be redefined as "the Agile". IT-equivalent of selling the day as "the proper industry-standard version of night", and nowdays it seems everyone is fully bought in to it, wondering why their night is rarely as dark as the original descriptions of night made it seem like. Also, during night, what should I do if I get blinded by the sun? #AgileLife
Thanks, Emal, it is indeed not a great business practice to introduce such a methodology change mid-stream, but what happens to the role of the Product Owner, shouldn't this role be responsible for closing that accountability gap and holding it all together as against the SCRUM Master role?
The product owner in enterpises is normally fulfilled by two people (business owner, and IT owner), and these people will not serve that purpose in most cases.
Take the first step to becoming a high-performing business analyst ⇨ bablocks.com/membership/?ref=2
Thank you, this actually represents what happens in most traditional organizations. This is partly because there is a gap in understanding among management on what Agile really is and what a scrum master does. Can you please refer to the other video you mentioned about Agile going wrong? Much appreciated, thanks.
Hi, the other video in the series of "when agile goes wrong" talks about change requests. You can find the video at the following link: ruclips.net/video/fCjzcgy0Fzs/видео.html
The Scrum Master likely also does not have the authority or power in an organization to make this happen and higher ups may have to get involved frequently to help when the 'self organizing' team gets stuck or cannot resolve conflict.
Totally right. That's why we always need a project manager (or someone who plays the role of a project manager).
I'm still baffled as to how on Earth anti-agile process like Scrum got to be redefined as "the Agile". IT-equivalent of selling the day as "the proper industry-standard version of night", and nowdays it seems everyone is fully bought in to it, wondering why their night is rarely as dark as the original descriptions of night made it seem like. Also, during night, what should I do if I get blinded by the sun? #AgileLife
SCRUM, on its own, certainly has a lot of major gaps. That's why most organizations go for a hybrid approach that works for their specific situation.
Thanks, Emal, it is indeed not a great business practice to introduce such a methodology change mid-stream, but what happens to the role of the Product Owner, shouldn't this role be responsible for closing that accountability gap and holding it all together as against the SCRUM Master role?
The product owner in enterpises is normally fulfilled by two people (business owner, and IT owner), and these people will not serve that purpose in most cases.
And this is more like an accountant in business analysis ?