Discussion about this post

User's avatar
Mike Johnson's avatar

Agile at TD Bank is slowing delivery and significantly increasing cost.

We have over-scaled Scaled Agile Framework (SAFe) to a point where the process is outweighing actual engineering work. There are too many coordination roles (SMs, POs, RTEs, Agile Coaches) compared to developers and analysts who actually build and deliver value.

A large amount of time is spent in:

• Multi-day planning cycles for 3 months ahead (which effectively becomes a mini waterfall)

• Continuous alignment meetings and ceremonies

• Maintaining and “beautifying” tools like Jira and Confluence

Despite all this effort, priorities still change, dependencies still break, and teams end up re-planning frequently. The result is increased overhead without a corresponding improvement in speed or outcomes.

The intent of Agile is faster value delivery, but the current implementation is doing the opposite:

• Slower decision-making

• Higher operational cost

• Reduced engineering productivity

At this scale, we are not gaining agility—we are adding layers of process on top of what already resembles a structured, plan-driven model.

It may be time to reassess whether the current level of process, planning horizon, and role distribution is actually helping teams deliver faster, or simply making the system heavier.

1 more comment...

No posts

Ready for more?