Agile Pulse Model – Program pulse

Program pulse is a weekly coordination between all projects in progress.

The program pulse meeting is conducted by the program manager. Participants are project managers for the ongoing projects and the assignment manager.

Program pulse has no separate pulse board, but instead the meeting visits the projects’ pulse boards one at a time. Inboxes at the product board and the portfolio board are used when the program manager escalate problems for decisions (see the book about Agile Pulse Model for Product Pulse and Portfolio Pulse).

Decisions at program pulse are documented by the program manager in the project’s decision log.

How to perform Program pulse

At the program pulse meeting the projects are reviewed in front of each project’s pulse board. The project manager will:

  • Show progress and major breakthroughs.
  • Put forward obstacles and difficulties that the project cannot resolve themselves. The program manager will make decision whenever possible. Problems can also be handed over to the product team or the portfolio team.
  • Address resource problems, if any. (see the book about Agile Pulse Model for Resource Pulse).
  • State what sub-results and handover points are expected to be completed in the coming week.

Problems that could not be solved during the program pulse meeting are marked with a red magnet in “Inbox”. These are reported in the Agile Pulse App as Open Problems.

Agile Pulse App

After the program pulse the week-log is added into the Agile Pulse App.

Visualization

The decision log is filled in directly at the program pulse meeting. New activities are written in a activity plan during the program pulse meeting. Unsolved escalated problems are marked red.

Agile Pulse Model by Parmatur HB is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.