Starting the Agile Journey

Understand Scrum is simple. If you don’t know what Scrum is and is not, there is a 17-page definition called Scrum Guide. If you like to know what is agile, go to the four values and 12 principles of Agile Manifesto. The agile community mostly agrees on both. As large products increase the complexity, there is no common agreement on how to apply agile and scrum to multiple teams and organization as a whole. The good news is that there are many options to choose from and many organizations can serve as inspiration on jour journey – Menlo Innovations, Zappos, Valve, Odde, ScrumAlliance, and I can continue. The first two are even often organizing visits to see how they work.

Agile Journey

In agile we love options and know, there is no one way how to do things. Some options are easier to apply, some harder, some less agile, some more. But remember Agile is not your goal, it’s just the way how to achieve your strategic goals so at the end of the day it doesn’t matter. The less agile ways are not necessarily bad options for given circumstances. Some companies go faster, some slower on their agile journey. Your organization needs to be internally ready for the higher level of agility and without direct experience with self-organization at the team level (across the organization at product teams but also at the executive teams and boards), it’s hard to go forward towards the organizational agility, Agile HR, Agile finance, and last but not least Agile leadership. I started this article by referring to the Agile and Scrum definitions. Would the definition of an Agile Organization be useful? It may look that way however I don’t think it’s needed. The Agile organization is not about practices, processes, not frameworks. It’s about being agile. It’s about agility hardcoded in the organizational DNA and culture. It’s about living the values. Be courageous to change the status quo, be open to feedback, respect different opinions, and have focus and commitment to deliver value not only to the customers and shareholders but also employees. So if you want to check your readiness to apply agile principles at the organizational level, start with the values. Do you like them? Do you live them? Or do you think they are not important?

Agile Board of Directors

Are you also wondering why you shall be Agile and your board of directors and the executive team is not? I wrote about Agile at the executive team last time, now it’s time to have a look at the board of directors.

There is no real reason why the board of directors should not act as an Agile team. Just the habit as most of the directors of the board are coming from the traditional companies and had never experienced it. The governance is important, but the usual committee structure presenting a report to the board each quarter doesn’t help them to react to challenges. I did this presentation at several different organizations, and I thought it might be useful to summarize the key points here as well.

Let’s start with an overview of what any Agile entity needs: Have Agile values of transparency, trust, respect, collaboration, and a shared understanding of a purpose so people are having the same goals. Simply be a great team, not just a group of individuals. But applying radical transparency, get feedback and collaborate is often very hard at this level. Not that it would not be useful, but it’s not going to be easy. Secondly, the board must be consistent with the organization. If Agile stops at the board level, it creates a gap within the organization and governance inconsistency and the whole organization will struggle. Finally, Agile boards are not just governance bodies, Agile boards of directors create a purpose-driven organizations, the sense of belonging which skyrockets organizations success. Having said so, it’s critical that Agile boards collaborate on the key strategic initiatives with the rest of the organization, which if you think about it is very far from filtering anything in and out of the board through the CEO. There are three principles of the Agile board of directors:

#1 Team over individuals and hierarchy

While traditional organizations are formed by stable departments and individuals, Agile organizations form communities build around the purpose. Internally there is usually a quite liquid structure to keep adaptivity and strategy focus in the nowadays complex world. It embraces the team as the key building unit and forms a collaborative network of teams. Similarly, the board of directors is a team which has one goal, even if internally there is a structure of the committees, each committee is a collaborative team as well where all the committee chairs and the board chair are acting more like facilitators then managers of the group. The board as a team is just a small part of the whole picture. We use the ‘team in the team’ concept in Scrum having a Development team being part of the Scrum team, being part of the product team once you scale, and such product teams being part of the entire organization which acts as a team or collaborative network if you wish, where all those pieces only stay together with a strong purpose which creates a common goal for everyone. The same way the board shall form a collaborative team with CEO, the BoD together with the CEO shall form a team structure with management and eventually the entire organization. Too much hierarchy kills the collaborative mindset and a team spirit. There is always going to be some hierarchy in the organization, but maybe the way of work may not be driven by the hierarchy – but the purpose, collaboration, having the radical transparency as a pre-requisite.

#2 Flexibility over fixed plans and budgets

The more are we responsive to changes through the collaboration, the higher need for adaptiveness is in the organization. Agile organizations are moving from year fixed budgets into the Beyond Budgeting principles. Valuing the purpose driven continuous planning over annual top-down fixed goals and plans.  You will see more voluntary based virtual teams over fixed departments or speaking about the board the committees. People are groping around the common cause instead of the fixed plan while the planning is a continuous inclusive process instead of a top-down annual event. Anyone shall be invited to join when they have something to add to the purpose of the event. Keep it transparent, inclusive, open. All that is an iterative process with regular feedback and an opportunity to inspect and adapt.

#3 Strategy over operational

The good board shall be focused 80% on strategy and significant business issues, 20% reporting. Nothing new, right? It’s the same old 80/20 rule which we often used in the Agile product ownership, organization in general or economy. The Agile boards are going through significant shift refocusing into strategic over operational. Don’t take me wrong, the governance is important. The same as the importance of the processes in the Agile Manifesto: “While there is value in the items on the right, we value the items on the left more”. The same applies here. Reporting is part of the transparency. It shall almost not be even needed if the transparency is there as everyone can just see it. The board doesn’t have to meet to get a status. They shall meet to discuss, understand each other, have creative conversations, visionary sessions, give feedback. The boards shall meet frequently every 1-2 months (that’s their Sprint time), and focus on a communication and work between meetings. There is no need for reporting, all the documents shall be visible so you save a meeting for conversations about the direction. Similarly to the product environment, the shorter Sprints ends up with better understanding, feedback, and higher delivered value.

Finally, keep in mind that the less fixed is the structure and the plan, there is a higher need for a good facilitation, as without it you might end up in the chaos.