View Source

Main steps:

Assess
Prepare
Launch
Accelerate
Sustain and improve

Assumptions to agree on:

LPM is a full eco-system: forums, roles, best practices, guardrails, constant connection with value streams, RTEs, Business Owners, Epic Owner
Sponsorship of top management is essential: cascading decisions, agree set-up, ensure roles and responsibilities at LPM level
Decentralization of decision making based on guardrails, otherwise it's killing the LPM empowerment

Steps	Ideal timeline before launch	Topic	Jira epics	Notes
Assess	6 months	Need for change set Vision Economic view	N/A	MERTENS, Simon see: : 0. Why Moving Ahead with SAFe, is the Right Choice?
Assess	6 to 4 months	Connection with SAFe. (tools and goal: lean/agility) Establish and Agree on the Portfolio Flow Initiatives vs epics	N/A	Agreed on the flow with : LEMOS, Barbara to see the complexity of adding a delivery state into the tool - no impact on Agility cycle. FYI MERTENS, Simon
Prepare/	3 months	Agree on format for request. Align on the selected value stream. (SAFe journey) Value stream = full stream Agree and schedule ceremonies Agree on the KPIs. (SAFe journey) Have the tools set Trainings on LPM and how it connects to SAFe?	Epic cycle set (phase 1): Agree on format for request. Agree on strategic themes Have the tools chosen and set Define champions Communicate and train Enforce the epic cycle and requests Align on the selected value stream. (SAFe journey). Value stream = full stream Agree and schedule ceremonies Agree on the KPIs. (SAFe journey) Trainings on LPM and how it connects to SAFe?	This is the right time time to define the training for the teams . MERTENS, Simon to confirm the epic template.
Prepare	2 months	Agree and schedule ceremonies Agree on the KPIs. (SAFe journey)	Agree and schedule ceremonies Agree on the KPIs. (SAFe journey)	Ceremonies will feed into the PI planning and should be schedule around 1 month before the PI to discuss feedback and final prio. LEMOS, Barbara Discussed with MERTENS, Simon on the cadence to be aligned with PI planning and it seems feasible. To agree on the PI planning cadence : at least 4 sprints of 2 weeks + 1 retribution week .
Launch	Launch day	Launch day!
Accelerate		Better prioritization		Train Teams on WSJF Ensure all teams understand the WSJF concepts and calculations. Provide training, examples, and make sure there is consistency in how job estimates and other inputs are derived.
		Better KPIs

Establish Portfolio Flow

Funnel: Contains all the EPICs proposed that could be candidate one day to enter in a PI
Reviewing: This column contains all the EPICs to give focus on. Epic owner is assigned. Hypothesis statement & Acceptance criteria are defined.
Analyzing: This column contains all the EPICs being refined. A potential feature can be created at this stage that will be completed in next PI to assess the context and create a mutual agreement stage.
Ready: This column will contain EPICs that are ready to be prioritized for next PIs.
Implementing: This column contains the EPICs that are already started (One of its child Features is In progress). This step should be automatized
Done: This column contains the EPICs that are completed (All child Features are in Done - Accepted or Archived status).

IT Knowledge Center > 90.LPM integration (draft) > image-2024-6-21_13-39-27.png