Focus Your Distributed Component Teams to Deliver Better Products Faster--Virtual Agile

Slide 1

Slide 1 text

Focus Your Distributed Component Teams to Deliver Better Products Faster Johanna Rothman [email protected] www.jrothman.com https://mastodon.sdf.org/@johannarothman

Slide 2

Slide 2 text

Slide 3

Slide 3 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Many Problems • Each team has people from across the globe • No team has fi nished anything for a month • Senior leadership is angry • The teams are unhappy 3

Slide 4

Slide 4 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Some Causes • The teams don’t have enough hours of overlap to collaborate • The teams are component teams, not cross-functional teams • Interdependencies up the wazoo • Cycle time is long, throughput is low 4

Slide 5

Slide 5 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman The Current Situation • Senior leadership thinks they can say, “Heads will roll!” and get the results they want • They need to release the product this quarter—or the Cost of Delay will get even higher 5 Cost of Delay

Slide 6

Slide 6 text

Slide 7

Slide 7 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Our Agenda 1. Visualize the teams’ hours of overlap 2. Consider how teams can work to reduce interdependencies and deliver value often 3. Consider the lifecycle(s) that make sense for which teams 4. Use the Flow Metrics to help everyone watch the work, not the people, and discuss the true costs and value 7

Slide 8

Slide 8 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman 1. Hours of Overlap • Can you call a collection of people a team? • Teams collaborate to deliver all their various work products • How much time do they have to collaborate with each other? 8 From WorldTimeBuddy

Slide 9

Slide 9 text

Slide 10

Slide 10 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Chart 2, the Middle of the “Day” • The entire team has organized themselves so they have two full hours of overlap every day • Notice that the Indian folks need to eat their dinner early to create this overlap 10

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Little’s Law and Insuf fi cient Hours of Overlap • Increased cycle time • Lower throughput • All the problems everyone sees • Little’s Law: • WIP = cycle time * throughput 13

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman 2. How Teams Can Work • Principles over practices • Collaborate wherever possible • Small stories • Work through the architecture • Integrate code review with development (pair, etc) • Requires policies • Forget iterations. Use a kanban system instead of iterations 16

Slide 17

Slide 17 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Agile Principles to Consider • Limit WIP at several levels: • Program itself: limit # feature sets in progress) • For each “team”: limit # stories • Work through the architecture, not across with daily checkins • Focus on delivering value as often as possible 17

Slide 18

Slide 18 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Possible Checkin Policies • Right-size the work so each person/ team can checkin daily (keep decisions and work small enough) • Keep code and tests clean • How often can you demo? • How often can you release internally? Then, externally? • Find agreement on an overarching goal so the program (and product) can succeed 18

Slide 19

Slide 19 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Combination Lifecycle • A combination lifecycle that does a little upfront work • Then move into increments of value • The farther away the team members, the less useful iterations are • Choose a “start” date for any milestone and explain that 19

Slide 20

Slide 20 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman 3. A Little About Lifecycles • Each approach depends on project, product, and portfolio risks • Agile approaches represent a cultural change of collaboration to an overarching goal • The big question: How long can you wait to learn something? 20

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Slide 23

Slide 23 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman 4. Flow Metrics Help Support Change • Talk about value in ways your managers understand: • Time to customer (cycle time, aging) • Customer acquisition and retention • Little’s Law explains that 23

Slide 24

Slide 24 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Change the Team’s Questions and Data • What's the one thing we should work on and fi nish? (Start with WIP.) • How old is our oldest item? Is that still valuable? (Start with aging.) • What should we change about our work so we can reduce our cycle time? (Focus on cycle time.) • How can we increase our throughput? (Focus on throughput.) 24

Slide 25

Slide 25 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Find Your Way to Ful fi ll Your Customers’ Needs • “Agile” is not the point • Satisfy the customer • Manage risks to release • To obtain revenue • Use risks to choose your “best” approach • Incorporate agility to bring joy and ease to your work 25

Slide 26

Slide 26 text

© 2024 Johanna Rothman https://mastodon.sdf.org/@johannarothman Let’s Stay in Touch • Pragmatic Manager: • www.jrothman.com/ pragmaticmanager • Please link with me on LinkedIn • The newsletter: https:// www.jrothman.com/newsletter/ 2024/02/three-tips-to-focus-to-deliver- better-products-faster/ • Project Lifecycles book: https:// www.jrothman.com/lifecyclebook 26