Extreme SAFe: Turning Up the Flow in PI Execution

1
Extreme SAFe: Turning Up the
Flow in PI Execution
Patterns to turn up the good & improve flow on your ART

2
Adrienne Wilson
SAFe Fellow + SPCT
COO, Pretty Agile
Em Campbell-Pretty
SAFe Fellow + SPCT
CEO, Pretty Agile

@AgileCanuck
@PrettyAgile #notrainwrecks
You’ve Finished
Planning ….
• Dependencies visualized
• Risks are ROAMed
• PI Objectives committed
• The Business Owner have
accepted the plan
• PI Execution is…..
kr/p/bBTHi7

@PrettyAgile @AgileCanuck
#notrainwrecks
A little bit bumpy…
https://flic.kr/p/DqaXhE

@AgileCanuck
Introducing….

@AgileCanuck
“My goal in laying out the project style was to take
everything I knew to be valuable about software
engineering and turn the dials [up] to 10. We would do
everything that was absolutely necessary as intensely
as we could imagine.”
-Kent Beck, Extreme Programming Explained

@AgileCanuck
“It’s deceptively simple:
Notice what is working
well, and find a way to
turn it up.”
—Woody Zuill

@AgileCanuck
What if we took what is valuable in PI Execution and turn up the flow up to 10?
“If a practice needs to change, understanding the principles will assure the change
moves the Enterprise in the right direction” – Implementing SAFe 5.1.1

© Scaled Agile. Inc.
ART events create a closed-loop system to keep the train on the tracks.
ART events drive the train
4-9
ART events
Team events
Scrum of Scrums PO Sync
System
Demo
Inspect & Adapt
PI
Planning Iteration
Planning
Daily
Stand-up
Backlog
Refinement
Iteration
Review
Iteration
Retro
Prepare for PI Planning
ART Sync
PI
Planning
You are
here

@AgileCanuck
What is valuable in PI Planning?
► Establishing personal communication across all team
members and stakeholders
► Aligning development to business goals with the business
context, Vision, and Team/Program PI Objectives
► Identifying dependencies and fostering cross-team and
cross-ART collaboration
► Providing the opportunity for just the right amount of
architecture and Lean User Experience (UX) guidance
► Matching demand to capacity, eliminating excess work in
process (WIP)
► Fast decision making
Cross-team collaboration
4-36
The benefits of PI Planning

@AgileCanuck
What does
this look like
when we
turn the dial
up to 10?

@AgileCanuck
Unity Hour Reunification
PI Planning Lite (aka Unity Day) EVERY Iteration
Team Iteration goals
- Goal 1
- Goal 2
- Goal 3
- Innovation
- Discovery
Want to know more:
https://prettyagile.co/UnityHour

4-13
System
Demo
Inspect & Adapt
PI
Planning Iteration
Planning
Daily
Stand-up
Backlog
Refinement
Iteration
Review
Iteration
Retro
ART Sync
PI
Planning
ART events
Team events
You are
here

@AgileCanuck
What is valuable about ART Sync?
▸ Visibility into progress and impediments
▸ Facilitated by RTE
▸ Participants: Scrum Masters, other select
team members, SMEs if necessary
▸ Weekly or more frequently, 30–60 minutes
▸ Timeboxed and followed by a meet-after
▸ Visibility into progress, scope, and priority
adjustments
▸ Facilitated by RTE or PM
▸ Participants: PM, POs, other stakeholders,
and SMEs as necessary
▸ Weekly or more frequently, 30–60 minutes
▸ Timeboxed and followed by a meet-after
Scrum of scrums PO Sync
ART Sync
4-71
ART sync is used to coordinate progress

@AgileCanuck
Want to know more:
http://bit.ly/DailyCocktailHour
ART Sync for 15 minutes EVERY Day

@AgileCanuck
Community of Practice Syncs EVERY week

System
Demo
Inspect & Adapt
PI
Planning Iteration
Planning
Daily
Stand-up
Backlog
Refinement
Iteration
Review
Iteration
Retro
ART Sync
PI
Planning
4-18
You are
here
ART events
Team events

@AgileCanuck
What is valuable about the System Demo?
► Features are functionally complete
or toggled so as not to disrupt
demonstrable functionality
► New Features work together and
with existing functionality
► Happens after the Iteration review
(may lag by as much as one
Iteration maximum)
► Demo from a staging environment
which resembles production as
much as possible
SUPPORT
System
team
Full system
4-72
Demo the full system increment every two weeks

@AgileCanuck

@AgileCanuck
System Demo Done Well Is Key for Flow
Software
Hardware
+
Firmware
Environments
Pipeline +
Configuration
Data
What components are a
part of your solution?
Integrate all of them
all the time

ART events
Team events
System
Demo
Inspect & Adapt
PI
Planning Iteration
Planning
Daily
Stand-up
Backlog
Refinement
Iteration
Review
Iteration
Retro
ART Sync
PI
Planning
4-23
You are
here

