Five books every Agile leader should read before they start Agile transformation

To continue my with my book recommendations (check Five books every ScrumMaster should read and Five books every Product Owner should read), I have several books here, I would recommend every Agile Leader and manager in Agile Organization to read before they start Agile transformation. It’s a mix which will help you to understand Agile Leadership, Agile Organization, it’s structure, design, and culture and allow you to adapt to the different leadership style. Enjoy reading 🙂

  1. Niels Pflaeging – Organize for Complexity: How to Get Life Back Into Work to Build the High-Performance Organization is about complexity and work – and about how to deal productively with both. A condensed introduction to the theory and practice of organizational high performance. A manifesto for contemporary leadership and profound transformation in organizations of all kinds. It is “practically theoretic”, featuring cutting-edge insight. It proposes new language and thinking for a new way of work and organizations.
  2. Frederic Laloux – Reinventing Organizations is a must. The way we manage organizations seems increasingly out of date. Survey after survey shows that a majority of employees feel disengaged from their companies. The epidemic of organizational disillusionment goes way beyond Corporate America-teachers, doctors, and nurses are leaving their professions in record numbers because the way we run schools and hospitals kills their vocation. Government agencies and nonprofits have a noble purpose, but working for these entities often feels soulless and lifeless just the same. All these organizations suffer from power games played at the top and powerlessness at lower levels, from infighting and bureaucracy, from endless meetings and a seemingly never-ending succession of change and cost-cutting programs.
  3. Large-Scale Scrum: More with LeSS is looking at the organizational design from a different perspective. Rather than asking, “How can we do agile at scale in our big complex organization?” a different and deeper question is, “How can we have the same simple structure that Scrum offers for the organization, and be agile at scale rather than do agile?” This profound insight is at the heart of LeSS. In Large-Scale Scrum: More with LeSS, Craig Larman and Bas Vodde have distilled over a decade of experience in large-scale LeSS adoptions towards a simpler organization that delivers more flexibility with less complexity, more value with less waste, and more purpose with less prescription.
  4. The Responsibility Process: Unlocking Your Natural Ability to Live and Lead with Power is about FREEDOM, POWER, and CHOICE. Leadership is innate. The Responsibility Process proves it. The Responsibility Process is a natural mental pattern that helps you process thoughts about taking or avoiding responsibility. How you navigate it determines whether you are leading toward meaningful results or just marking time. This book gives you precision tools, practices, and leadership truths to navigate The Responsibility Process and lead yourself and others to freedom, power, and choice.
  5. Leadership and Self Deceptions shows how most personal and organizational problems are the result of a little-known problem called self-deception. Through an entertaining and highly instructive story, Leadership and Self-Deception shows what self-deception is, how people get trapped in it, how it undermines personal achievement and organizational performance, and- most importantly the surprising way to solve it.

BONUS:

Finally, there is a bonus book which I wrote a few years after this blogpost 🙂 The Agile Leader: Leveraging the Power of Influence Book published in December 2020 will help you to unleash your agile leadership potential and guide your entire organization toward agility. It’s a great overview of concepts for managers, directors, executives, and entrepreneurs―anyone, regardless of position, who’s ready to take ownership, challenge the status quo, and become a true agile leader. See more at https://greatagileleader.com.

Five books every Product Owner should read

