SAFe (RTE)
Samstag, 8. Juli 2023
15:59
Preparation:
Why deliver early and
often?
Value far earlier to the customer. Delivered earlier is more valuable to
the market. Total value is greater than a waterfall approach.
#1 Principle SAFe
economic framework
Lean Budgets, Unterstand Solution Trade-offs, Suppliers, WSJF
#2 Principle Apply system
thinking
Holistic approach to system solutions,
1. Optimizing a component doesn't optimize the system
2. For the system to behave well as a system, we need a higherlevel understanding of behavior and architecture
3. The value of a system passes through ist interconnections
4. A system can't evolve faster than ist slowest integration point
#3 Principle Assume
variability, preserve
options
Set-based desing approach, multiple options, trade-offs and eliminate
none working options, better solutions
#4 Principle Build
incrementally with fast,
integrated learning cycles
Plan Do Check Adjust (PDCA)-Cycle -> integrate regularly, uncertainty
into knowledge
#5 Principle Base
milestones on objectives
evaluation of working
system
Progress: On track on the current mission
Product:
Process:
#6 Principle Make value
flow without
interruptions
8 Fundamentals:
1. Visualize and limit WP: Kanban Board
2. Addres bottlenecks
3. Minimize handoffs and dependencies
4. Get faster feedback
5. Work in small batche: Small batches go through the
system faster
6. Manage queue lenghts: Accerlates, increase quality,
quicker and better value to costumer
7. Optimize time in "the zone"
8. Remeditate legacy policies and practicies
#7 Principle Apply
Cadence: A rhythmic pattern of events that provides the steady
cadence, sychnronize with heartbeat of the development process
cross-domain planning
PI Planning
#8 Principle Unlock the
intrinsic motivation of
knowledge workers
#9 Decentralize decision
making
Moving the authority to the people closed to the work
#10 Organize around
value
From tradtional silos to value streams
PI Introduction:
Input: Business context, roadmap and vision, top 10 features of the ART Backlog
Output: PI objectvies, ART Planning board, PI risks,
Importance: Powerful way to ensure all teams on the ART are aligned and moving forward together;
to match demand to capacity by allowing teams to plan their own work; to establish face-to-face
communication and speed up decision-making; to create visibility for inter-team dependencies
necessary for feature delivery; to gain commitment from the entire ART on the upcoming PI plan
Overview:
2d long, face-to-face to plan together
Agenda:
Day 1 morning: Aligning teams to the same goals
Pro tips:
 Double and triple check that the audio and the video equipment works
 Use one slideshow deck and one computer for presentations
 Hold time for short Q&As after each presentation but manage the time box
Day 1 Team breakouts:
Training day 1:
Slides gonna be marked if important
Important Slides:
 Value Stream Management
 Coordinate & Deliver





Agile Product Delivery
Devlop on Cadence, Release on Demand
DevOps and the continous Delivery Pipeline
Enterprise Solution Delivery
Coordinate Trains and Suppliers
7 Core Competencies
 Left side executiion
 Right side strategy
 Built on Agile Leardership
 Focused on customers
Deep-Dive into core competencies
**********EXCOURSE************
Drama Triangle:
 Victim
 Saver
 Prosecutor
You as the servant leader, should never ever be in the drama triangle. How to get out:
 .. I will do my best to ..
 Share your observation
 Do not blame anyone, or point anyone out
 Clean Feedback/ Clean language
o Facts
o Inference: What you would like to happen?
o Impact