Let Metronome Simplify your PI Planning

Metronome PI Planning

This post is part of a series highlighting Metronome’s support for SAFe ceremonies including Program Increment (PI) Planning. Jump to the series…

Getting ready for PI Planning?  Here is a good sequence of events and if my past decade of work is any indication you and your team are constantly jumping in and out of your Agile ALM tool because …

Well, you know why!

With Metronome we have solved the issues that come with the use of less capable tools. This is how we have done it. Read on to learn more, but do not forget to check out our short video on PI Planning in Metronome.

PI Planning – First Breakout Session

The Program Board in Metronome displays the initial set of Features identified for the PI. During the first breakout session of PI Planning, teams accessing the Program Board can view the Features, using filters, that they plan to work on in the upcoming Program Increment. Teams can add Features directly to the Program Board with Metronome and can also break each Feature down into Stories and assign them to Iterations without having to navigate away from the Program Board. With Metronome, Teams can quickly set/create and establish the Capacity for each iteration in the Program Board. Metronome has visual indicators that helps team plan and commit to stories.

Metronome SAFe Program Board
Metronome Program Board

Teams can also easily enter the Team PI Objectives and as they do so, include any Stretch objectives that the groups decide are relevant.

Metronome SAFe PI Objectives
Metronome PI Objectives

Second Breakout Session

During the 2nd session of PI Planning, teams can more efficiently finalize their plans and ROAM the risks using Metronome.  Speaking of risks, Dependency identification is one of Metronome’s KEY and UNIQUE differentiators!  Teams can very quickly and easily track dependencies between Stories and Features, between the Stories themselves, or between two Features.  Dependencies are indicated by a red line.Teams can easily identify Risks and Impediments and ROAM the risks using Metronome.

Risks and Dependencies
Risks and Dependencies, ROAM

In summary, Metronome enables:

  • Real-time synchronization across program boards
  • Dynamic collaboration between teams
  • Portability of information creation
  • Progress and dependencies tracking across teams
  • Story board update creation; these can be carried over to the program board
  • Enhanced ability to conduct SAFe ceremonies with confidence: Program Iteration (PI) Planning, Daily Scrum, Retro, Scrum of Scrum and Inspect & Adapt
  • Increased ability to visualize progress using graphs and charts

This post is part of a series highlighting Metronome’s support for SAFe ceremonies. Jump to the series…

Also, check out our short video on PI Planning in Metronome.

Metronome 4
Minute Video Tour