✦ For everyone, free.

Practical knowledge for real and everyday life

Home

Contingency and Fallback Planning

Contingency and Fallback Planning helps Agile teams prepare for risks by designing backup strategies to maintain project momentum during disruptions.

Contingency and Fallback Planning is the preparation of predefined alternative courses of action to be activated if a specific risk actually materializes despite any mitigation efforts already in place, ensuring the team has a ready, considered response rather than needing to improvise under pressure at the moment a risk becomes an actual problem. It complements mitigation planning by addressing what happens after a risk occurs rather than focusing solely on reducing the chance or severity of that occurrence in advance.


Distinguishing Contingency Planning From Mitigation Planning

Mitigation Acts Before Occurrence

Mitigation planning is concerned with reducing the likelihood or impact of a risk before it happens, aiming to prevent or lessen the problem in the first place.

Contingency Acts After Occurrence

Contingency planning is concerned specifically with what the team will do if the risk occurs anyway, despite mitigation efforts, providing a predetermined response rather than requiring the team to design a reaction from scratch in the moment.

Both Are Often Used Together

For significant risks, mitigation and contingency planning are frequently developed together, since reducing the chance of occurrence through mitigation does not guarantee the risk will never materialize, and contingency planning provides the necessary preparation for that remaining possibility.


What a Fallback Plan Provides

A Predefined Alternative Path

A fallback plan specifies an alternative course of action the team will shift to if the original approach becomes untenable due to a materialized risk, such as switching to a simpler technical solution if the originally planned approach proves unworkable.

Clarity Under Pressure

Because a risk materializing is often accompanied by time pressure and stress, having a fallback plan already thought through in advance reduces the cognitive burden of designing a response while also managing the immediate disruption the risk has caused.

A Basis for Faster Decision-Making

Rather than needing to fully evaluate a new set of options from scratch once a risk occurs, a team with a prepared fallback can move directly to executing a course of action already agreed upon, substantially reducing response time.


Elements of Effective Contingency Planning

Clear Trigger Conditions

An effective contingency plan specifies the precise conditions under which it should be activated, avoiding ambiguity about whether the situation has actually reached the point where the fallback should be used rather than continuing with the original plan.

Defined Roles and Responsibilities

The plan specifies who is responsible for recognizing that a trigger condition has been met and for initiating the fallback response, preventing delay caused by uncertainty over who has the authority or responsibility to act.

Realistic and Actionable Alternatives

A fallback plan is only useful if it describes something genuinely achievable given the team's actual capabilities and resources at the time it might be needed, rather than an idealized alternative that would itself be difficult to execute under the circumstances that triggered it.

Communication Plan for Stakeholders

Because activating a contingency plan often has implications visible beyond the team itself, an effective plan includes how and when relevant stakeholders will be informed that the fallback has been triggered and what it means for expectations going forward.


Deciding When Contingency Planning Is Warranted

Reserved for Sufficiently Significant Risks

Because developing detailed contingency plans requires effort, this level of preparation is generally reserved for risks assessed as carrying meaningful likelihood or impact, rather than applied uniformly to every identified risk regardless of its priority.

Proportional to the Cost of Being Unprepared

The depth of contingency planning applied to a given risk is weighed against the cost of being caught unprepared if that risk occurs, with higher-consequence risks generally justifying more thorough advance preparation.


Maintaining Contingency Plans Over Time

Reviewing Alongside Risk Reassessment

As a risk's likelihood or impact is reassessed over the course of a project, its associated contingency plan is reviewed alongside it, ensuring the fallback remains relevant and realistic given current circumstances rather than reflecting outdated assumptions.

Testing Where Practical

Where feasible, elements of a contingency plan may be tested or rehearsed in advance, increasing confidence that the plan will actually function as intended if it is ever genuinely needed.


Consequences of Neglecting Contingency Planning

Improvised, Slower Responses Under Pressure

Without a prepared fallback, a team facing a materialized risk must design a response in real time, typically resulting in a slower and less well-considered reaction than one prepared calmly in advance.

Greater Disruption From Preventable Delay

The additional time lost improvising a response, compared to executing a plan already agreed upon, can itself compound the disruption caused by the original risk, increasing overall impact beyond what the risk alone would have caused.


Visual Representation

Primary Plan Continued Delivery Fallback Plan Risk triggers

If the trigger condition is met, the team shifts from the primary plan onto the prepared fallback path rather than continuing unprepared. This can be expressed as:

Active Plan = Fallback Plan if Trigger Condition Met , else Primary Plan

Contingency and Fallback Planning ensures this conditional response is fully defined in advance, rather than left to be worked out only once the triggering condition has already occurred.