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		LEMOS, Barbara to create a SAFe transformation vision and share with MERTENS, Simon
Assess	6 to 4 months	Connection with SAFe. Establish Portfolio Flow		Portfolio flow describes how portfolio epics move through their lifecycle, including limiting the number of significant and typically cross-cutting initiatives in progress to match the portfolio’s capacity. LPM uses the portfolio Kanban system to visualize and limit work-in-process (WIP), work in smaller batch sizes, and reduce the length of development queues. Successfully establishing flow requires knowing the total capacity for new development work versus ongoing maintenance and support activities. The enterprise can objectively evaluate and originate epics only when this balance is understood 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?		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 . Inclusion of RTEs on the portfolio meetings		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