To continue my with my book recommendations (check the five books every ScrumMaster should read, and five books Agile Leader shall read), I have several books here, I would recommend every Product Owner to read. It’s a mix which will help you to understand Agile Product Ownership, Discovery and delivery process in much broader perspective. Enjoy reading 🙂

  1. Impact Mapping: Making a big impact with software products and projects is a practical guide to impact mapping, a simple yet incredibly effective method for collaborative strategic planning that helps organizations make an impact with software. Impact mapping helps to create better plans and roadmaps that ensure alignment of business and delivery, and are easily adaptable to change. Impact mapping fits nicely into several current trends in software product management and release planning, including goal-oriented requirements engineering, frequent iterative delivery, agile and lean software methods, lean startup product development cycles, and design thinking.
  2. Agile Estimating and Planning is the definitive, practical guide to estimating and planning agile projects. In the book, Agile Alliance co-founder Mike Cohn discusses the philosophy of the agile estimate and planning, and shows you exactly how to get the job done with real-world examples and case studies. This book is a must-have agile estimation tool for your development toolbox.
  3. User Story Mapping: Discover the Whole Story, Build the Right Product shows you how changeable story maps enable your team to hold better conversations about the project throughout the development process. Your team will learn to come away with a shared understanding of what you’re attempting to build and why. This insightful book examines how this often misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features.
  4. Innovation Games®: Creating Breakthrough Products Through Collaborative Play is a must-read for anyone involved in market research and product or service development (which, when you think about it, means virtually everyone). Innovation is incredibly simple. All you have to do is accurately predict what your customers want, need, and will pay for. Oh, wait. Sorry. That’s actually very hard. At least with traditional tools. So how do you find this information? Well, you can just ask your customers what they want. The problem, of course, is that with most truly breakthrough innovations, current and potential customers don’t actually know what they want before they see it. If you just try to deliver what they already want, you’ll never truly innovate. Even worse, traditional market research practices prove that often, customers have trouble articulating what, exactly, they want in the first place.
  5. The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses is about a new approach being adopted across the globe, changing the way companies are built and new products are launched. The Lean Startup approach fosters companies that are both more capital efficient and that leverage human creativity more effectively. Inspired by lessons from lean manufacturing, it relies on “validated learning,” rapid scientific experimentation, as well as a number of counter-intuitive practices that shorten product development cycles, measure actual progress without resorting to vanity metrics, and learn what customers really want. It enables a company to shift directions with agility, altering plans inch by inch, minute by minute. Rather than wasting time creating elaborate business plans, The Lean Startup offers entrepreneurs – in companies of all sizes – a way to test their vision continuously, to adapt and adjust before it’s too late.

Five books every ScrumMaster should read

