First 90 days: how I would run them

Fig 6.1

Six sprints, two gates

S0, weeks 1 to 2 Discovery and mapping
S1, weeks 3 to 4 Rule catalog on a real export
S2, weeks 5 to 6 Dry-run load and traceGo or no-go before this sprint: dry run
S3, weeks 7 to 8 Dashboards and KPIs
S4, weeks 9 to 10 UAT, training, user guide
S5, weeks 11 to 12 Production readiness and hypercareGo or no-go before this sprint: production

Fig 6.1 Six two-week sprints across 12 weeks. Red diamonds mark the go or no-go decisions. Proposed plan.

Weeks 1 to 2

Sprint 0: Discovery and mapping

Agree on what a correct timing plan looks like before checking any row.

Stories

As a PMO lead, I need the legacy export columns mapped to Planisware target fields so the load has a signed specification.
As a program planner, I need the gate catalog confirmed against the timing templates so the gate rule checks the real sequence.
As a configurator, I need the target schema confirmed in the test environment so no rule checks a field the platform lacks.

Acceptance criteria

Mapping table reviewed and signed by the PMO lead
Gate catalog and calendar policy written down
Target schema confirmed field by field

Demo at sprint review

The mapping table and the confirmed rule catalog, walked through row by row.

Risks

Export access takes longer than two weeks
Two programs follow two template versions

Weeks 3 to 4

Sprint 1: Rule catalog on a real export

Run the rules on one real program export and get a first ledger.

Stories

As a PMO analyst, I need every finding listed with the record and a proposed fix so owners get a work list, not a complaint.
As a program manager, I need findings for my program only so I work my own list.

Acceptance criteria

Ten rules run on one real export
SQL twin for every rule, with the cross-check test green
Ledger exported and handed to one program owner

Demo at sprint review

The ledger for one program, sorted BLOCK first.

Risks

Rule thresholds need tuning (drift tolerance, rollup tolerance)

Weeks 5 to 6

Sprint 2: Dry-run load and trace

Load the cleaned program into a Planisware test environment and compare.

Stories

As a configurator, I need each finding traced from legacy row to loaded object so a fix lands in the right system.
As a program owner, I need my fixes confirmed in the dry run so I sign off with evidence.

Acceptance criteria

One program loaded in test with zero open BLOCK findings
Every REVIEW finding carries a decision note
Dry-run differences logged

Demo at sprint review

One record traced from the export, through the rules, into the test environment.

Risks

Import validation in the platform rejects rows the check passed

Weeks 7 to 8

Sprint 3: Dashboards and KPIs

Give the PMO one place to see readiness across programs.

Stories

As a PMO director, I need programs by verdict and blockers per 100 records so I see readiness at a glance.
As an executive sponsor, I need a one-page summary I read before the steering meeting.

Acceptance criteria

KPI definitions agreed
Executive summary prints on one page
Numbers match the ledger exactly

Demo at sprint review

The gate view and the printed one-page summary.

Risks

Reporting tool choice still open

Weeks 9 to 10

Sprint 4: UAT, training, user guide

Prove the rules with users and teach the workflow.

Stories

As a UAT tester, I need scenarios generated from the rules so the test plan matches the logic.
As a planner, I need a short guide and a workbook so I fix my own findings.

Acceptance criteria

Every UAT scenario run and marked
Two training sessions held
User guide published

Demo at sprint review

A tester running three scenarios live, plus the user guide.

Risks

Tester availability during program gate reviews

Weeks 11 to 12

Sprint 5: Production readiness and hypercare

Release the load and watch the parallel run.

Stories

As the PMO lead, I need a sign-off sheet so the go decision has a record.
As a program manager, I need a weekly drift report while the legacy tool stays live so slips surface before steering meetings.

Acceptance criteria

Sign-off sheet complete for the wave
Drift report runs weekly
Hypercare issue log open and owned

Demo at sprint review

The signed sheet, the first production load, and the first drift report.

Risks

Legacy edits continue after the freeze date

Practice

Ceremonies

Daily stand-up: 15 minutes. Yesterday, today, blockers, with the ledger count on screen.
Sprint planning: Stories pulled from the backlog with acceptance criteria written before work starts.
Design review: Mapping and rule changes reviewed with the PMO before code.
Sprint review: Live demo on real data. No slides.
Retrospective: One process change per sprint, tracked to the next retro.