Fallback Plan

A preplanned backup set of activities to use when the main approach must be dropped because of problems, realized risks, or other disruptions.

Key Points

  • Prepared in advance and documented with clear triggers, owners, and step-by-step actions.
  • Activated when the primary plan becomes impractical or unsafe, often including rollback or switch-over steps.
  • Requires reserved resources, approvals, and communication plans to execute quickly.
  • Different from a workaround (unplanned quick fix) and from mitigation actions (taken beforehand to reduce risk).

Example

During an ERP go-live, severe performance issues make the planned cutover unworkable. The team enacts the fallback plan: roll back to the legacy system, extend the parallel run for two weeks, notify stakeholders, and schedule a new cutover window after fixes.

PMP Example Question

During deployment, a critical service outage makes the planned cutover impossible. The team executes a documented rollback and temporary manual processing steps defined ahead of time. What is this called?

  1. Contingency plan
  2. Fallback plan
  3. Workaround
  4. Mitigation strategy

Correct Answer: B — Fallback plan

Explanation: A fallback plan is a preapproved backup course of action used when the primary plan cannot proceed. A workaround is unplanned, and mitigation reduces risk before it occurs; a contingency plan addresses a specific risk event.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your Agile career!

HK School of Management helps you learn Agile and Scrum with practical playbooks, AI-powered prompts, and real-world workflows for planning and delivery. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More