How a leading children's hospital trained 400+ employees in Agile in three months

A leading pediatric healthcare organization wanted to expand Agile beyond its technology teams and build a consistent way of delivering value across healthcare operations, business functions and technology. In three months, Agile Brains trained more than 400 employees in healthcare-specific Agile and helped establish a common Value Delivery Framework connecting organizational priorities to team execution and measurable outcomes.

The challenge

The task was not simply teaching employees Scrum or Kanban. The organization needed a shared language and a common way of working that could operate inside the realities of healthcare, where clinical and operational priorities, regulatory requirements, technology dependencies and limited capacity constantly intersect.

Agile knowledge varied widely. Some employees had worked on Agile technology teams; others came from operational and business functions built on traditional project management. The result was inconsistent terminology, different approaches to planning and prioritization, limited visibility into work across functions, difficulty translating strategic priorities into team-level execution, and too much emphasis on completing activities rather than measuring value delivered. Capability had to be built quickly, and training had to change how teams actually worked.

How we helped

Healthcare-specific Agile training. Agile Brains designed and delivered an accelerated Agile in Healthcare learning and enablement program tailored to the organization. Rather than generic certification training, the curriculum connected Agile principles to real healthcare delivery challenges, covering mindset, value-driven delivery, Scrum and Kanban, roles, backlog management, user stories, prioritization, iterative planning, flow of work, stakeholder engagement, continuous improvement and Agile metrics, all through healthcare-oriented scenarios and exercises. Over three months, more than 400 employees across business, operational, technology and delivery roles completed the program.

A common Value Delivery Framework. Training was the starting point. We then worked with leaders and teams to translate it into a practical framework that runs from strategy to priorities, value, work, delivery, outcomes and learning. Strategic and operational priorities were translated into defined outcomes; outcomes informed prioritized work; work was organized into manageable backlogs and delivered incrementally; results were reviewed against meaningful measures and fed back into priorities. Teams with planned, product-oriented work adopted a Scrum cadence, while teams facing continuous operational demand used Kanban to manage flow, giving enterprise consistency without eliminating team-level flexibility.

Coaching to make it stick. Agile coaches reinforced the learning through team formation, role clarification, backlog development, prioritization, Jira configuration, sprint and flow management, ceremonies, metrics and retrospectives. Training plus application plus coaching moved the organization beyond Agile vocabulary toward sustainable delivery capability.

The result

In three months the organization built Agile capability across its workforce without a prolonged multi-year program, and business, operational and technology teams now share one framework for connecting priorities to work, delivery and outcomes. The most important outcome was not the number of people trained. It was the shift from learning Agile to working differently.

What the organization gained

• 400+ employees trained, with a common understanding of Agile, value delivery, Scrum, Kanban, prioritization and iterative execution
• A three-month accelerated rollout instead of a multi-year training program
• One common Value Delivery Framework linking organizational priorities to work, delivery and outcomes
• Healthcare-specific Agile practices, adapted to operations rather than borrowed from software development
• Common terminology, roles, planning concepts, backlog practices and delivery expectations across teams
• Internal capability that can keep expanding as additional teams adopt Agile ways of working