cfp abstract review request: Lessons learned from scaling software

I’m preparing my call for paper abstract for upcoming conferences. You can find current version below, feel free to make any suggestions. If you prefer more efficient way of making comments you can use this gDoc.

Scaling software is hard. One can argue that scaling software development teams is as hard as creating scalable solutions. Judging by my experience in many cases it’s not less crucial though as it contributes to achievement of success as well.
A couple of thoughts from my experience with scaling teams I would like to discuss. As team grows:

…from somewhat small to big I prefer to move focus during interviews and team development from checking skill set towards culture alignment with current team

…development environment and toolset is becoming an obstacle more exponentially than linear

…end-to-end responsibility (Spotify-tribe-alike) helps in both work division and efficiency

Related

Computer Science and MBA graduate, responsible for managing IT teams for the last 4 years. Has experience working for different-size companies ranging from small start-ups to corporation that deal with different IT businesses (firmware, device drivers, mobile, eCommerce, social media, big data, financial markets). Currently a senior dev-ops working for one of banks providing enterprise applications enabling trading on financial markets. Involved in organising Tricity Java User Group and Polish edition of Washington Business Week. Interested in behavioural economics and psychology.