» Scrum Master
We’ve all seen it - Scrum Gone Bad
I think we have all seen Bad Scrum and misuse of the Scrum Framework. Sometimes Scrum started out good with a solid understanding of Scrum, good leadership, an effective Scrum Master, an engaged and empowered Product Owner and a hopeful and open-minded Dev Team. But then somewhere along the way it went bad. Maybe the leadership changed or changed their mind. Perhaps the skillful Scrum Master left and was replaced by one who was ineffective. The team may have soured or felt like Scrum was used against them.
Inevitably, when working with organizations and helping them move from Waterfall to the Scrum Framework, there is a lot of confusion about the Scrum Master role. One of the most common questions I get is, What does a Scrum Master do? People often ask the follow-up question, Can we make our Project Managers the Scrum Masters? (Yes you can but no you should absolutely not.) And third, Do we need a full-time Scrum Master?
The new Scrum Guide, the definitive reference for the Scrum Framework, is out. As of November 7, Scrum co-creators Jeff Sutherland and Ken Schwaber have published an updated version of the Scrum Guide. The last three revisions were in 2011, 2013 and 2016 so this is a relatively fast update since July 2016.
Between Santa Claus, Big Foot and the Agile Project Manager, which exists? Few people argue for the existence of Big Foot or Santa Claus, though most believe that Agile Project Managers exist. I would contend that none of them exist, especially the Agile project manager. (BTW we used a photo of a Wookie for Big Foot since all the pictures we had of Big Foot were blurry.)
I have a client that has been using Agile and the Scrum Framework for the last 3 years. Let me restate that, this client has been using A.I.N.O. (Agile in name only) for the last 3 years. I am working with him to implement Scrum and eventually embrace a full Agile Transformation. With him and his team I have to refer to this as implementing a "more disciplined Scrum" because unfortunately, everyone believes they are already using Scrum.
As an Agile Coach, I find an interesting paradox about Agile Training. Most people will state that they already know all about Agile and Scrum. And if asked, most organizations will say that they are already using Agile, even if what they are doing is A.I.N.O. (Agile in Name Only). Or they will describe what they are doing as "agilish". I am pretty sure that "agilish" in this context means that they aren't following Agile Values and Principles.
Being a Scrum Master or Agile Coach is a challenging job! We've created this page to help you to grow so that you can improve the productivity and effectiveness of your team. Whether it is deepening your understanding of the rules of Scrum, improving your ability to lead scrum events skillfully, or simply hearing stories about coaching that didn't work, we hope you will find the resources on this page useful.
I always thought that crew looked like a cool sport and I've admired crew teams. In crew, team members in lightweight boats race to go as fast as possible. It is hard work! I think the crew team is a useful metaphor for Scrum teams.
Crew teams strive for speed so they keep everything as light as possible by eliminating anything heavy or unnecessary. The more strong people that are rowing, relative to the weight of the boat and everything on it, the faster the boat will go.