Slide 1

Slide 1 text

HOW TO SCALE IF NOTHING IS FOR FREE

Slide 2

Slide 2 text

ANDRÉ NEUBAUER - CTO 2 „Technology enthusiast, org development fanatic and strong advocate on modern leadership. Motivated by 'Y'! Love to work as CTO for @Misterspex“ @devpg

Slide 3

Slide 3 text

EVOLUTIONARY THEORY FOR COMPANIES How to scale if nothing is for free

Slide 4

Slide 4 text

EVOLUTIONARY THEORY FOR COMPANIES How to scale if nothing is for free „Pioneers, Settlers, Town Planner“ by Simon Wardley Link: http://blog.gardeviance.org/2015/03/on-pioneers-settlers-town-planners-and.html

Slide 5

Slide 5 text

SCALABILITY IS THE FOUNDATION OF GROWING A BUSINESS How to scale if nothing is for free Economies of scale „Scalability is the capability of a system, network, or process to handle a growing amount of work, or its potential to be enlarged in order to accommodate that growth.“ https://en.wikipedia.org/wiki/Scalability

Slide 6

Slide 6 text

SCALING IN THE „INDUSTRIAL AGE“

Slide 7

Slide 7 text

ASSEMBLY-LINE WORK

Slide 8

Slide 8 text

„The Principles of Scientific Managment“ Mister Spex Company Profile, Status Mai 2016 FREDERICK WINSLOW TAYLOR

Slide 9

Slide 9 text

•  Repetitive work •  Separation of thought from action •  Standardisation of tasks •  Scaling by repeating without thinking Mister Spex Company Profile, Status Mai 2016 ASSEMBLY-LINE WORK

Slide 10

Slide 10 text

STEAM ENGINE

Slide 11

Slide 11 text

STEAM ENGINE •  One of the most important technologies of the Industrial Revolution •  Enabled faster production •  Replaced staff from heavy physical work

Slide 12

Slide 12 text

Mister Spex Company Profile, Status Mai 2016 ECONOMIES OF SCALE

Slide 13

Slide 13 text

LEARNINGS •  Scalability (with proportional/ positive effects) is an exception •  Most systems don’t scale (in a meaningful degree) •  Optimize (till you drop) to scale constant •  Change the way of doing things on a different level to achieve disproportionately effects

Slide 14

Slide 14 text

WELCOME TO THE „INFORMATION AGE“

Slide 15

Slide 15 text

•  Discontinuous change •  Short product life cycles •  Continuous price declines •  Little customer loyalty •  Based on knowledge work INFORMATION AGE

Slide 16

Slide 16 text

KNOWLEDGE WORK IS DIFFERENT FROM ASSEMBLY-LINE WORK AND DOESN‘T SCALE CONSTANT •  Requires creativity •  Relies heavily on collaboration between individuals •  Doesn’t repeat itself •  Is unpredictable but emerges over time

Slide 17

Slide 17 text

SCALING THE TRADITIONAL WAY AKA. „ADDING MORE CAPACITY“

Slide 18

Slide 18 text

COLLABORATION IS HARD TO SCALE

Slide 19

Slide 19 text

ECONOMIES OF SCALE

Slide 20

Slide 20 text

HOW TO SCALE ANYWAY?!!

Slide 21

Slide 21 text

SCALING THE OTHER WAY Economic principle: •  Minimum: Variable input, fixed output (default option ... unfortunately) •  Maximum: Fixed input, variable output Do not ask how much resources you need to make X, but what you can achieve with existing resources. Scaling does not necessarily mean adding more resources. You can also just use the existing resources more efficiently.

Slide 22

Slide 22 text

10 BEST PRACTICES TO SCALE BEFORE ADDING MORE RESOURCES

Slide 23

Slide 23 text

#1: FOCUS, FOCUS, FOCUS!

Slide 24

Slide 24 text

•  Strive for throughput rather than (local) utilization (Culture of done) •  Don‘t worry about things that don‘t belong to your value proposition •  Use external services/ support/… •  Decide for (de-facto) standards •  Focus on what moves the needle/ makes the difference #1: FOCUS, FOCUS, FOCUS!

