Cadence and synchronization limit the accumulation of variance.

—Don Reinertsen, Principles of Product Development Flow

 

Principle #7 – Apply Cadence, Synchronize with Cross-Domain Planning

Solution development is an inherently uncertain process. If it weren’t, the solutions would already exist, and there would be no room for the next generation of innovations. This risk conflicts with the need for businesses to manage investments, track progress, and have sufficient confidence in future outcomes to plan and commit to a reasonable course of action.

Lean-Agile teams function in the ‘safety zone,’ where sufficient uncertainty actually provides the freedom for innovation, while sufficient confidence allows the business to operate. The primary means to achieve this balance is to maintain true knowledge of the current state. Cadence, synchronization, and cross-domain planning delivers this information.

Cadence

Cadence provides a rhythmic pattern, the dependable heartbeat of the process. It makes routine that which can be routine, so the intellectual capacity of knowledge workers can be devoted to managing the variables. By transforming unpredictable events into expected events, Cadence offers many additional benefits:

  • Wait times become predictable. If the work you’re waiting for isn’t in this Program Increment (PI) timebox, it likely can be in the next one.
  • Facilitating planning, it enables more efficient use of people and resources.
  • The resulting forcing function lowers the transaction costs of key events, including planning, integration, demonstrations, feedback, and retrospectives

Synchronization

Synchronization allows multiple perspectives to be understood, resolved, and integrated at the same time. As a result, it:

  • Pulls the different assets of a system together to assess solution viability
  • Aligns the development teams and business to a common mission
  • Integrates the customers into the development process
SAFe cadence and synchronization harmonics

Taken together, cadence and synchronization—and most importantly, the associated activities—help teams proceed confidently despite the risks described above.

Synchronize with cross-domain planning

Of all the events that occur, one is the most critical: Periodically, all stakeholders gather for cross-domain planning and synchronization. This event, known as Program Increment (PI) Planning, is the fulcrum upon which all other events rest. It also serves as the team’s opportunity to present and review its true knowledge of the current state.

The event serves three primary purposes:

  1. Assesses the current state of the solution. An integrated, solution-level demonstration and assessment determines the objective knowledge of the current state. This typically occurs just before the planning event.
  2. Realigns all stakeholders to a common technical and business vision. Based on the current state, business and technology leaders reset the mission, with the minimum number of constraints (Principles 8 & 9). This aligns all stakeholders to a common vision, both near- and long-term.
  3. Plans and commits teams to the next Program Increment. Based on the new knowledge, the teams plan what they can accomplish in the upcoming timebox. Sharing the planning and control empowers teams to create the best possible plans to achieve the best possible solution within the given constraints.

Developing large-scale systems is fundamentally a social activity, and this planning event provides a continuous opportunity to build and improve the social network.

There’s no cure for the inherent uncertainty of solution development. If there were, it would surely be worse than the disease. However, applying cadence and synchronization, and periodic cross-domain planning, provides the tools needed to operate in the ‘safety zone.’

 


Learn More

[1] Reinertsen, Donald. The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing, 2009.

[2] Kennedy, Michael. Product Development for the Lean Enterprise. Oaklea Press, 2003.

Last update: 10 October, 2017