YDS: What Should We Do If Leadership Removes the Scrum Master?

In this video, we discuss the implications of C-level leadership replacing Scrum Masters and Product Owners with Technical Product Managers while still practicing Scrum. Combining these roles can create a toxic environment by merging responsibilities for the "what" and the "process." Although the Scrum Guide focuses on accountabilities rather than job titles, this change can lead to dysfunction, with Scrum Master duties likely being neglected. We advise approaching this change cautiously and understanding the full scope of responsibilities involved. For more insights into potential pitfalls, check out "Fixing Your Scrum."
💬 Comment Below:
Share your experiences in the comment section. Let's learn from each other!
👍 Like, Share, and Subscribe:
Enjoyed this video? Hit like, share with your network, and don't forget to subscribe for more insightful discussions on Scrum and Agile methodologies.
Explore more:
📖 "Unlocking Business Agility with Evidence-Based Management: Satisfy Customers and Improve Organizational Effectiveness" on Amazon -- amzn.to/4690qJy
📖 "Fixing Your Scrum: Practical Solutions to Common Scrum Problems" on Amazon -- amzn.to/46dAQTC
✅ Subscribe to this channel for Agile, Scrum, and Kanban insights: www.youtube.co...
🌐 Connect with Agile for Humans:
📘 Website - agileforhumans...
🐦 Twitter - / agileforhumans
🔗 LinkedIn - / agile-for-humans-llc
🔍 The Evidence-Based Company - theevidencebas...
📧 Email - [e-mail]

[@checla]

This experience I had was somehow connected with this case. Once, I joined a company where the first goal to achieve was doing a Scrum maturity assessment. After three months, the evaluation was ready. We had a meeting to present and discuss the results. The CIO, after hearing the results and how it was done, stated, "We don't care about agility! We need to care about quality!". I removed myself autonomously after a little while.😁