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
The document set this method calls for

Documents

0 of 52 written. The set follows the chosen method, so a change of method changes what belongs here.

Documents in the set, with their PMBOK reference and status.
DocumentReferenceAudienceStatus
Project charterPMBOK6:4.1SponsorNot written
Project management planPMBOK6:4.2BothNot written
Assumption and constraint logPMBOK6:4.1TeamNot written
Change management planPMBOK6:4.6BothNot written
Lessons learned registerPMBOK6:4.4TeamNot written
Project closeout reportPMBOK6:4.7SponsorNot written
Scope management planPMBOK6:5.1TeamNot written
Requirements documentationPMBOK6:5.2BothNot written
Requirements traceability matrixPMBOK6:5.2TeamNot written
Project scope statementPMBOK6:5.3SponsorNot written
Work breakdown structurePMBOK6:5.4BothNot written
WBS dictionaryPMBOK6:5.4TeamNot written
Schedule management planPMBOK6:6.1TeamNot written
Schedule baselinePMBOK6:6.5BothNot written
Milestone listPMBOK6:6.2SponsorNot written
Schedule network diagramPMBOK6:6.3TeamNot written
Cost management planPMBOK6:7.1TeamNot written
Cost baselinePMBOK6:7.3SponsorNot written
Project funding requirementsPMBOK6:7.3SponsorNot written
Quality management planPMBOK6:8.1BothNot written
Quality metricsPMBOK6:8.1TeamNot written
Resource management planPMBOK6:9.1TeamNot written
Responsibility assignment matrixPMBOK6:9.1BothNot written
Team charterPMBOK6:9.1TeamNot written
Communications management planPMBOK6:10.1BothNot written
Status reportPMBOK6:10.2SponsorNot written
Risk management planPMBOK6:11.1TeamNot written
Risk registerPMBOK6:11.2BothNot written
Risk reportPMBOK6:11.2SponsorNot written
Procurement management planPMBOK6:12.1TeamNot written
Stakeholder registerPMBOK6:13.1TeamNot written
Stakeholder engagement planPMBOK6:13.2BothNot written
Stakeholder engagement assessment matrixPMBOK6:13.2TeamNot written
Tailoring rationalePMBOK7:TailoringBothNot written
Development approach and life cyclePMBOK7:Development ApproachBothNot written
Delivery approach and value planPMBOK7:DeliverySponsorNot written
Measurement planPMBOK7:MeasurementBothNot written
Uncertainty and ambiguity responsePMBOK7:UncertaintyTeamNot written
Benefits realization planPMBOK7:DeliverySponsorNot written
PMBOK 6 to PMBOK 7 crosswalkPMBOK7:TailoringBothNot written
Product backlogAgile Practice GuideTeamNot written
Definition of doneAgile Practice GuideTeamNot written
Release planAgile Practice GuideBothNot written
Change impact assessmentProsci:ADKARBothNot written
Sponsor roadmapProsci:ADKARSponsorNot written
Resistance management planProsci:ADKARTeamNot written
Training planProsci:ADKARBothNot written
Reinforcement planProsci:ADKARTeamNot written
Change visionKotter:Step 3SponsorNot written
Guiding coalitionKotter:Step 2TeamNot written
Short-term wins planKotter:Step 6BothNot written
ADKAR readiness assessmentProsci:ADKARTeamNot written
How to read this
Approved, draft, not written
Where each document in the set for this method stands, with the version number it stands at.
Reference
Where this document sits in the PMBOK process groups, so a reader can check it against the standard rather than against a house habit.
Audience
Who the document is written for. Sponsor documents get read at a distance, so they carry their own summary.