Demo Verification Workflow v3.1

Demo verification is the third layer of progress triangulation — the acceptance anchor.

How It Works

Every 2 weeks (configurable), the system creates a demo session with tasks pending verification. The contractor demos working software to a designated reviewer on the UAT environment.

During the Demo

For each task in the demo:

• Reviewer verifies completion criteria against the live system
• Accept — task earns Earned Value in EVM calculations
• Reject — task returns to in-progress with reviewer notes; a defect is auto-created
• Defer — task moves to the next demo session

Why It Matters

Only demo-accepted features earn Earned Value. Functions that "are done but not shown" earn zero EV. You can't fake a working demo on a UAT environment.

PM360 displays two SPI values:

• SPI (Reported) — based on self-reported progress (optimistic)
• SPI (Verified) — based only on demo-accepted items (the honest number)