The number 9

STEP 9

Fragile Spots (Critical Assumptions)

Every assumption that could break the plan is marked as fragile.

Examples:

  • “Assume API gives full history”
  • “Assume credit score provider can refresh daily”
  • “Assume legal allows upsell banner”

These must be tested in the first sprint.

They are not risks, they are guaranteed sources of rework unless tested.

Activities

  • Short assumption review
  • Assign testing/ownership

Frameworks / Tools

  • Assumption mapping (importance vs evidence)
  • Risk radar
  • Technical debt register

Outputs

  • Critical assumptions map
  • Fragility register
  • Owners + actions to de-risk early

Who attends

  • Product Lead
  • Architect
  • Engineering Lead
  • Delivery Lead

How long

  • 45 minutes

Notes

This is quick.
Your dependency map already reveals most fragile areas.