Tweet
Tweet

Slide 1

Slide 1 text

Johanna Rothman @johannarothman www.jrothman.com Build Resilience into Any Project, Regardless of Lifecycle

Slide 2

Slide 2 text

© 2022 Johanna Rothman @johannarothman Risks: A Fact of Life for (All) Projects • Murphy’s Law: Whatever can go wrong, will (at the worst possible time) • Hofstadter’s Law: Everything takes longer, even when you take Hofstadter’s Law into account 2

Slide 3

Slide 3 text

© 2022 Johanna Rothman @johannarothman (Without telling us anything we shouldn’t hear, write in the chat): How are risks creating havoc with your project now? 3

Slide 4

Slide 4 text

© 2022 Johanna Rothman @johannarothman How do you deal with risks now? 4

Slide 5

Slide 5 text

© 2022 Johanna Rothman @johannarothman Risk “proo fi ng” costs money. We need alternatives. 5

Slide 6

Slide 6 text

© 2022 Johanna Rothman @johannarothman Three Big Ideas • Deliverable-based planning • Frequent internal releases/demos • Frequent kaizens/retrospectives 6

Slide 7

Slide 7 text

© 2022 Johanna Rothman @johannarothman 1. Deliverable-Based Plans and Planning • Many people love the comfort of a serial lifecycle • Especially accountants, because of capitalization 7

Slide 8

Slide 8 text

© 2022 Johanna Rothman @johannarothman But Serial Lifecycles Don’t Work Like That • Requirements hell • Need more feedback 8

Slide 9

Slide 9 text

© 2022 Johanna Rothman @johannarothman Most projects need to incorporate learning as they proceed 9

Slide 10

Slide 10 text

© 2022 Johanna Rothman @johannarothman If you must use phases for planning, create deliverables inside each phase and discuss those 10

Slide 11

Slide 11 text

© 2022 Johanna Rothman @johannarothman Examples of Deliverable-Based Plans • Instead of phase initiate or end, consider: • Login screens for search, designed, coded, and tested. Ready to release • Veri fi ed that admin logs fi t into our footprint • Heat output within spec for scenarios 11

Slide 12

Slide 12 text

© 2022 Johanna Rothman @johannarothman A Little Trick • Change a serial lifecycle to an incremental lifecycle 12

Slide 13

Slide 13 text

© 2022 Johanna Rothman @johannarothman You Can Use Iterative Approaches, Too 13

Slide 14

Slide 14 text

© 2022 Johanna Rothman @johannarothman My Favorite Lifecycle, a Combo 14

Slide 15

Slide 15 text

© 2022 Johanna Rothman @johannarothman Works for Hardware, Too 15

Slide 16

Slide 16 text

© 2022 Johanna Rothman @johannarothman What’s Common in All These Approaches • Deliverables, not phases • (Do whatever your leadership needs, but plan and organize with deliverables) • If you meet your deliverables, no one cares how you organize 16

Slide 17

Slide 17 text

© 2022 Johanna Rothman @johannarothman 2. Frequent Internal Releases and/or Demos • How many times does someone want to know “Where Are You????” • Internal releases and demos help answer that question • Requires frequent internal integration and willingness for everyone to use each other’s work • From “my work” to “our product” 17

Slide 18

Slide 18 text

© 2022 Johanna Rothman @johannarothman Options for Internal Releases/Demos • Demo deliverables • Build trust when you say, “We’ll demo what we delivered this past month.” • Use feature fl ags to hide what’s not done yet. • Prevents more risks 18

Slide 19

Slide 19 text

© 2022 Johanna Rothman @johannarothman 3. Frequent Kaizens or Retros • Since we incorporate learning into the project, why not formalize that learning? • Formal retros every 1-3 weeks • Kaizen on demand for 20-30 minutes 19

Slide 20

Slide 20 text

© 2022 Johanna Rothman @johannarothman Kaizen: Continuous Improvement • On demand • On a cadence • Question: • What issue(s) do we have since the previous kaizen? • What’s our action plan to deal with it (them)? 20

Slide 21

Slide 21 text

© 2022 Johanna Rothman @johannarothman Retrospective • Speci fi cally for double-loop learning: • What do we need to learn about what we did? (product) • What do we need to learn about how we did that? (process) • The more we learn, the more we challenge our mental models about the work 21

Slide 22

Slide 22 text

© 2022 Johanna Rothman @johannarothman Deliverables and Learning Encourage Rolling Wave Planning • Choose a wave duration (1, 2, 3, 4 weeks) • Plan for that duration • As you fi nish one week, add another to the end • Always have a wave- duration plan 22

Slide 23

Slide 23 text

© 2022 Johanna Rothman @johannarothman More Ideas if We Have Time • Cycle time for estimation (which allows Monte Carlo simulation) • Make the work visible (not a write- only Gantt chart, but a board of just the next few days-weeks of work) • Ask me anything because I have more ideas than can fi t into this presentation 23

Slide 24

Slide 24 text

© 2022 Johanna Rothman @johannarothman Links I Discussed • The “iron triangle” is missing several sides. Here’s the drivers, constraints, fl oats series: https:// www.jrothman.com/mpd/2020/02/summary-for-a-projects-boundaries-drivers-constraints- fl oats/ • There’s more about that in Manage It! Your Guide to Modern Pragmatic Project Management • I use cycle time instead of story points or velocity. See https://www.jrothman.com/mpd/2019/09/measure- cycle-time-not-velocity/ • There’s more about that in Create Your Successful Agile Project. • The best prices for the ebooks are here: • https://pragprog.com/titles/jrpm/manage-it/ • https://pragprog.com/titles/jragm/create-your-successful-agile-project/ • Amazon is probably best for the print books 24

Slide 25

Slide 25 text

© 2022 Johanna Rothman @johannarothman Let’s Stay in Touch • Pragmatic Manager: • www.jrothman.com/ pragmaticmanager • Please link with me on LinkedIn • An article you might like: https:// www.projectmanagement.com/ articles/682691/build-resilience-in-any- kind-of-project 25