11
Dealing with process legacy-- @AgileHelen

Dealing with process legacy final

Embed Size (px)

Citation preview

Page 1: Dealing with process legacy final

Dealing with process legacy-- @AgileHelen

Page 2: Dealing with process legacy final

Dealing with process legacy

image: ryan caron king / wnpr

Helen Snitkovsky@AgileHelen

Page 3: Dealing with process legacy final

… and it was grumpy

Once there was a team, an Agile team

Why?image: journey-to-better.comDealing with process legacy -- @AgileHelen

Page 4: Dealing with process legacy final

Retro

Sad, Mad, GladSad – 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

Page 5: Dealing with process legacy final

Team velocity exceeds funding speed

Process legacy example #2

Page 6: Dealing with process legacy final

Process legacy example #3

Environment provisioning takes longer than a sprint

Page 7: Dealing with process legacy final

Process legacy spotted

Bottom up transformationTop down transformation

Pilot Agile teamEVERYWHERE

Dealing with process legacy -- @AgileHelen

Page 8: Dealing with process legacy final

Process legacy

• External outdated process• Slows Agile team down• Just in time handling required

Page 9: Dealing with process legacy final

The 7 wastes• Partially done work• Extra features• Relearning• Handoffs• Delays• Task switching• Defects

Wait - don't remove it just yet

Page 10: Dealing with process legacy final

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

Page 11: Dealing with process legacy final

questions?

Helen Snitkovsky@AgileHelen

thanks.