We’ve talked recently about Corporate Rebels and the impact they’ve had on us on our Corporate Rebels blog post.
But because most of us at Clear Star have a background in Agile, our interest in Corporate Rebels has caused us to challenge some of our thinking and preconceptions around Agile. So we thought we’d capture these and explore where Agile might need to go in order to stay relevant and valuable.
Let’s explore this using the 8 trends from Corporate Rebels.
From profit to purpose & values
There are two interesting elements to this. The first is at an organisational level – am I working for a company that is doing something I believe is important and that motivates me and provides meaning for my work, and are there clear company values to influence and support decision making at every level.
The second is a more local consideration – am I working in a team whose purpose (responsibility) is clear and motivating and where it’s clear how this contributes to the overall purpose and objectives of the organisation. This is where I think Agile has moved the conversation on, but also failed. Teams that are properly setup to own a product or service, who have direct connectivity to their customers, and whose success is measured based on the value delivered to their customers, are hugely empowering, rewarding and motivating to work in.
However our experience is that this rarely happens when organisations and teams adopt Agile. Teams end up being 2 or 3 steps removed from their customers and success is measured in story points or features delivered. Our view – these are miserable teams to work in and are not aligned to the spirit and outcomes that Agile is trying to achieve.
And the same goes for the values espoused by Agile. While these are broadly positive, they are often neglected. Frequently trampled under the adoption of practices, or even worse, are imposed or forced on teams.
From hierarchical pyramid to network of teams
The adoption of Agile often brings with it the idea of the team as the lowest level organisational unit. Along with team objectives or goals and the concept of collective success and failure.
But the challenge often comes in scaling, in two dimensions.
Firstly, how to get multiple teams to collaborate on products or services that are too big for a single team to deliver. A range of “scaling” frameworks claim to have an answer here. But they all have the creation of a hierarchy in common. One where “senior” product people look at the bigger picture and co-ordinate or lead the product people in each team, disempowering the teams and becoming an interface between the teams and the customer. We think there’s a space for a new model, built around some of the Rendanheyi concepts exemplified by Haier; networks of teams with relationships built on the delivery of value and with collective responsibility for delivery to an end customer.
Secondly, how do Agile teams fit into the wider organisation? What we often see are Agile teams operating within a traditional organisation hierarchy. In our view Agile has never had an answer for how organisations can adopt a structure built entirely around teams. This change is hugely disruptive for middle and senior management and their view of their role. But as anyone that’s seen a truly effective leadership team at work can attest, it can deliver transformational organisational performance.
From directive leadership to supportive leadership
Another area where Agile talks a good game; servant leadership, transitioning from management to leadership, the great leadership stuff in Agile 2.0 – are all on the money, but are often neglected or ignored in companies adopting and implementing Agile. Sometimes you’ll see local change, but as Agile transformations struggle to expand, the wider corporate management culture is often unimpacted. This compromises the ability of teams to be agile.
From plan & predict to experiment & adapt
Surely this is a slam dunk for Agile, which is built on the idea of experimentation, iteration, reflection, and adaptation? Maybe not if you’re an Agile team working to a fixed cost, fixed timescale, fixed set of outputs – responsible for the delivery of a plan, rather than the delivery of value to a customer. Again, the root cause of this is usually “Agile” teams working within a traditional organisation, which means decisions on money, resourcing, priorities, and governance are taken elsewhere.
From rules & control to freedom & trust
Here’s where we think the adoption of Agile most often and most fundamentally fails. It’s where the the focus is entirely on the adoption of the practices of a chosen framework. Suddenly teams are under the yoke of a thousand rules on what they should and shouldn’t do.
Practices are a useful starting point for helping teams to understand some of the principles and values associated with Agile. But they must have the freedom and trust to own their ways of working and to change these as required such that they work for them. That might mean every team in your organisation working and operating in a slightly different way. As long as you have sufficient fixed points that enable co-ordination and transparency, you will have happier, more empowered, and more productive teams.
And don’t get us started on corporate mandated tools – apparently vital so that there is clear enterprise visibility to enable strategic decision making. In our experience, this is about rules and control. No strategic decisions are made. No-one actually looks at the data. Teams just suffer using tools that don’t fit the way they want to work. It generates hours of busy work, and the whole process reinforces the idea that teams are only there to churn out features.
From centralized authority to distributed decision making
Positives – Agile allows teams to own their plan for how they achieve their objectives, rather than working to a plan imposed on them that everyone knows is unachievable and doomed to failure. But that’s a tiny first step. Until you have true delegation of business decisions (something that could start with the creation of product or service teams), and a clear organisation decision making framework that creates transparency and shared understanding, you’re scratching the surface of the benefits that can be achieved.
This will (probably) also require the breaking of the hierarchy. Any model where teams are “empowered” by seniors, but where that empowerment can be removed or overridden, is no empowerment at all.
From secrecy to radical transparency
Another of the trends that, on the face of it, relates closely to Agile. The reality and implementation is often challenged by a lack of trust and leadership. Teams criticised because their velocity has dipped this sprint, or hauled over the coals because they prioritised high business value at the cost of delivering a feature a few days later than an arbitrary milestone.
Transparency has to be supported by cultural change. Acceptance that things sometimes don’t go to plan, that failure is a chance to learn, and that everyone can be open and honest about bad news without fear of consequences or retribution.
From job descriptions to talents & mastery
In our experience, this is a fundamental challenge with the adoption of Agile. Everyone is given new job descriptions (Product Owner, Scrum Master, etc.), but with the barest of training as to what their new role is. Let alone the ongoing support and investment to enable them to develop and master.
In summary
I think this quote from the Corporate Rebels book probably summarises the core of the challenge; “While the foundations of the agile movement are sound, and valuable, the way many companies practice it is simply wrong”. In our experience, the cause is usually the same – implementations are focused on the practices espoused by a chosen framework, rather than on the values and principles that underpin them.
But the problems go further than that. Agile has struggled to break out of its original niche of IT software delivery. Even to the next step of having teams organised around and responsible for products and services, let alone to an holistic view of how an entire organisation should operate. This often means that adoption ends up sitting within a traditional organisation structure and operations model, preventing the organisation from realising the expected benefits.
Next Steps
So what has this period of reflection meant for us? Firstly, it has supported and re-enforced the approach we take with our clients – starting with principles, and then exploring a range of practices (including many Agile ones) to help them understand how these principles may be realised, and empowering them to adopt (and shape) the practices that best fit their needs, context and people.
This approach has allowed us to support a number of clients that had adopted agile, but struggled to get the value from it, and were now not sure about where to go next. By helping them understand what they were trying to achieve and the principles and values that were important to them, we’ve been able to help them to identify the changes required to their practices that have then allowed them to move forward.
If you’re interested in discussing any of this further, or would like some help or support in how you can unblock your agile adoption, then please reach out to us.
