Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Product Development Flow - how to scale beyond 20 developers - Johannes Mainusch & Aya El Settini & Wolf Siberski - NewStore

GoDays
January 22, 2020

Product Development Flow - how to scale beyond 20 developers - Johannes Mainusch & Aya El Settini & Wolf Siberski - NewStore

Product development is pretty much jammed up in most organisations beyond 20 and adding more developers or teams to the company often results in slow down and chaos. Like a car that chokes when hitting the accelerator. But there are rare examples, where teams collaborate and produce a regular and scalable output of new features. This can only be achieved by radically reorganising, ensuring management collaboration and distributing responsibilities to experts. And by forgetting most of the old and dysfunctional management paradigms.

GoDays

January 22, 2020
Tweet

More Decks by GoDays

Other Decks in Technology

Transcript

  1. 3

  2. 5 1. Load test revealed a problem 2. tpauling discovered

    a lock protecting a shared resource in our legacy go code. 3. This happened in a shared librar 1. running 1000 parallel routines went from 8,4 minutes to 14 seconds. 1. We fixed part of out 108 microservice structure just before black friday… 1. → our go code needs fixing 2. → this is a metaphor for independence of processing units... a lock in legacy
  3. 7 highly aligned and loosely coupled apply Amdahls law to

    an organisation ⇒ highly aligned + loosely coupled teams
  4. 8

  5. 9

  6. 10

  7. 15 Own Your Future • Vision • Customers • Success

    Criteria • What you DON’T do Team Purpose
  8. 18

  9. 20

  10. 21

  11. 22

  12. 25

  13. 26

  14. 27

  15. 28

  16. 32 Things we share at NewStore Shared Values Shared Objectives

    Quarterly Goals where the whole company is incentivized to support reaching them
  17. 33 • Shared success → if we achieve our engineering

    goals, the whole company profits. ´ Q4 2019: 105% goal achievement
  18. 34 shared success helps us in becoming highly aligned. ...but

    there are still a lot of misunderstandings. People use the same words but mean different things...
  19. 35

  20. 38 Language of the Organization • Use Ubiquitous Language (DDD)

    • Use business terms • Share across all departments • Use core terms in communication and code ORDER! ORDER! ORDER!
  21. 39 Language of the Team • Extends the ubiquitous language

    • Business terms relevant for the team purpose • Use with neighbor teams and business stakeholders • Reflect team language in API API C A P T U R E AU T H O R I Z E R E F U N D R E V O K E S T A T U S
  22. 40

  23. 41

  24. 42 Takeaways for the audience 1. Independence of teams →

    apply Amdahl’s law to the organisation 2. Ownership → let teams define their purpose within the organization 1. To enable teams to take risks and take responsibility for what the own → metaphor psychological safety 2. Shared success → if we achieve our engineering goals, the whole company profits. 3. Ubiquitous language → ensure alignment by speaking the same language
  25. 45 Copyright Attributions • Thanks to all photographers! ◦ Recipe:

    By Barack Obama or an aide - posted on Whitehouse.gov, Public Domain, https://commons.wikimedia.org/w/index.php?curid=21059099 ◦ House: By Andreas Koll - Own Work, CC BY-SA 2.0 DE, https://commons.wikimedia.org/w/index.php?curid=586432 ◦ Kanban Process: By G5.cokro - Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=44916589 ◦ Kanban Board: By Andy Carmichael - Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=55448101 ◦ Team Avatars: Phil Whitehouse - Own work, CC BY 2.0, https://www.flickr.com/photos/philliecasablanca/4789125747
  26. 46 Kurt Schwitters said: ... PRIZE QUESTION: 1. Eve Blossom

    is red, 2. Eve Blossom has wheels 3. what colour are the wheels? ... Kurt Schwitters An Anna Blume 1919 A match is not a match. But is it a match?