DemoRiverside is invented. Every figure on screen is computed by the real engines from fixture data, so the numbers are honest about the fixtures and the fixtures are not real.
Capo
Riverside rolloutGated Scrum with an ADKAR overlay
DE
How this project runs

Gated Scrum with an ADKAR overlay

Approval gates at the top, delivery in sprints underneath, change management alongside. One project, three ways of working, bound by scope rather than by compromise.

Breakdown
The levels work is decomposed into
  1. 1
    Phase
    Scheduled
  2. 2
    Work package
    Earns valueScheduledOn the boardEstimated
  3. 3
    Story
    On the boardEstimated
  4. 4
    Task
    On the boardEstimated
Consequences
What this turns on
  • 10 sections in the navigation
  • Approval gates between phases
  • Delivery in timeboxes (off)
  • Work-in-progress limits (off)
  • A critical path and float
  • Earned value and forecasting
  • A locked baseline, so scope changes need approval
  • 52 documents in the set
  • 12 measures computed
Zones
Parts of this project run differently

A zone rebinds part of the method to a branch of the plan. This is what lets one project run gates at the top and sprints underneath without pretending they are the same thing.

  • Delivery squad
    cadenceestimationboardceremoniesmetricsvocabulary
Overlays
Added alongside delivery
  • Prosci ADKARChange management overlay. Adds readiness assessment per stakeholder group, the sponsor roadmap, and resistance management alongside delivery.
Tailoring notes
1 thing worth knowing

Tailoring is a PMBOK 7 principle, so none of these block anything. They are advice.

  • The cadence runs on approval gates but no board is laid out by gate.Switch a board to the gate layout, or swimlane the existing board by phase.
Document set
52 documents
  • Project charterPMBOK6:4.1
  • Project management planPMBOK6:4.2
  • Assumption and constraint logPMBOK6:4.1
  • Change management planPMBOK6:4.6
  • Lessons learned registerPMBOK6:4.4
  • Project closeout reportPMBOK6:4.7
  • Scope management planPMBOK6:5.1
  • Requirements documentationPMBOK6:5.2
  • Requirements traceability matrixPMBOK6:5.2
  • Project scope statementPMBOK6:5.3
  • Work breakdown structurePMBOK6:5.4
  • WBS dictionaryPMBOK6:5.4
  • Schedule management planPMBOK6:6.1
  • Schedule baselinePMBOK6:6.5
  • Milestone listPMBOK6:6.2
  • Schedule network diagramPMBOK6:6.3
  • Cost management planPMBOK6:7.1
  • Cost baselinePMBOK6:7.3
  • Project funding requirementsPMBOK6:7.3
  • Quality management planPMBOK6:8.1
  • Quality metricsPMBOK6:8.1
  • Resource management planPMBOK6:9.1
  • Responsibility assignment matrixPMBOK6:9.1
  • Team charterPMBOK6:9.1
  • Communications management planPMBOK6:10.1
  • Status reportPMBOK6:10.2
  • Risk management planPMBOK6:11.1
  • Risk registerPMBOK6:11.2
  • Risk reportPMBOK6:11.2
  • Procurement management planPMBOK6:12.1
  • Stakeholder registerPMBOK6:13.1
  • Stakeholder engagement planPMBOK6:13.2
  • Stakeholder engagement assessment matrixPMBOK6:13.2
  • Tailoring rationalePMBOK7:Tailoring
  • Development approach and life cyclePMBOK7:Development Approach
  • Delivery approach and value planPMBOK7:Delivery
  • Measurement planPMBOK7:Measurement
  • Uncertainty and ambiguity responsePMBOK7:Uncertainty
  • Benefits realization planPMBOK7:Delivery
  • PMBOK 6 to PMBOK 7 crosswalkPMBOK7:Tailoring
  • Product backlogAgile Practice Guide
  • Definition of doneAgile Practice Guide
  • Release planAgile Practice Guide
  • Change impact assessmentProsci:ADKAR
  • Sponsor roadmapProsci:ADKAR
  • Resistance management planProsci:ADKAR
  • Training planProsci:ADKAR
  • Reinforcement planProsci:ADKAR
  • Change visionKotter:Step 3
  • Guiding coalitionKotter:Step 2
  • Short-term wins planKotter:Step 6
  • ADKAR readiness assessmentProsci:ADKAR