I have several books here, I would recommend every ScrumMaster to read (check the five books every Product Owner should read, and five books Agile Leader shall 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.

5 reasons why to attend AgilePrague Conference 2018

#1: World-class Program
Several years in a row we managed to achieve high-quality program while keeping it affordable to the people in the Czech Republic. This year you can be looking forward to awesome speakers – for example: David Hussman, Roman Pichler, Evan Leybourn, Marsha Shenk, Yves Hanoulle and many more.

#2: Business Agility Focus
The theme for this year is Business Agility. Agile is more than an IT process. We are going to talk about Agile transformations, scaling, the new ways of running your products and businesses, Agile Leadership, collaborative culture and great teams.

#3: Coaches’ Clinic
You can discuss any area you are interested in and get free help from experienced coaches at our Coaches’ Clinic. It is a unique and free service designed to help you with specific challenges you’ve encountered on your way to a more Agile way of working.

#4: Open Space
AgilePrague Conference is not just about listening. We want you to participate and come up with your own session. Every mid-day there is an open space where you have an opportunity to share ideas, discuss topics with each other and join a deep dive conversation with our speakers. Open space is an opportunity to create your own program and bring your own topics to the conference.

#5: Visit Prague
Prague is an awesome city, so why not combine the sightseeing & conference? Have a beer, wonder though old town & narrow streets, enjoy one of the greatest historical cities 🙂

Looking forward to seeing you on Sep 10-11, 2018 at AgilePrague Conference! Register for Agile Prague 2018.

Is Agile for us?

It seems to be a very common question. In general, if you are willing to change yourself, yes. There is no bigger enemy than yourself. There is no environment, size or business restrictions. Any company can change if they find a strong enough reason for a change. However, there are few questions which can help you to identify if you are ready or not.

Agile is not for us if…

  • We are looking for “magic” that helps us deliver everything faster.
  • We want to allocate individuals on tasks based on their specialization.
  • We focus on a buyer-supplier relationship and customer acceptance.
  • We focus on specification, requirements, and change requests.
  • We optimize for local efficiency (individuals, component, technology).
  • We just want to be “modern” and copy some terminology (tribes, squads, etc.).

Agile is for us if…

  • We are ready to build real self-organizing stable teams.
  • We are ready to form real cross-functional teams.
  • We are ready to build a partnership with customers and looking for feedback.
  • We are ready to focus on fast value delivery in a working product.
  • We are ready to optimize for adaptiveness, flexibility and change responsiveness.
  • We are ready to change our way of working to achieve some strategic goals and sustain the current complex world.

The first list is grounded in a misunderstanding of what the Agile and Scrum is about and leads to “Dark Scrum”. The second implies a significant change of your approach, values, the way of work, simply the change of mindset. It’s up to you 🙂

Difference between manager and leader

Leader and manager, what is the difference? Is there any? People are often mixing these terms up so let’s make it more clear.

Leader- LeaderFirstly, managers shall be leaders. That’s where the confusion is most likely coming from. But leaders are not just managers, leader is not a position, anyone can be a leader. In an Agile organization where hierarchy is becoming less important, we take more focus on leadership than management. There is no authority given to a leader. They gain it by their actions and behaviors and by their service to the people around them. Leaders could be anywhere in your organization and their power grows by respect of others. Managers, on the other hand, are often associated with decision making, and certain power which must be given to them.

Leaders are key to any Agile organization. The more leadership is in the organization, the more likely the mindset will change and the Agile transformation will become successful.

“Leaders need to change first. The organization will follow. “

Don’t wait for anyone, you are the leader you can change today. Agile is not about practices, rules, or processes. Agile is about the different way of thinking, different way of approaching things, different mindset. And it’s all in your hands. You are the leader.

Contracts in Agile and Scrum

One of the very common questions I got at my trainings is how to do agile contracts. In a traditional world where there is neither trust nor collaboration, the contract is the key. It must be detailed enough so we can defend ourselves or blame the other party. Agile is trying to change this contract game, heal the relationship and build a partnership.

In the agile world with high trust and transparency, I believe the traditional contracts shall be abandoned. They are not needed anymore. In my business, we exchange a couple of emails, have a call or scribe a few notes in a Google Doc to make sure we understand each other and collaborate. We treat each other as partners and share with high transparency and honesty that needs to be shared. On contrary, the more organizations spent effort with me on writing a formal contract, the less likely we did any business together. Not because I would make it difficult and argue with lawyers, I usually signed, but I guess they didn’t have the primary focus on the business.

On the other hand, Agile is not preventing you from using any contract at all, so everything starting from

“Fixed time, cost, and scope & you pay fee if you don’t deliver it this way”

to

“We want to work together as partners, help each other, be honest and transparent.”

can work. Though some contract will distract you from delivering value and other will help you with that. It’s always your choice. You can keep the status quo and contracts or change the mindset of not only yourself but your customer (including lawyers).

For some bigger software deliveries, we did frame contract with NDA, a general link to the way of working and tools to be used (Continuous Integration, Backlog management, etc.). Such contract pretty much said we keep certain standards. And that we collaborate to identify and deliver scope. Any details, content, and problems were discussed at the time they emerged.

In summary, my recommendation is to spend your valuable time on building relationship and partnership. Increase transparency, understand each other, collaborate. If you still feel you need to read more, read Agile Contract Primer or join Agile Prague 2018 Conference.

What is Agile Leadership

What is agile leadership about? How would you define it, how would you explain it? Those are just a few questions people are asking these days.

Agile leaders are able to inspire others, creates and communicate an appealing vision or a higher purpose which motivates organization and would constantly be looking for better ways of working through feedback. It’s about being inclusive, support others on their leadership journey. Being open to new ideas, experiments and innovations. Support creativity. Be able to garden the right mindset and creates cultures based on collaboration. Agile leader is a coach and good listener.

Agile leadership is not about tools, practices or methodologies. It’s an ability to look at the organization from the system perspective, understand system dynamics, be able to get awareness about what’s happening, embrace it, understand it and become an integral part of the system and finally be able to act upon and influence it with coaching, and initiate a change.

Agile Leadership Model

New management paradigm is about collaboration and trust, decentralization, continuous adaptation and flexibility, cooperation and teamwork. From the static management in the industrial era, we shifted to strategic management in last twenty years of the last century and moved quickly into the dynamic management which tries to keep up the speed with modern constantly changing, complex world. That’s the world which critically needs agile leadership as anything else is not flexible enough to deal with nowadays challenges. Companies need more creativity, collaboration, and innovations – simply agility. That’s the way how to be successful. That’s the way how to achieve their goals. That’s the way how to survive and don’t become new dinosaurs who are so huge, slow and inflexible that they eventually disappear from the world.

It’s all about the relationship

Some time back I went through the ORSC – Organizational Relationship and System Coaching and wrote this article to share my learning with the Agile community. Now it’s time to share some experiences. I tried most of the concepts with maybe few exceptions (like Deep Democracy). I kind of digested the overall idea and simplify it back in my mind into “it’s all about the relationship”. I still remember my first ORSC class when one of the facilitators come and reminded us of not to coach the problem but the relationship. I looked at her with surprise. “If the relationship is strong, it will solve all the problems itself,” she said and I got my first aha moment. I guess it took me much longer to truly understand that.

As a time went I realized, that the whole idea of coaching the relationship and looking at organization and team from the system perspective is the key to 99% of my work with organizations, teams, managers and leaders and ScrumMasters. The ability to look at things from the top detached from details and stop evaluating what is happening, because “who knows what is right and what is wrong” and “everyone is right but only partially” was enlightening. It gave me a freedom in a sense and allows me to be much more effective in changing the organizations and working with leaders. As I wrote in the Great ScrumMaster: #ScrumMasterWay book, one of the key metaskills ScrumMasters need is curiosity, have a culture anthropologist mindset. This simple change in the approach will unblock the most of the ‘unsolvable’ situations. And it’s not only true for ScrumMasters but Agile Coaches, managers, and leaders of the organization.

Look at the organization from the system perspective. Don’t evaluate. Be curious. Focus on inproving the relationships.

Have a good team spirit and collaborative mindset. Good relationships solve the problems and enable the organizational success.

My intention was not to explain you any ORSC techniques as you need to experience them in several days program followed by your practical implementation but start a conversation with fellow Agile coaches about their experiences with ORSC and the need of ORSC in the Agile space.

So, if you write your experience with ORSC in a short text, I publish it or link it from here and if that goes well, maybe we can create a blogs series about ORSC@Agile.

The hot topic of the next few years will be leadership

Modern world brings not only the different way of developing software called Agile but also changes in the organizational structure and leadership. You see it more and more often. People at the classes are asking why their managers are not there to hear the message. But very often they are, and they are ready to change the entire organization and their leadership style.

ShuThe ‘Shu’ level of Agile transformation is focused on practices and individuals or teams. How can we start? As a result, we create small isolated islands of Agility where we get to experience and learn more about what does it mean to be Agile. Sometimes companies are looking for shortcuts. But you can’t skip this level. It’s your foundation. If you make it solid, you are more likely going to be successful with Agile at the organizational level. At this level, you might see some improvements, but can’t achieve greater efficiency across the whole organization.

HaThe ‘Ha’ level of Agile Transformation is when you start Scaling phase. This is where the Business Agility starts to take place. That’s where the different leadership starts to be critically needed as you have to grow the different structure and mindset. The key focus is shifting towards how to develop leaders and how senior employees are growing within a company. As the right culture is getting its place, people are coming with innovative creative ideas which can make a difference in the company results. This situation is currently the biggest challenge we are facing now as an industry and its topic of many discussions. Together with Scaling frameworks (like LeSS – Large Scale Scrum) which address the organizational design, we talk about different Agile management practices, Agile HR, Agile in marketing, Agile in finance. Companies that understand this can create an environment that is more efficient, productive, and more successful than anything we have ever achieved with classical management methods.

RiFinally, the ‘Ri’ level of Agile transformation starts when the Business Agility is the normal way you operate your business. We have individual Agile leaders in the organization, and people take over initiatives. This is a time for another organizational shift. At this stage, we have a true Agile executive team, focusing on long-term strategy and Agile Board of Directors focusing on the purpose and vision both working as teams collaborating together. Both truly living Agile values.