program increment – Lean Agile Guru

Jun

11

2020

PO Synch

Day 77. Product Owner (PO) Synch is a SAFe program-level event. POs and Product Management (PM) meet on a weekly basis (could be more often as needed) to discuss any problems or opportunities with the current Program Increment (PI) and the features of the upcoming PI. Usually facilitated by the Release Train Engineer (RTE)... but could also be facilitated by the PM. In addition to POs, PM and RTE, SMEs and other key stakeholders may be invited. Continue reading

PI Objective — Demystified

business objective, pi objective, program increment, Program PI Objective, Team PI Objective

Program Increment (PI) Objective is mysterious and troublesome to some folks. What is it? How is it written?Where is it from? What is it for? When is it created? Who uses it? Why is it important? No worries! Read on as PI Objective is Demystified here! To be continued...

Idea approved, now what’s next? Part IV

PI, program increment, roadmap, Success

Roadmap -- yes, you need a roadmap of the features. Do all the features fit in a program increment (PI)? Sometimes, features for a product span across two or more PIs ... depending on the prioritization, sequencing of the features (sequenced to hit a hard date/milestone, for example) and how large the Epic or Capability or Product that is going to be built. Usually, a PI is a quarter of a year long... 3 months long... 6 to 7 iterations (sprints)... 12 to 14 weeks long. Lay out the features over the roadmap (over a PI or series of PIs).…