Scrum is just another leadership attempt

Lets put a finger on some hard spots: Scrum is no silver bullet! It will not fit in every situation. On top it will not be the best solution for every situation. Whenever the humans in the organisation aren’t ready to accept and internalize the mindsets behind Scrum, it will not work.

Next spot i want to look at is what i call the holy knowledge how it should be. The Scrum Guide leaves much room for the implementations. This is on purpose. There is room for finding the best fitting solutions for every problem you and the organisation encounter. You can’t expect that two randomly implementations of Scrum are exact the same. Ok, you can, but you will be disappointed! No two organisations have the same

  • customers and their needs,
  • employees and their knowledge and needs,
  • roles and rules and
  • relationships and contracts.

Having said this, we must step back and admit, that there can not be a role, event or artefact that has to be exactly as you imagine it or saw somewhere else. Everything may differ. And it is ok! I dare to say everything should differ to fulfill the specific needs.

So lets accept, that Scrum is just an attempt how to solve problems. It is a great one, with many pros. But it is not more than one of many leadership attempts.

What is Scrum for you? Have you stumbled upon somebody stubborn? Let the world know and leave a comment!

Thanks for reading and sharing, hope you enjoyed it!

Divide and Rule in Scrum – the roles

When thinking about Scrum what is coming in your mind first? The Scrum Master? The Sprints? The Product Backlog? Whatever it is, lets have a look on it from another angle: the good old divide et impera or defeat in detail! There are many historical persons who are attributed with it. We will not cover this part here, it could be a longer story :)!

With this blog post i am trying something new – at least a bit new for me: a series of shorter posts on a bigger topic. Let me know, if you like this more or the old way of sooo looong articles!

The roles

One part which i love about Scrum is the separation of concerns (sorry, deep in my heart i am still a software developer) of the roles. On one side we got the Product Owner. She, and only she, is responsible for the “what” is done and the “why” is it done. Business value and its maximization is her key responsibility.

Then there is the Team. Their business is the “how”. Nobody, not even the Scrum Master, can tell the Team how a specific thing has to be done. The Scrum Master has the right to intervene and ask, if there isn’t a better way to do things. But the Team has the final say!

Last but not least we got the Scrum Master. Her sphere of influence is the Scrum framework, its understanding and the living of it in the whole organization in the best way possible. With best possible here is ment, that the Team rises to high velocity and stays there. While we have many smaller parts in the servant leadership of this beautiful role, but in my eyes they fall completely under the correct understanding and living of Scrum and the high velocity of the Team.

Conclusion

Overall for me the Scrum Team is the best example of divide and rule! I love, that for every important part of the business there is somebody personal accountable. That gives Scrum the power it has! In the next blog posts you will read about the events, the artifacts and maybe the rules in Scrum corresponding to divide and rule.

What are your thoughts on Scrum in this point of view? Do you have something else you want to read about? Another perspective or another part of Scrum? Did you liked this blog post? Let me and the world know it and leave a comment!

Thanks for reading and sharing 🙂