Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »


Main steps:

  1. Assess
  2. Prepare
  3. Launch
  4. Accelerate
  5. Sustain and improve


Out of scope of the below is the LPM and its alignment with SAFe, reason being that LPM exists to decide which work will be tackled as an input of each PI. 

SAFe Transformation - LPM integration (draft) will follow the discussions on this topic



StepsIdeal timeline before launch TopicJira epicsNotes

Assess

6 months

Need for change set 

  • Vision
  • Economic view
  • SAFe Awareness

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

See article of SAFe (something Tipping point..) which describes reasons for this change

Assess

6 monthsTrain leadership (leading safe)

Unable to locate Jira server for this macro. It may be due to Application Link configuration.


Assess6 to 4 months

Define and validate the main milestones

Define transformation team


Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Transformation team seems to be set - to discuss with Florence if the meeting Wednesdays includes the full team members
Assess6 to 4 monthsCommunicate vision/ Engage teams
Plan created by Alix, cannot find vision nor economic view, to be discussed
Prepare3 months

Identify value streams and ARTs (workshop):

  • Systems thinking
  • People needed (#s and roles)
  • Create VS ID cards (name, description, trigger, value received for X,Y,Z).

Identify and communicate ideal attributes:

  • 50/120 people?
  • Stable teams
  • Independent from external ARTs/ groups

Identify tools



Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Experience: The bigger the ART is , the most likely is a full value stream but the more complex it becomes to organise.  

 Ideally, also on experience, we should start with one ART and focus on that launch.

Train Teams/ potential epic owners to request the epics in a specific way.

Portfolio integration: either go with a simple approach where all requests from port man are considered valid (aligned with strategy) OR align the value stream with the to be SAFe.

MVP

Portfolio team is aligned with the Epic template is defined.

Epics owners with specific support for its creation

Prio done and created (not necessarily based on WSJF )


Prepare3 months

Pick the first value stream. 

Define value stream mission, who are the people

Core team for the ART launch defined

Tools (JIRA, confluence, Design epic templates)

Design the ART

Teams compositions rethough

Agree on the KPIs.


This is the right time time to define the training for the teams .



Prepare2 months

Skill training

Business owners identified

RTE, Architect, PM appointed

Create teams  

Set launch date

Set cadence


(Goo ideas From Alix assessment):Improve and harmonize backlogs good practices: DoR, DoD, acceptance criterias

Prepare2 months

Program all ceremonies

Train on the planning event (role based)

Safe awareness sessions


 Safe 

This is the right time time to define any additional  training for the teams (POs, PMs, RTE etc).



Prepare 1 month

PI objectives are agreed

Backlog is prepared

PI planning event is prepared 

 e.g. Agenda, Rooms, channels for comm, Objectives are set, etc 


Input of Portfolio here. To 

LaunchLaunch day

Launch day!

Agenda is set .



Accelarate




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.

 

  • No labels