Agile doesn’t work like you think it does

Over time, the concept of Agile delivery has been diluted by a proliferation of buzzwords, antipatterns, miss-selling and bad habits. Many organisations claiming to work in an Agile manner still essentially operate the rigid, outdated command-and-control structures against which Agile was a reaction, creating confusion and uncertainty in the market. Too often, people’s experience of nominally Agile working is that of a purely performative collaboration, with endless ceremonies, dashboards and meetings that focus on activity rather than outcomes and results.

As a result, a set of myths have emerged around how Agile delivery works – with many people showing deep-seated misunderstandings of both the theory, and what the application of Agile should look like in practice. Many supposedly Agile projects are nothing of the sort, and many ostensibly Agile practitioners show scant practical adherence to the practice’s core values and principles. There’s an obvious risk here: if people execute projects poorly under an Agile banner, the methodology’s reputation suffers. Agile practitioners must seek to debunk these myths or face a bleak future. Here’s some of the key fallacies to challenge:

Myth 1: “Agile delivery leaders are just administrators”

Agile professionals are often seen principally as note-takers, schedulers, or Jira managers – the people who organise everyone else’s work. This view misses the point: their real value is not as bureaucrats, but as facilitators and protectors from distraction. Good Agile professionals create the space for teams to focus, and align delivery with outcomes rather than activity.

Myth 2: “Agile professionals are the scrum police”

Some believe Agile delivery operates within a top-down hierarchy, with Agile professionals in place to enforce frameworks and control how team members spend their time. This is quite wrong: Agile professionals work with teams, coaching them to make better decisions, remove friction and build confidence in delivery – without resorting to outdated command-and-control methods.

Myth 3: “Agile delivery must be technical”

It’s a common assumption that Agile delivery leaders require a deep technical background. Technical awareness can certainly help, supporting a deeper understanding of the team’s tasks and challenges, but it isn’t the core of the job. The real skill lies in understanding people and processes, then creating the conditions for specialists to succeed. In most projects, the need is for strong communication and facilitation across the entire team rather than strategic decision-making or technical troubleshooting. Indeed, in some circumstances ‘hands-on’ Agile delivery leaders who think they know best can create conflict within teams, damaging morale and motivation in the process. Think of it like sports: coaches don’t need to run faster than the athletes; their task is to help the athletes run faster.

Myth 4: “Certification equals capability”

A certificate may prove that somebody knows about an Agile framework, but it does not demonstrate that they’re capable of applying it in practice. The best Agile professionals succeed through experience, attitude and ‘soft’ skills. They know from experience how to adapt Agile values and principles to particular circumstances; when to challenge people, and when to simply step back and get out of their team’s way. Like any profession, being truly effective at the job requires skill, practical experience and professional characteristics appropriate for the role. A piece of paper doesn’t make you agile; effectiveness with people and process does.

Myth 5: “Agile delivery leaders are cheerleaders”

Contrary to popular belief, Agile delivery isn’t principally about arranging team socials or keeping everyone upbeat during stand-ups. The value lies in keeping people aligned and focused under deadline pressure and/or changing priorities; after all, no plan survives contact with the enemy. Agile delivery leaders are there to create stability within an uncertain environment: they help teams stay focused on what matters, and shield them from distractions so they can maximise time spent ‘in the zone’. That said, there is value in boosting morale – and championing a team’s achievements is one way to do this.

According to the “broaden-and-build” theory of psychologist Barbara Fredrickson, positive emotions broaden our thought-action repertoires, enabling us to develop skills and resources that improve our long-term productivity. One famous study from the "Journal of Labor Economics" showed that happiness at work leads to improved performance, especially in jobs where creativity and initiative are key.

Myth 6: “Agile delivery leaders must remove all blockers for their teams”

While impediment removal is without doubt a core responsibility for an Agile delivery leader, the reality is that teams solve most of their own issues – perhaps with the assistance of a little coaching or support. Nonetheless, sometimes a challenge is too big, distracting or political for them to handle, and Agile delivery leaders must step in – often by representing the team with stakeholders and at governance layers: this can be helpful in reducing the ‘noise’ around the team and the number of distracting interactions that take team members away from the core task. As captured in the proverb: “Give a man a fish, and you feed him for a day; teach a man to fish, and you feed him for a lifetime,” effective Agile delivery leadership is about enabling, not babysitting.

So Agile is a much more subtle and responsive discipline than the stereotypes present – and it must be led by subtle and responsive practitioners. The approach can generate huge benefits – saving time, handling change more elegantly, reducing project failure rates and, above all, creating better products and services that more effectively meet customer needs and objectives. These goals are achieved by working with people – rather than by tinkering with processes – to surface problems early in the development process, resolve them quickly and with a minimum of fuss, and avoid interfering when the team is already functioning effectively.

Good Agile delivery leaders foster an environment of psychological safety – enabling their teams to be focused enough to stay on track, confident enough to own their work, and insightful enough to learn from their mistakes. This is a role that is very much about empowerment; when they’re doing their job well, much of an Agile practitioner’s work occurs out of sight. So how do you know when you’ve got a really great Agile delivery leader? When their team runs perfectly well without them. This may not sound like the smartest business model for the practitioner, but it’s definitely the best outcome for the client’s own business – and that, ultimately, is what Agile is all about.