Tweet
Tweet

Slide 1

Slide 1 text

Lifecycles: Organize Your Program to Reduce Risk, Release Often, & Build Trust Johanna Rothman @johannarothman www.jrothman.com Lifecycle book coming soon!

Slide 2

Slide 2 text

© 2023 Johanna Rothman @johannarothman Problem • “Don’t I have a choice other than waterfall or agile?” • “We need to de fi ne our version of agile” • “Seems like agile has a lot of meetings and overhead. I just want to ship the product.” 2

Slide 3

Slide 3 text

© 2023 Johanna Rothman @johannarothman We can do better when we decide the lifecycle(s) we need for our purpose 3

Slide 4

Slide 4 text

© 2023 Johanna Rothman @johannarothman Agenda • Lifecycle de fi nition • Risks (and why there are more than three) • Serial lifecycles • Iterative lifecycles • Incremental lifecycles • Combo lifecycles • Agile approaches (not just a lifecycle, but a cultural change) 4

Slide 5

Slide 5 text

© 2023 Johanna Rothman @johannarothman A lifecycle is an idealized approach to organizing a speci fi c effort 5

Slide 6

Slide 6 text

© 2023 Johanna Rothman @johannarothman All models are wrong, but some models are useful — George Box, 1976 6

Slide 7

Slide 7 text

© 2023 Johanna Rothman @johannarothman Programs (and the projects in the programs) use lifecycles to manage risk 7

Slide 8

Slide 8 text

© 2023 Johanna Rothman @johannarothman What’s the right lifecycle for your project? It depends on your risks 8

Slide 9

Slide 9 text

© 2023 Johanna Rothman @johannarothman All Programs & Projects Have Business Risks • Cost: Can we build this for the cost we anticipate? • Technical: can we build this? • Defects: will our customers take this? • Release: Can we release when we want? 9

Slide 10

Slide 10 text

© 2023 Johanna Rothman @johannarothman Ask These Questions Before You Start the Program • Imagine this scenario • It’s three weeks before we’re supposed to release • We’re not done with all the features • We have too many defects • Ask your stakeholders/partners: What do you want to do? • How does your program balance discovery and delivery? 10

Slide 11

Slide 11 text

© 2023 Johanna Rothman @johannarothman Program/Product Risks & Challenges 11

Slide 12

Slide 12 text

© 2023 Johanna Rothman @johannarothman Use Serial Approach When You Have Zero Innovation • Waterfall, as long as the program duration is three months or less (my experience) • Phase-gate allows cancellation • Concurrent engineering gathers the cross-functional team, which can reduce risks 12

Slide 13

Slide 13 text

© 2023 Johanna Rothman @johannarothman Serial Lifecycles • Examples: • Waterfall • Phase-gate • Concurrent Engineering • All focus on one delivery at the end • This image is how my orgs used waterfall back in the 70s 13

Slide 14

Slide 14 text

© 2023 Johanna Rothman @johannarothman Money Waterfall Misconceptions • Can manage the money because we “ fi nish” the work (and capitalize the work as we go. We can’t.) • Capitalization only works when you deliver working product to a user • However, knowledge work is about learning as we proceed 14

Slide 15

Slide 15 text

© 2023 Johanna Rothman @johannarothman Waterfall Realities • We often need feedback • One-delivery approaches work for very short projects 15

Slide 16

Slide 16 text

© 2023 Johanna Rothman @johannarothman Iterative Approaches Manage Technical Risk • Iterative approaches solve one innovation problem at a time • Demos of prototypes • Sometimes offers deliveries (but that makes it an incremental approach, too) • Examples: Spiral, Evolutionary Prototyping 16

Slide 17

Slide 17 text

© 2023 Johanna Rothman @johannarothman Iterative Lifecycle: Spiral • Feedback for each prototype • One delivery at the end 17

Slide 18

Slide 18 text

© 2023 Johanna Rothman @johannarothman Iterative: Evolutionary Prototyping • Feedback for initial concept and each prototype • One delivery at the end 18

Slide 19

Slide 19 text

© 2023 Johanna Rothman @johannarothman Incremental Approaches Manage Date/Cost Risk • Customer-based deliveries • Phase 1, Phase 2… • Release 1, Release 2… • Examples: • Staged Delivery • Design to Schedule 19

Slide 20

Slide 20 text

© 2023 Johanna Rothman @johannarothman Incremental: Design to Schedule • Feedback after each completed feature • Optional releases 20

Slide 21

Slide 21 text

© 2023 Johanna Rothman @johannarothman Incremental: Staged Delivery • Feedback after each completed feature • As many releases as you need 21

Slide 22

Slide 22 text

© 2023 Johanna Rothman @johannarothman You can add iterative and incremental approaches for a combination 22

Slide 23

Slide 23 text

© 2023 Johanna Rothman @johannarothman Combo Lifecycles • Use iterative approach to create prototypes • Demo the prototypes • Timeboxes to manage other risks • Use incremental delivery to get customer feedback (in the 80s, this was alpha and beta) • We kept the code shippable every day 23

Slide 24

Slide 24 text

© 2023 Johanna Rothman @johannarothman Two Similar Combo Lifecycles 24

Slide 25

Slide 25 text

© 2023 Johanna Rothman @johannarothman Agile Approaches Focus on the Team 25 “Watch the work, not the people” (More often used in fl ow approaches, but should be used in all agile approaches)

Slide 26

Slide 26 text

© 2023 Johanna Rothman @johannarothman Agile Approaches • Iterate over requirements • Incremental delivery after each increment of work • Require cultural changes for team- based work ( fl ow-ef fi ciency thinking) 26

Slide 27

Slide 27 text

© 2023 Johanna Rothman @johannarothman Programs require syncing during their duration (The more projects, the more frequent the synching) 27

Slide 28

Slide 28 text

© 2023 Johanna Rothman @johannarothman Integrated System Program • Do you release the Platform of Common Services fi rst? • Iterate over features, deliver increments • Release everything as you build, one feature at a time? • Agile approach 28

Slide 29

Slide 29 text

© 2023 Johanna Rothman @johannarothman Inter-Related Program 29 • Do you release the Platform of Common Services fi rst? • Iterate over features, deliver increments • Release everything as you build? • Agile approach

Slide 30

Slide 30 text

© 2023 Johanna Rothman @johannarothman Program of Concurrent Projects • Relatively independent projects • Demo as desired • Any incremental or agile approach • Program requires projects sync for increments of delivery • Sync to deliver • Any incremental or agile approach 30

Slide 31

Slide 31 text

© 2023 Johanna Rothman @johannarothman Review Your Program’s Risks • What matters most to your program for business risks? • Release date? • Finishing features? • Ensuring there are no new defects? • What innovation risks do you have? • Decide and you’re likely to succeed 31

Slide 32

Slide 32 text

© 2023 Johanna Rothman @johannarothman Let’s Stay in Touch • The books: • Manage It!: https://www.jrothman.com/manageit • Create Your Successful Agile Project: https:// www.jrothman.com/cysap • Agile and Lean Program Management: https:// www.jrothman.com/alpm • Blog series: https://www.jrothman.com/lifecycle • Pragmatic Manager newsletter: www.jrothman.com/pragmaticmanager • Please link with me on LinkedIn • Look for the lifecycle book, soon… 32