Agile Pulse Model – Product pulse

Product pulse will enable the product teams to coordinate their work so that results can be delivered. Product pulse will also enable the product teams to react quickly to new conditions and ideas, and to handle problems that the ongoing projects need help with and that require swift decisions.

The product team uses backlog planning to focus their efforts. A period is generally one month long.

How to perform product pulse

Product pulse meetings are held daily.

General: Activities and ideas identified during product pulse can be added to the activity window for immediate actions, or added to the period log and handled as soon as possible, or added to the backlog for later prioritization together with other long term tasks. Problems and decisions are documented in the decision log.

  1. Finished activities. Activities in the activity window that are complete are moved from “In progress” to “Done”.
  2. New input. Are there any new ideas, problems or actions in the “Inbox” or from the participants? Identify actions and make decisions.
  3. Activities to do. What workshops are needed and who should participate? What handover points in the projects are coming up soon and who should participate? Are there tasks in the period log or activity plans that should be moved to the activity window? What activities should be moved from “To do” to “In Progress”? Who will do what?

Visualization

Put up business goals, program plans, backlog, period log and other important documents on the product pulse board. Draw an area for activity window and inbox. Use post-it notes to write activities in the activity window and to put new issues in the “Inbox”.

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