{"id":17070,"date":"2026-08-19T10:14:38","date_gmt":"2026-08-19T10:14:38","guid":{"rendered":"https:\/\/oes.com\/uk\/?p=17070"},"modified":"2026-08-19T15:21:06","modified_gmt":"2026-08-19T15:21:06","slug":"agile-execution-why-speed-and-quality-are-not-opposites","status":"publish","type":"post","link":"https:\/\/oes.com\/uk\/agile-execution-why-speed-and-quality-are-not-opposites\/","title":{"rendered":"Agile execution: Why speed and quality are not opposites"},"content":{"rendered":"
\n
\n
\n\n
\n

\"Leading<\/p>\n

An exciting new online programme has taken shape. Market research that predicted strong demand has proved correct and thousands of students have enroled before launch. The proposition promises to be both groundbreaking and commercially significant.<\/span>\u00a0<\/span><\/p>\n

Then the build begins to slip.<\/span>\u00a0<\/span><\/p>\n

Content arrives late. Approvals become bottlenecks. Teams wait on one another. Quality checks are compressed, and the fixed launch date draws ever closer. What looked like a strategic success is suddenly at risk.<\/span>\u00a0<\/span><\/p>\n

At this point, institutions often feel forced to choose between moving quickly and accepting compromises or protecting quality and risk missing the moment.<\/span>\u00a0<\/span><\/p>\n

The Agile Execution chapter of <\/span>Leading with SCALE: A framework for resilient digital higher education<\/span><\/i><\/b><\/a> challenges that assumption. Speed and quality are not natural opposites. More often, it is rigid processes that make them appear that way.<\/span>\u00a0<\/span><\/p>\n

The full SCALE guide sets out five interconnected pillars for building sustainable digital capability: Strategy First<\/a>, Collaborative Design<\/a>, Agile Execution, Learner-Centric Quality<\/a> and Evergreen Innovation<\/a>. Strategy establishes the direction and Collaboration creates shared ownership. Agile Execution turns that alignment into progress without allowing urgency to erode standards.<\/span>\u00a0<\/span><\/p>\n

The problem is not always the deadline<\/span><\/b>\u00a0<\/span><\/h2>\n


\nHigher education projects rarely unfold in a straight line because subject matter experts (SME) are balancing competing responsibilities and approval cycles can be complex. Requirements change, feedback arrives late and dependencies appear only once the work is under way.<\/span>\u00a0<\/span><\/p>\n

Yet many digital learning projects are still managed through linear processes in which one stage must be fully completed before the next can begin. When a delay occurs early in the chain, every team downstream feels the impact.<\/span>\u00a0<\/span><\/p>\n

That is when pressure builds, and quality assurance starts to feel like a final obstacle rather than an integral part of development.<\/span>\u00a0<\/span><\/p>\n

Agility offers a different way of working.<\/span>\u00a0<\/span><\/p>\n

\u201cAgile execution isn’t so much about asking people to work faster as about creating a process that can absorb change,” says Arlene Stewart, Director of Academics and Operations at OES UK. ” Applied well, agility exposes risks earlier and keep progress moving without losing sight of academic quality.\u201d<\/span>\u00a0<\/span><\/p><\/blockquote>\n

Agility is structure, not haste<\/span><\/b>\u00a0<\/span><\/h2>\n


\nFirst coined in 2001 as an innovative and effective software development methodology, the term \u201cagile\u201d is sometimes misunderstood as shorthand for speed, informality or constant change.<\/span>\u00a0<\/span><\/p>\n

Within SCALE, it means something more disciplined: breaking complex work into manageable stages, creating regular opportunities for review and allowing different areas of the project to progress in a coordinated way.<\/span>\u00a0<\/span><\/p>\n

The need for this is particularly acute in UK higher education. Nine in ten vice-chancellors report unprecedented uncertainty combined with a desire for rapid growth, yet many institutions continue to rely on linear planning and sequential delivery models. The SCALE guide\u2019s central insight is that agility is less about accelerating every task than about building the resilience to respond when plans inevitably shift.<\/span>\u00a0<\/span><\/p>\n

The difference becomes visible when something goes wrong.<\/span>\u00a0<\/span><\/p>\n

In a rigid process, one missing approval can stall an entire build. In an agile one, teams have a clearer view of dependencies, and work can continue in parallel. This allows problems to be identified while they are still manageable rather than during a high-stakes review.<\/span>\u00a0<\/span><\/p>\n

Where traditional delivery begins to break down<\/span><\/b>\u00a0<\/span><\/h2>\n


\nThe SCALE Guide was developed by OES based on over 15 years of working with institutions. In that time, we’ve seen the same patterns emerge from delayed content and changing requirements to variable academic staff availability.<\/span>\u00a0<\/span><\/p>\n

The <\/span>Agile Execution<\/span> chapter explores how institutions can redesign those workflows and shows how institutions can create momentum without stripping out the reflection that quality depends on.<\/span>\u00a0<\/span><\/p>\n

An agile project reorganises the work so teams can:<\/span>\u00a0<\/span><\/p>\n