@AgileCanuck
What is valuable about Preparing for PI Planning?
Monday Tuesday Wednesday Thursday Friday
Buffer for leftover work
Final verification and validation, and documentation (if releasing)
Innovation
PI planning readiness
Innovation
continues
PI planning
readiness
Continuing
education
Inspect
& Adapt
Event
PI planning
Business context
Product / solution
vision
Architecture vision
and development
practices
Planning
requirements
and lunch
Team breakouts
Draft plan review
Management
review and
problem-solving
Planning
adjustments
Team breakouts
Final plan review
and lunch
Program risks
PI confidence vote
Plan rework if
necessary
Planning
retrospective and
moving forward
Optional time
for distributed
planning
4-74
Example IP Iteration calendar

@AgileCanuck
Start Planning for Next PI DAY1 of This PI
Want to know more:
https://vimeo.com/497667872

@AgileCanuck
WSJF on Cadence EVERY Iteration
Ready for
Disco
Review
Feature
Definition
Discovery
Complete
Ready
WSJF
WSJF
Complete
÷

4-28
System
Demo
Inspect & Adapt
PI
Planning Iteration
Planning
Daily
Stand-up
Backlog
Refinement
Iteration
Review
Iteration
Retro
ART Sync
PI
Planning
You are
here
ART events
Team events

@AgileCanuck
What is valuable about I&A?
Three parts of Inspect and Adapt:
1. The PI System Demo
2. Quantitative and Qualitative Measurement
3. Problem-Solving Workshop
► Timebox: 3 – 4 hours per PI
► Attendees: Teams and stakeholders
4-76
Improving results with the Inspect and Adapt event

@AgileCanuck
Rate Actual Value For Completed PI Objectives EVERY Iteration
PI Objectives BV AV
Ob 1 9
Ob 2 8
Ob 3 10
Ob 4 6
Ob 5 4
__________
Uncommitted Ob 7
PI Objectives BV AV
Ob 1 9
Ob 2 8 8
Ob 3 10
Ob 4 6
Ob 5 4
__________
Uncommitted Ob 7
PI Objectives BV AV
Ob 1 9
Ob 2 8 8
Ob 3 10
Ob 4 6
Ob 5 4. 4
__________
Uncommitted Ob 7 7
PI Objectives BV AV
Ob 1 9
Ob 2 8 8
Ob 3 10 10
Ob 4 6
Ob 5 4. 4
__________
Uncommitted Ob 7 7
PI Objectives BV AV
Ob 1 9 9
Ob 2 8 8
Ob 3 10 10
Ob 4 6
Ob 5 4. 4
__________
Uncommitted Ob 7 7

@AgileCanuck
”Bubble Up” Systemic Issues EVERY Iteration
In iteration x, this event occurred
at this place resulting in this
impact on the ART or Program
Increment.
Added Allocated Burst

@AgileCanuck
What if we took what is valuable in PI Execution and turn up
flow up to 10?
Day 6 Day 7
Day 3 Day 4 Day 5
Day 2
Day 8 Day 9 Day 10
Day 1
System
Demo*
Iteration
Review
Retro
Iteration
Planning
SoS
PO Sync
Backlog
Refinement
Team Events ART Events

@AgileCanuck
SAFe PI Execution Events - Turning up the Flow
Team Events ART Events Turn Up the Flow Events
Day 6 Day 7
Day 3 Day 4 Day 5
Day 2
Day 8 Day 9 Day 10
Day 1
Unity Hour
Iteration
Planning
Reunification
Cocktail Hour
Feature Disco
Cocktail Hour
CoP Syncs
Disco Review
WSJF
System Demo
Cocktail Hour
Cocktail Hour
CoP Syncs
Cocktail Hour
Iteration
Reviews
Bubble Up
Cocktail Hour
Cocktail Hour
Backlog
Refinement
Feature
Auction
Cocktail Hour
Feature Disco

@AgileCanuck
No matter the circumstance you can always improve.
You can always start improving with yourself.
You can always start improving today.
–Kent Beck, Extreme Programming Explained

Em Campbell-Pretty
CEO, SAFe Fellow & SPCT
@PrettyAgile
linkedin.com/in/ejcampbellpretty/
ecp@prettyagile.com
Adrienne Wilson
COO, SAFe Fellow & SPCT
@AgileCanuck
linkedin.com/in/adriennelwilson
awilson@prettyagile.com

Extreme SAFe: Turning Up the Flow in PI Execution

Recomendados

Recomendados

Más contenido relacionado

Similar a Extreme SAFe: Turning Up the Flow in PI Execution

Similar a Extreme SAFe: Turning Up the Flow in PI Execution (20)

Más de Em Campbell-Pretty

Más de Em Campbell-Pretty (20)

Último

Último (20)

Extreme SAFe: Turning Up the Flow in PI Execution