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
• 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
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.
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!
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!
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
organisation” Niels Pflaeging • Take cross-functional, self-organized and market-driven teams into account #5: ORGANIZE FOR COMPLEXITY! http://www.organizeforcomplexity.com
• 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!
• 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!
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