Cadence – P4-Dev Framework

In the pragmatic-agile way of working, the working and decision-making processes are realized through purpose-bound recurring meetings, aka Events. This makes ad hoc meetings unnecessary or at least drastically reduces them. The frequency of the Events determines the maximum waiting time that a work element has to “wait” until it can be dealt with (daily, weekly, per Iteration, per Cycle/quarter).

The Cadence is a centrally defined event schedule for the Organization. It enables workflows to run as smoothly as possible by sequencing recurring Events, similar to a school or university timetable. The cadence also ensures that …

all roles within the organization can participate in the Events intended for them. (No overlapping meeting 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 Portfolio Cycle in the P4 Framework consists of four Cluster Cycles, each of which is a quarter. Various organizational and cluster events take place at the transitions between the Cluster Cycles, similar to the Iteration transfer in Scrum. It is advisable not to set the Cluster Cycle transfer to calendar quarter year boundaries, so that a change does not, for example, collide with the turn of the year and the previous Christmas season.