Five books every ScrumMaster should read

I have several books here, I would recommend every ScrumMaster to read. It’s a mix which will help you to understand ScrumMaster role in much broader perspective. In addition to the ScrumMaster guidebook which summarizes all you need to know to become the great ScrumMaster, you need to get better at forming great teams, team coaching, servant leadership and change management. Enjoy reading 🙂

  1. Great ScrumMaster: #ScrumMasteWay is a guidebook for all ScrumMasters, Agile coaches and leaders who want to transform their organizations. It’s intended to give you a reference to general concepts which every ScrumMaster should understand and point you towards resources which may help you in resolving difficult situations. It was designed as a slim illustrated book, which you can read during the weekend and won’t get lost in too much heavy stuff. However, it is supposed to be your starting point in searching for help or ideas on where to go next. On top of that, it’s full of practical examples of how to apply each individual concept.
  2. The Five Dysfunctions of a Team: A Leadership Fable is the world’s most definitive source on practical information for building teams. The Five Dysfunctions of a Team outlines the root causes of politics and dysfunction on the teams where you work, and the keys to overcoming them. Counter to conventional wisdom, the causes of dysfunction are both identifiable and curable. However, they don’t die easily. Making a team functional and cohesive requires levels of courage and discipline that many groups cannot seem to muster.
  3. Coaching Agile Teams: A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition is a guide to the role of Agile Coach. Most people are wondering, “What is my role in a self-organized team?How do I help the team yet stay hands-off?”  Many respond by going too far to either extreme.  Coaching Agile Teams turns these questions into answers, and answers into action by offering practical ways to adapt skills from professional coaching and other disciplines to coaching agile teams toward high performance.
  4. Turn the Ship Around!: A True Story of Turning Followers into Leaders is how-to manual for managers on delegating, training, and driving flawless execution. Since Turn the Ship Around! was published in 2013, hundreds of thousands of readers have been inspired by former Navy captain David Marquet’s true story. Many have applied his insights to their own organizations, creating workplaces where everyone takes responsibility for his or her actions, where followers grow to become leaders, and where happier teams drive dramatically better results.
  5. Our Iceberg Is Melting: Changing and Succeeding Under Any Conditions has all you need to know about the change management. It is a simple story about doing well under the stress and uncertainty of rapid change. The tale is one of resistance to change and heroic action, seemingly intractable obstacles and clever tactics for dealing with those obstacles. The penguins offer an inspiring model as we all struggle to adapt to new circumstances. After finishing the story, you’ll have a powerful framework for influencing your own team, no matter how big or small.

Agile Leaders are the beginning of modern management

In order to achieve success at the organizational level, we need to start management talent development program to create leaders who will help to grow a company, make quick decisions and stay ahead of others. Modern leadership style is no longer applying the traditional model of the “leader-follower”, i.e. one decides and the other executes orders. Nowadays, when most employees are from the category of creative workers and the company is looking for innovation and creative ideas to stay competitive, the leader-leader model is a more effective one, where the leaders’ main goal is to help others to be successful leaders. What is modern Agile management or Agile leadership about?

Excellent Agile Leader has four core competencies: Ability to define the vision, motivate, gain feedback, and ability to influence through themselves, others and system.

The ability to formulate a vision is the engine of change and motivation. A vision is not necessarily linked to product and business but should be focused on the organization and its purpose. The second competency is the ability to motivate and give the energy. It is a competence closely related to the vision. If you have a good vision, it motivates itself. Agile leadership builds on so-called internal motivation to strengthen the autonomy of individuals and teams. The third of Agile leader’s competences is feedback. Feedback is DNA component for Agile Organization together with openness and transparency. The art of getting system-level feedback is critical for the leader. The last is the art of influencing complex environments. Change things, people and their behavior, support and consolidate culture. Agile leadership begins with a change of self, your judgments, values, and behavior, style of work. Great leaders start with themselves as a role model, to change the way they show up, how they interact with others, and how they can inspire people around them to collaborate, create a team spirit, and become leaders. They are capable of working with the entire system and influence the whole organization and its culture.

Agile Leader-Wheel

Agile Leader Wheel also defines four supporting competencies to help leaders define the right approach. When is it better to decide and when decisions can be delegated and it’s better to collaborate. At the same time, when it’s better to take a role of facilitator and when start coaching. We do not talk that much about coaching individuals, which of course may be useful, but coaching the whole system – teams and organizations as a whole. Excellent Agile Leaders have not been born as Agile Leaders, but they are constantly looking for new ways to get better and to gain and strengthen the above-mentioned competencies.

Agile Adoption Story – Common Mistakes (part 6)

And finally, to finish the agile adoption story, even though the team is after all able to find their way to communicate, share knowhow, learn from each other, and cooperate, there is another obstacle. Surprisingly it’s not outside the company but in the business unit internally.

Company doesn’t need to change

The company doesn’t need any change. It used to be working good for many years, and if we had observed any problems, they were indeed located in the ICT, so why should we change the business unit? Isn’t Scrum called software development methodology?

Oh, yes, Scrum is business driven, but here are the requirements, so take them as they are and if you need to make any User Stories out of them, sure, feel free to do it. But we are not really interested in your internal processes so don’t bother us. However, we expect you to finish all this work on time.

So the teams are desperate again. Unless they got Product Owner, who is willing to become part of their team, and share the risk and success with them, they can’t proceed with real Scrum. They can’t take all responsibility and gain success in return.

Unfortunately, some get frustrated from the lack of business support and still complaining “Agile is not for us”. We are different, we have too complex product, we are too big/small to implement agile. Our customers are like this and that, and you know, agile is great, just for a different company.