Exercising, Testing, and Maintenance
Purpose and types
Exercising builds competence and confidence; testing verifies that components work. Candidates must distinguish the exercise family: plan walkthroughs and tabletop discussions, component tests (call trees, backups, failover), simulation exercises, and full-scale live exercises. Each has a cost and a learning yield; programmes build from discussion-based to operations-based over time.
Design principles
- Every exercise needs objectives, a scenario, a scope, participants, a safety plan, and an evaluation method.
- Evaluation should be against stated objectives, not general impressions; capture observations, gaps, and actions.
- Findings must be tracked to closure with owners and dates; an exercise without follow-up is theatre.
- Maintenance is triggered by change as well as by calendar: reorganisations, new systems, new suppliers, and post-incident learning all force plan review.
- Exercise frequency should reflect risk and regulatory obligation, and should be recorded as evidence.
Traps
- Confusing a tabletop discussion with a live test of recovery capability.
- Running exercises that are designed to pass rather than to reveal weakness.
- Failing to involve senior leaders, so decision-making is never rehearsed.
- No safety or stop conditions in live exercises.
- Closing actions without verification that the fix works.
Rule of thumb
Design each exercise to answer one question: can we actually do this within the required time, with the people and resources we would really have?
Worked example
A firm claims a 4-hour RTO. A tabletop confirms the team knows the steps but proves nothing about delivery. A failover test then shows recovery takes 9 hours. The gap is real, and the RTO claim must be corrected or the strategy upgraded.