Program Agile Prioritization Principles Prioritization Process Product Roadmap

Program Agile Prioritization Principles

Prioritization Process Product Roadmap Enters single “front door” Prioritization Decision Input to PI planning Tracked on Program Kanban Committed Program Board

Product Roadmap Committed Proposed Q 3 Jul Aug Q 4 Sept Oct Q 1 Nov Dec Jan Feb Mar Epic Enabler Epic Enabler 3

Platform Enhancements Break/Fix New Products Customer Driven Strategic Implementations One Backlog Teams Execute Prioritized Backlog Tactical 4

Product Mgmt facilitates prioritization with delivery organization Analytics Operations IT Development Product Management Legal Compliance Product Marketing BU Sales • IFS • USIS • Workforce • Cross BU / COE involvement • Increases communication and improves alignment • Quarterly review of proposed priorities • Gain agreement from key stakeholders

Example Epic Description For (customers) Who (do something) The (solution) is a (how) that (provides some value) Unlike (competition or current solution) Our solution (does something better, why? )

Connected Kanban's New Prioritized In Process New Stories at Team Level Prioritized Epics at Portfolio Level Done In Process New Features at Program Level Done Prioritized In Process Done

Backlog Prioritization New Feature Description Feature Acceptance Criteria Feature In Sized WSJF Prioritized Next Process Feature Feature Meets definition of ready Done

What is (and isn’t) prioritized? Feature 4 Feature 13 Feature 12 Feature 8 Feature 1 Feature 7 Feature 5 Feature 10 Feature 3 Feature 9 Feature 6 Feature 11 Size 10 20 10 30 30 20 20 40 80 50 50 50 130 WSJF 21. 0 6. 5 6. 0 5. 0 4. 5 2. 8 2. 6 2. 0 1. 2 0. 8 Based on this example the program has capacity for 100 points forcing the line to be drawn after Feature 8 for the quarter This will become a basis for tradeoff discussions regarding priority, to put something else “in” something has to come “out”

PI Planning Event

Post PI Planning Program Board