4.2 Agile Practices and Agile Change Practices

The syllabus treats agile in two places: agile practices, meaning the delivery approach change managers work alongside, and agile change practices, meaning how the change manager's own work adapts. Both are examinable.

What agile is

Often the real-world implementation strategy is a hybrid of two or more of the basic delivery approaches. Agile approaches are characterised by:

• Collaboration and good communication
• Pushing tactical decisions down the hierarchy as far as possible
• Frequent releases
• The expectation of change
• The need to inspect and adapt work

That third and fourth pairing is what distinguishes agile from simply working faster. Agile assumes the requirement will change and builds inspection points to catch it, rather than treating change as a failure of planning.

Common agile concepts, behaviours and techniques

CM3 lists these together, and recall questions draw from the list:

MoSCoW

MoSCoW is the prioritisation technique named in the syllabus:

• M — Must have
• S — Should have
• C — Could have
• W — Won't have for now

The W is the one candidates get wrong. It is won't have for now — a deliberate, time-bounded deferral, not "would like" and not permanent exclusion.

The effective change manager and agile change practices

CM3 lists five behaviours effective change managers should show. These are among the most quotable lines in the syllabus:

• Assess context and apply a mix of change practices as appropriate
• Avoid taking a single framework or model and applying it persistently or rigidly
• Continuously watch for insights from change analytics and process feedback
• Adapt their approaches as the situation evolves, keeping sponsors, leaders and others involved in the change effort fully briefed
• Remain resilient, flexible and willing to learn

Using agile techniques in a change management context greatly helps with adaptability.

Three capabilities

Drawing on Frahm and Ross's The Agile Change Playbook, CM3 identifies three capabilities:

1. Data-informed decision making
2. Continuous engagement
3. Visual and transparent communication

Four core practices

And four core practices:

1. Working out loud — making your work visible as you do it, rather than reporting on it afterwards
2. Change data analysis
3. Visual management
4. The Kanban board

Agile change techniques

The specific techniques CM3 names for change managers:

• Minimum Viable Change Practice (MVCP)
• Visual management tools
• Stand-ups — short, frequent team check-ins
• Retrospectives — structured reflection on what is working and what is not
• Change backlog — a prioritised list of change activities, reordered as priorities shift
• Sprints — timeboxed change work aligned to delivery cadence

Minimum viable change practice

MVCP deserves particular attention because the exam quotes its definition. Minimum viable change practice is "the least effort change intervention that you could make and still accomplish your goals".

Note the wording precisely: least effort, not "minimum work" and not "maximum effort". The principle is proportionality. Where a release is genuinely low-impact, a two-line note in a team channel may be the whole change intervention. Reserving the heavy machinery — training, engagement workshops, impact assessment — for the releases that need it is what makes change management sustainable alongside a fortnightly release cadence.

MVCP connects directly to the delivery-strategy warning that five minutes' work for a software developer could produce a major process rewrite. Applying minimum viable change well requires accurate impact judgement, not simply doing less.

Working out loud

Of the four core practices, working out loud is the one that most changes a change manager's daily habits. It means making your work visible as you do it rather than reporting on it afterwards — an open change backlog, a visible impact assessment in progress, a decision log people can read while the decision is still open.

The benefit is not transparency for its own sake. Work that is visible while it is being done attracts correction while correction is still cheap. A stakeholder who sees an impact assessment mid-draft can say "you have missed the night shift" before the assessment is published, briefed and acted on.

The discomfort is real: visible work invites challenge, and change managers are as prone as anyone to preferring to present finished things. That is precisely why it pairs with visual management and the Kanban board in CM3's list — both make the state of the work legible to people outside the change team without anyone having to ask.

Retrospectives complete the set. A change team that runs delivery sprints but never inspects its own way of working is applying agile mechanics without the inspect-and-adapt behaviour that makes them useful.