Slide 25

Slide 25 text

#2: CUT PROJECTS!

Slide 26

Slide 26 text

•  Most projects are “black hole projects” •  Overloaded with features •  Consider maintenance! #2: CUT PROJECTS!

Slide 27

Slide 27 text

#3: ESTABLISH BUSINESS REVIEWS!

Slide 28

Slide 28 text

•  Compare expectations with actual impact •  Understand deeply what drives success an what causes costs •  Derive lessons learned and apply them to the next projects #3: ESTABLISH BUSINESS REVIEWS!

Slide 29

Slide 29 text

#4: (N)ONE PROCESS TO RULE THEM ALL!

Slide 30

Slide 30 text

•  Conway’s law for processes —> You will run projects that match the process but not necessarily your needs. •  Don’t underestimate costs of process! •  Different processes for different project •  Focus on impact rather than utilisation #4: (N)ONE PROCESS TO RULE THEM ALL!

Slide 31

Slide 31 text

#5: ORGANIZE FOR COMPLEXITY!

Slide 32

Slide 32 text

“You already have the right people. You have a bad organisation” Niels Pflaeging •  Take cross-functional, self-organized and market-driven teams into account #5: ORGANIZE FOR COMPLEXITY! http://www.slideshare.net/npflaeging/organize-for-complexity- keynote-by-niels-pflaeging-at-spark-the-change-torontoca/15 http://www.slideshare.net/npflaeging/organize-for-complexity- keynote-by-niels-pflaeging-at-spark-the-change-torontoca/16

Slide 33

Slide 33 text

“You already have the right people. You have a bad organisation” Niels Pflaeging •  Take cross-functional, self-organized and market-driven teams into account #5: ORGANIZE FOR COMPLEXITY! http://www.organizeforcomplexity.com

Slide 34

Slide 34 text

#6: DON’T MIX UP INNOVATION WITH DAILY WORK!

Slide 35

Slide 35 text

•  Distingush between cash cow and the rising star of tomorrow •  Have separate standards (regarding sustainability, etc.) #6: DON’T MIX UP INNOVATION WITH DAILY WORK!

Slide 36

Slide 36 text

#7: RETHINK “THE RIGHT TOOL”!

Slide 37

Slide 37 text

•  Strive for small technology stack, don’t increase accidentally •  Stay with what you can do aka. “Schuster bleibt bei deinen Leisten” •  Create space for “experiments” #7: RETHINK “THE RIGHT TOOL”!

Slide 38

Slide 38 text

#8: KEEP IT STUPID SIMPLE! “Complexity is your enemy. Any fool can make something complicated. It is hard to keep things simple.” Sir Richard Branson

Slide 39

Slide 39 text

•  … not only on software level but solution level •  Business is complex enough •  “Indeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. [… Therefore,] making it easy to read makes it easier to write.” Robert C. Martin #8: KEEP IT STUPID SIMPLE!

Slide 40

Slide 40 text

#9: KNOW YOUR COST DRIVER!

Slide 41

Slide 41 text

•  Important for capacity planning •  Distingush between fixed, variable and stepped-fixed costs •  Stepped-fixed: Fixed over a certain range; at particular point, step increase in fixed cost #9: KNOW YOUR COST DRIVER!

Slide 42

Slide 42 text

#10: CONSIDER MAINTENANCE & LIVE THE LIFECYCLE! https://www.researchgate.net/figure/236189469_fig1_Development-of-Software-maintenance-costs-as-percentage-of-total-cost-Floris-and-Harald

Slide 43

Slide 43 text

•  Quality and automation are not negotiable (in core business) •  Effort for maintenance will eat up capacity •  Maintenance shouldn’t be the reason for scaling •  Plan removal of features like new projects #10: CONSIDER MAINTENANCE & LIVE THE LIFECYCLE!

Slide 44

Slide 44 text

LONG STORY SHORT ... •  Just adding more resources doesn‘t work in a knowledge work environment ... At least not in a proper way •  Give maximum principle at try and rethink way of working continuously •  Optimize till you drop before considering additional resources

Slide 45

Slide 45 text

THANKS! ANY QUESTIONS? How to scale if nothing is for free