How do you think Agile is evolving since its inception in 2001?
I think agile has been evolving steadily, although not always in the way we would like to see.
Hierarchy
One of the central ideas expressed in the agile manifesto, and reinforced through the agile values and principles, is a shift from the traditional top-down management structures to a decentralized environment where decision-making is pushed down to the experts doing the work.
Sure, leadership and executive teams are best positioned to make decisions around strategy, the future of the organization, and the vision for the product, but we want the people who have the most skill, experience, and expertise about how things should be done to make the decisions about how something should be done.
The thinking is that those who are closest to the market and customers, can make decisions that empower us, as an organization, to adapt and respond most effectively.
If the last time an executive spoke to a customer was when they were a software developer, we don’t want them making live, real-time decisions about the customer environment. We want the developers who are dealing with customers daily to make those decisions.
This hasn’t been happening.
Even the most progressive organizations still embrace a top-down hierarchy where senior managers tell junior managers what to do, and those junior managers in turn pass those instructions down to the people working at the coalface.
Many teams, although they have adopted agile, played no role in that decision, nor did they have an option to help choose the agile framework that would best suit their application. It was simply imposed on them along with a set of control-and-command tools to track and manage productivity.
Agile 2.0
We are seeing movement in the transition from traditional management to agile leadership.
I think this is the next area that we will see massive leaps of progress. Organizations are beginning to understand that a team doing scrum is not the same as developing agile capability throughout the organization.
It needs more than a single team. It requires leadership, suppliers, partners, and execution teams to develop agile capabilities and demonstrate agile behaviours.
The concept of ‘rewilding’ agile is getting a lot of attention because people recognize that we need to go back to basics when it comes to agile. Revisit the agile values and principles and stay true to the spirit of the agile manifesto.
Creating products and services that truly delight customers and being able to adapt and respond effectively to disruption or opportunities. That’s the goal. It isn’t about embracing a new style of working to replace an old style of working, it is about embracing responsiveness to opportunity and threats.
Getting out of our own way.
At the turn of the 20th century, we figured out how best to do something and then instructed everyone else to do it the same way.
To ensure that happened, we had supervisors watching every move, and managers supervising supervisors. We created processes, systems, checks and balances to ensure that nobody but the most senior people were able to make decisions or act independently.
As that evolved over time, monolithic structures of command-and-control were created that ensured we couldn’t take a single step out of line without multiple people approving that step.
If the ship needs to go from point A to point B, in a straight line, that’s a great idea.
If the ship needs to adapt and pivot based on conditions, new destinations, or to avoid traps and pitfalls, you’re likely to see that ship sink before it moves an inch off course.
That’s what we have now. Legacy organizations that are so hamstrung by their own processes and systems that people are defeated before they begin to scratch the surface of change. They simply can’t adapt or respond to positive or negative events in the market.
Agile embraces lightweight frameworks that allow organizations to get out of their own way.
To create hyper creative, collaborative, and innovative environments where people can respond to data and feedback, create the most valuable solutions, and resolve the most compelling problems quickly and effectively.
This is where I see the next big shift in agile.
Executive and leadership teams, in collaboration with stakeholders and suppliers/partners transforming the way they do business to facilitate greater agility
About NKD Agility
Naked Agility is an #agile consultancy that specializes in #scrumtraining, #agilecoaching and #agileconsulting to help teams evolve, integrate, and continuously improve.
We recognize the positive impact that a happy AND inspired workforce can have on customer experience, and we actively help organizations to tap into the power of creative, collaborative, and high-performing teams that is unique to #agile and #scrum environments.
If you are interested in #agiletraining, visit https://nkdagility.com/training/
If you have identified the need for #agilecoaching and #agileconsulting, visit https://nkdagility.com/agile-consulting-coaching/
We would love to work with you.
#scrum #agile #scrumteam #agileprojectmanagement #agileproductdevelopment #projectmanagement #productdevelopment #agilecoach #agileconsultant #agiletraining #scrumtraining #scrumorg
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape
Explores effective Agile transformation by empowering teams, improving collaboration, focusing on value delivery, and fostering continuous …
Unmasking Agile: How to Spot Genuine Practices Amidst the Myths
Learn how to identify authentic agile practices, spot common myths, and understand cultural barriers that hinder true agility in modern …
How is agile product development different to waterfall project management?
Compares agile product development and waterfall project management, highlighting differences in decision-making, delivery, customer …
What more needs to happen before traditional organisations consider Agile?
Explores what traditional organisations must change, beyond adopting Agile tools, to achieve true agility, cultural transformation, and …
Why did so many of the early agile transformations fail?
Early agile transformations often failed due to top-down decisions, lack of team involvement, and misalignment between leadership and those …
Evolution not Transformation: This is the Inevitability of change
Change in organisations is a continuous, evolutionary process driven by experimentation and adaptation, not a one-time transformation or …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …