The document discusses dealing with "process legacy" - outdated processes that slow down agile teams. It provides examples of how long integration testing times, slow environment provisioning, and funding speeds that are slower than team velocities can introduce process legacy issues. It advocates using retrospectives, value stream mappings, and impediment walls to observe these issues and identify the weakest link. It then recommends using an OODA (observe, orient, decide, act) cycle to pick a goal, plan actions, get approvals, and improve that link to help address process legacy problems in an agile context.

1. Dealing with process legacy-- @AgileHelen

2. Dealing with
process legacy
image: ryan caron king / wnpr
Helen Snitkovsky
@AgileHelen

3. … and it was grumpy
Once there was a team,
an Agile team
Why?
image: journey-to-better.com
Dealing with process legacy -- @AgileHelen

4. Retro
Sad, Mad, Glad
Sad – mostly about testing
Week 1 3 5 7 9 11 13
Agile team sprint Integration testingGAP
Root cause: integration testing
image: youtube
Process legacy example #1
Dealing with process legacy -- @AgileHelen

5. Team velocity exceeds funding speed
Process legacy
example #2

6. Process legacy example #3
Environment provisioning takes
longer than a sprint

7. Process
legacy
spotted
Bottom up transformation
Top down transformation
Pilot Agile team
EVERYWHERE
Dealing with process legacy -- @AgileHelen

8. Process
legacy
• External outdated process
• Slows Agile team down
• Just in time handling required

9. The 7 wastes
• Partially done work
• Extra features
• Relearning
• Handoffs
• Delays
• Task switching
• Defects
Wait - don't remove it just yet

10. Observe
(Value stream
mappings,
Retrospective, stand
ups, impediment walls,
A3)
Orient
(pick just one
goal)
Decide
(plan actions,
obtain
approvals)
Act
(improve the
weakest link)
Dealing with process legacy -- @AgileHelen
The OODA
cycle

11. questions?
Helen Snitkovsky
@AgileHelen
thanks.