Agile has been around for about 20 years and has supported significantly improvements within teams. Jeff Sutherland, co-creator of the Agile framework “Scrum” famously described Scrum as “doing twice as much in half the time“.
Most of the success, though, happened within software development teams. And this is to no surprise: The Agile Manifesto of Software Development in 2001 was the first attempt to create a new belief to improve the quality and predictability of Software. Up to then, most software projects failed due to delay in delivery or suddenly increasing costs.
Therefore, a group of thought leaders in the software industry, who all already worked with other development frameworks than waterfall came together and created with the Agile Manifesto a new way of thinking when approaching software development. While there was a lot of effort already done on the framework side of Agile Development (Extreme Programming, Scrum, Crystal, etc.), this Agile Manifesto is often considered the starting point for Agile as we know it today.
Organizational Agility
Many brick & mortar companies are nowadays looking at Agile as a way of new collaboration, cooperation and improved success. Insurances and banks have started and continue to implement cooperation frameworks based on the Agile mindset.
But often those companies fail in their attempt. The thought leaders created Agile to help teams to understand that even if you are planning for years, your forecast and estimation won’t become better. But, if you develop a small piece and ask for feedback as soon as possible, you then can incrementally and iteratively create better products.
Agile is based on the scientific theory of complex adaptive systems: If you are a part of a complex adaptive system, then you might have knowledge about the environment near you. But this will not give you automatically knowledge over the whole system. This is why Agile invites for short feedback cycles, so teams can adjust their plan thanks to newly acquired knowledge. Agile invites also for self-organizing teams, as they have more knowledge about their environment, than their individuals ever can have. Finally, Agile invites for cross-functional teams, so they are not dependent on other functions to move forward and decide iteratively & incrementally for quicker feedback cycles.
The Role of a manager in Agile
Agile was for teams. Nowadays, the whole organization wants to become Agile. But originally, Agile itself does not address one important factor: The Managers. If teams are supposed to be self-organized and cross-functional, why do we still need Managers?
In Agile, the role of the Management changes. While in the past, managers got to that position due to their role in their job, in Agile environment, this does not work anymore. If teams do not understand the system completely, but only their part, the same is true for Managers: Nowadays, most Managers do not have the knowledge about everything anymore. They understand that their team has the better knowledge of their individual tasks and builds the environment for improved collaboration and results.
Agile Teams need to be self-organised, cross-functional and competent to realize the desired value for the customer. As the team is competent, Managers do not need to tell the team anymore, what to do, but rather coach, mentor and lead them towards achieving constantly improved cross-functionality, self-organization and competence. The Manager becomes a facilitator, who nurtures the team to grow.
The 6 Views of Management 3.0
But how would that look exactly in the daily work? Management 3.0 is a set of principles and mindset with practices achieving such a team. It does look at Management in the following six views:
- Energize People – Successful self-organized teams need motivation & engagement. Managers support to develop the right foundations to motivate and engage everybody.
- Empower Teams – Self-organized teams need trust and empowerment from the Managers. To achieve this, Managers need to make delegation decisions.
- Align Constraints – Self-organization can lead to anywhere, if not managed correctly. An organization with enacted values, develops the right constraints to keep self-organization under control. Managers keep the team on the values to grow into the desired culture.
- Learning & Competencies – Agile teams should be competent. To achieve that, Managers would need to find the right balance to address individual as well as team competences.
- Growing Structures – Agile organizations are addressing complex environments. Not every part of an organization needs to be agile. Managers need to balance between diversity, disruption & effectiveness and stability, certainty & efficiency.
- Improve Everything – Complex adaptive systems are constantly adapting to the surrounding environment. Managers need to constantly allow for teams to be able to improve everything to answer those adaptations.
In our Management 3.0 trainings, each of these views address a need of the Manager in agile teams. Every view has several leadership practices applying directly the principles.
