Insights

In my years of leading SAFe transformations, one concept stands out as the single most impactful structural pattern: the Agile Release Train. It is not merely a team-of-teams construct — it is the heartbeat of how large organisations can deliver value continuously and predictably.

When I was working with Sky TV & Broadband on their large-scale SAFe transformation, the challenge was clear: multiple portfolios, dozens of teams, and a complex web of dependencies that made predictability feel impossible. The ART became the answer — not just as a structure, but as a cultural shift toward shared ownership and collective intelligence.

At Barclays, the challenge was different but the principle was the same. Globally distributed teams separated by time zones needed a unifying rhythm. By optimising ARTs and leveraging JIRA Align for dependency management, we created a system where cross-team collaboration became seamless, and delivery timelines improved significantly.

The Three Pillars of a High-Performing ART

1. PI Planning as a Sacred Cadence. Programme Increment Planning is not just a meeting — it is the event where strategy meets execution. I've learned to manage PI Planning through meticulous checklists, clear agendas, and centralised dependency boards in MIRO. The magic happens when teams see their work in the context of the whole.

2. Servant Leadership at Every Level. The Scrum Masters and RTEs who make ARTs work are not project managers by another name. They are servant leaders who proactively identify and resolve dependencies, foster transparency, and drive smooth programme execution.

3. Continuous Improvement as Culture. Every PI retrospective is an opportunity to inspect and adapt not just the product, but the system of delivery itself. The best ARTs I've coached are the ones that never stop improving.

The ART does not create agility — it creates the conditions for agility to emerge.

In seventeen years of coaching teams across financial services, telecommunications, and technology, I've observed a consistent truth: the organisations that transform most deeply are the ones led by people who understand that leadership is an act of service.

At Lloyds Banking Group, I had the opportunity to coach teams, Scrum Masters, and Product Owners through a period of significant change. The results — a 42% improvement in team performance — were impressive on paper. But the real transformation was subtler. It was in the Product Owner who stopped dictating priorities and started facilitating discovery. It was in the Scrum Master who learned to hold space for difficult conversations rather than rushing to solutions.

What Servant Leadership Looks Like in Practice

It is uncomfortable. Servant leadership requires you to resist the urge to direct and instead create the conditions for others to lead. At Barclays, working with globally distributed teams across time zones, I learned that the most impactful thing I could do was not solve problems, but ensure the right people were in the right conversations.

It is measurable. Empathy is often dismissed as a soft skill, but its impact is quantifiable. Through continuous feedback loops, process improvements, and creating psychological safety, the teams I coached consistently showed improved velocity, reduced cycle times, and — most importantly — higher engagement.

It scales. The servant leadership principles that work in a single Scrum team are the same ones that make an Agile Release Train effective. When I facilitated SAFe Lean Portfolio Management at Sky, the leaders who embraced service over control were the ones whose portfolios aligned most naturally with organisational strategy.

Empathy is not a soft skill. It is the hardest skill we practise — because it asks us to set aside our own certainty and truly listen.

The Agile coaching world is at an inflection point. The same organisations I work with — enterprises navigating complex SAFe transformations — are simultaneously navigating the implications of generative AI on their workflows, their teams, and their very understanding of what productivity means.

Having spent considerable time with tools like ChatGPT (including custom GPTs and prompt engineering), Claude, Perplexity, and Notebook LLM, I can say with confidence: AI is not replacing the Agile Coach. But it is transforming our toolkit in ways we should embrace thoughtfully.

Where AI Adds Value

Retrospective Pattern Analysis. After years of facilitating retrospectives, I've started using AI to analyse anonymised feedback across multiple sprints, identifying recurring themes and sentiment shifts that human pattern recognition might miss.

Backlog Refinement Support. AI can help Product Owners draft user stories, suggest acceptance criteria, and even flag potential dependency risks — saving hours of preparation time while improving consistency.

Learning and Development. Custom GPTs can serve as on-demand coaching companions for Scrum Masters between sessions, reinforcing concepts from courses like SAFe, ICAgile, and Kanban certifications.

Where AI Falls Short

AI cannot read the room. It cannot sense the unspoken tension in a PI Planning session. It cannot build the trust needed for a Scrum Master to have a courageous conversation with a Product Owner about prioritisation. The human element of coaching — empathy, presence, intuition — remains irreplaceable.

The best tools make us better humans, not better machines. AI should free us to do more of the deeply human work of coaching, not less.

In my years at Advance Agility, coaching organisations like American Express, John Lewis, and Pepsi, I discovered that the most transformative conversations often started not with Scrum or SAFe, but with a simple question: "Where does your work actually wait?"

Value Stream Mapping is the practice of visualising every step in a delivery process — from idea to production — and measuring the ratio of active work time to wait time. The results are almost always sobering. In one engagement, we discovered that 68% of total cycle time was wait time: approvals, handoffs, queues, and environment provisioning.

Why VSM Changes Everything

Unlike velocity, which tells you how fast teams are moving, VSM tells you where the system is broken. It shifts the conversation from "How do we make teams faster?" to "How do we remove the waits that slow value delivery?"

The power of VSM workshops is that they create a shared understanding across silos. When product managers, engineers, and operations teams see the same map, alignment becomes natural rather than forced.

Velocity measures how fast teams run. Value Stream Mapping reveals whether they're running in the right direction — or running in place.

My journey from CCS University in India, where I studied Physics at both undergraduate and postgraduate levels, to becoming an Agile Coach in London might seem like an unusual one. But looking back, the connection is more direct than you might think.

Physics taught me to observe systems without assumptions. To form hypotheses and test them. To accept that the elegant theory I'd constructed might be completely wrong when confronted with data. These are not just scientific principles — they are the foundations of effective Agile coaching.

The Scientific Method in Agile

Observe without bias. Just as a physicist observes phenomena before theorising, a good coach observes team dynamics before intervening. The best insights come from patient observation.

Hypothesise and experiment. Every process change is a hypothesis. Every sprint is an experiment. The retrospective is where we analyse results and adapt. This is the scientific method in action.

Embrace uncertainty. Physics taught me that at the quantum level, certainty is an illusion. Similarly, in complex organisational systems, the most honest thing a coach can say is: "I don't know yet — let's find out together."

Science taught me how to learn. Agile gave me a reason to never stop.

One of the most rewarding parts of my work at Lloyds Banking Group was delivering ICAgile-certified courses specifically designed to help Product Owners understand the true nature of their role. The confusion between product ownership and project management is pervasive — and it undermines Agile adoption more than any other single factor.

A Project Manager asks: "Is it on time and on budget?" A Product Owner asks: "Are we building the right thing, and does it deliver value?" These are fundamentally different questions, and they lead to fundamentally different behaviours.

Coaching Product Owners for Value

Through backlog refinement coaching, I helped Product Owners shift from output-driven thinking to outcome-driven thinking. We worked on Definition of Done, user story creation, and — most importantly — the courage to say no to features that didn't align with business goals.

The result was not just improved deliverable quality (which improved by 30%), but a cultural shift where the Product Owner became a true business partner rather than a requirements translator.

The Product Owner's greatest power is not what they add to the backlog — it's what they have the courage to leave out.