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
People and scope

Change

2 requests waiting on a decision.

1 over fifteen days old
Readiness
Where people are stuck

The barrier point is the first dimension scoring below three. It is the one fact that says whether somebody needs information, motivation, training, practice or recognition.

  • Blocked at desireDana Whitfield, Tom Blaine need a reason of their own to take part.
  • Blocked at awarenessHelena Vance need information about why the change is happening.
Scope
2 change requests
  • CR-001Add the third-party case system connectoranalyzing
    64k15 daysWaiting 21 working days
  • CR-002Move training after the summer intake peaksubmitted
    020 daysWaiting 9 working days
How to read this
Submitted, analyzing, approved, rejected, deferred
Where a change request sits in the decision path.
Cost and schedule impact
What approving the request would do to the budget and to the finish date. Not analyzed is shown as itself, because an unanalyzed impact is not a zero impact.
Waiting
Working days a request has sat without a decision. Past fifteen it is flagged, because an undecided request is a governance problem rather than a scope problem.
Blocked at
The first readiness dimension scoring below three. It names what a person actually needs: information, a reason of their own, training, practice, or recognition.

The baseline is locked on this project, so a change to scope, schedule or cost needs an approved request before it lands. Approving one writes a new baseline version rather than editing the old one, and closed periods keep measuring against the baseline in force at the time.