How SAFe Can Be Applied to Technology Migration & Greenfield Initiatives

Slide 1

Slide 1 text

Em Campbell-Pretty CEO, SAFe Fellow & SPCT [email protected] w w w.prettyagi l e .com Adrienne Wilson COO, SAFe Fellow & SPCT [email protected] How SAFe Can Be Applied to Technology Migration & Greenfield Initiatives

Slide 2

Slide 2 text

©Pretty Agile Pty Ltd Two Use Cases

Slide 3

Slide 3 text

©Pretty Agile Pty Ltd Image: https://flic.kr/p/rupU15 @AgileCanuck @PrettyAgile #notrainwrecks

Slide 4

Slide 4 text

©Pretty Agile Pty Ltd What Should We Do About It? The Debate Begins… The “Business” Technology We have to get off this platform because …. Nothing The platform is out of support This is just an excuse for the Technology people to get the ’new shiny thing’ Why do I care? It’s getting more and more unstable We can’t find anyone who knows how to code in assembly (or COBOL or…)

Slide 5

Slide 5 text

©Pretty Agile Pty Ltd

Slide 6

Slide 6 text

©Pretty Agile Pty Ltd Show Me the Destination Destination postcards do double duty: They show the Rider where you’re headed, and they show the Elephant why the journey is worthwhile. - Switch, Chip Heath & Dan Heath

Slide 7

Slide 7 text

©Pretty Agile Pty Ltd Image: https://flic.kr/p/MKsVwK

Slide 8

Slide 8 text

©Pretty Agile Pty Ltd

Slide 9

Slide 9 text

©Pretty Agile Pty Ltd

Slide 10

Slide 10 text

©Pretty Agile Pty Ltd How Do We Do This? Copy and Paste Waterfall Carve out a special team(s) of our best and brightest

Slide 11

Slide 11 text

©Pretty Agile Pty Ltd Really? Why not? You wont need everything SAFe will give you a better result If you branch, you will have to merge – people and systems Copy and Paste Waterfall Carve out a special team(s) of our best and brightest

Slide 12

Slide 12 text

©Pretty Agile Pty Ltd

Slide 13

Slide 13 text

©Pretty Agile Pty Ltd Start By Defining the Epic(s) “Yes, you do need to do this!” “Yes, you do need to include “the business”!” • Creates shared understanding • Provides transparency into the solutions complexity Why Hold an Epic Defintion Workshop? • Foster alignment on the outcomes • Enables more informed prioritisation

Slide 14

Slide 14 text

©Pretty Agile Pty Ltd Be Clear on the Business Outcome & Don’t Forget the Leading Indicators Pirate Metrics Acquisition Activation Retention Referral Revenue One measurable business outcome per epic that will drive the right outcomes Be Clear on the Business Outcome

Slide 15

Slide 15 text

©Pretty Agile Pty Ltd Identify One or More Minimal Viable Product(s) Image: https://flic.kr/p/7NKi2S The goal of the MVP is to begin the process of learning, not end it. Unlike a prototype or concept test, an MVP is designed not just to answer product design or technical questions. Its goal is to test fundamental business hypotheses. — Eric Ries, The Lean Start Up

Slide 16

Slide 16 text

©Pretty Agile Pty Ltd But How Does an MVP Apply to an Enabler Epic? Image: https://flic.kr/p/iLhSaS We don’t need to do this! We know it works! Mitigate business and solution risk through targeted experiments The assets created in the MVP(s) might be throw away but the learning will not.

Slide 17

Slide 17 text

©Pretty Agile Pty Ltd Solution On A Page (Or Whiteboard) CRUD Assumptions Questions Simple boxes 1 2 3 4

Slide 18

Slide 18 text

©Pretty Agile Pty Ltd CHARGE!

Slide 19

Slide 19 text

©Pretty Agile Pty Ltd Break It Down….

Slide 20

Slide 20 text

©Pretty Agile Pty Ltd Goal Actors Impact Deliverables Use Impact Mapping to Break Epics into Features Why are we doing this? Who can produce the desired effect? How should our actors' behaviour change? What can we do, as a delivery team, to support the required impacts?

Slide 21

Slide 21 text

©Pretty Agile Pty Ltd Applying Impact Mapping to Technology Migration Initiatives

Slide 22

Slide 22 text

©Pretty Agile Pty Ltd Deliver Business Value While Migrating; A Win: Win Approach “...the only technical debt work that should be prioritized is work that increases future flows through the value stream. Tech debt should never be done for the sake of software architecture alone…” — Mik Kersten Project to Product

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

©Pretty Agile Pty Ltd Step 1 Write tests for the behavior of the system You Think You Know How Your Current System Works… Step 2 Run them on the legacy system and see how many pass! Step 3 Determine which is correct – the test or the system Step 4 Run and add tests for the New System as you build

Slide 27

Slide 27 text

Slide 28

Slide 28 text

©Pretty Agile Pty Ltd Automate Now!!!! Step 1 Write tests for the behavior of the system Step 2 Run them and they will fail Step 3 Write code until tests pass Step 4 Refactor to meet standards, AUTOMATE!

Slide 29

Slide 29 text

Slide 30

Slide 30 text

©Pretty Agile Pty Ltd Guiding Investments by Horizon Apply Capacity Allocation Continuous Business Owner Engagement Approving Significant Initiatives Leverage the Guardrails to Achieve Balance Source: https://www.scaledagileframework.com/guardrails/

Slide 31

Slide 31 text

Slide 32

Slide 32 text

©Pretty Agile Pty Ltd Continuously Evolve Live Systems After All It Is Just Good Hygiene According to Randy Shoup: “…both eBay and Google are each on their 5th entire rewrite of their architecture from top to bottom” —Gene Kim et al. DevOps Handbook Image: https://flic.kr/p/x1z7v

Slide 33

Slide 33 text

Em Campbell-Pretty CEO, SAFe Fellow & SPCT linkedin.com/in/ejcampbellpretty/ [email protected] Adrienne Wilson COO, SAFe Fellow & SPCT linkedin.com/in/adriennelwilson [email protected]