Cadence of a year

The Cadence is a centrally defined event planning for the Organization. Similar to a schedule at a school or university, it enables …

  • all roles within the organization can participate in the events intended for them. (No overlapping invitations)
  • all private events of the Teams and Groups take place at the same time in order to allow as much free working time as possible within the Teams and Groups

The Cadence of a year in the P4 Framework consists of four Cycles, each of which is a quarter. Various organizational and cluster events take place at the transitions between the Cycles, similar to the Iteration transfer in Scrum. It is advisable not to set the Cycle transfer to calendar four-year boundaries, so that a change does not, for example, collide with the turn of the year and the previous Christmas season.

.

\r\n


Further suitable links:

Events Roles Groups Artifacts
Team Planning

Team Sync

Team Backlog Refinement

Team Review

Team Retrospective

.

Cluster Planning

Cluster Sync

Cluster Backlog Refinement

Cluster Review

Cluster Retrospective

.

Portfolio Planning

Organisation Sync

Portfolio Refinement

Portfolio Review

Organisation Retrospective

Team Product Owner

Team System Engineer

Team Scrum Master

.

Cluster Product Owner

Cluster System Engineer

Cluster Scrum Master

.

Portfolio Owner

Portfolio Architect

Organisation Scrum Master

Working Team

Community of Practice

.

Team Product Owner Group

Team System Engineer Group

Team Scrum Master Group

Cluster Management Circle

.

Cluster Product Owner Group

Cluster System Engineer Group

Cluster Scrum Master Group

Organisation Management Circle

Team Backlog

Inspectable Results

Team DoD

Team Improvement Backlog

.

Cluster Backlog

Usable Knowledge & System Increment

Cluster DoD

Cluster Improvement Backlog

.

Portfolio Backlog

Systems & Applications

System Platforms & Variants

Organisation DoD

Organisation Improvement Backlog