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
- …it’s more crucial to mix “old” tribe with “newbies”
- …maintaining team integration is much harder so motivation stack (brown bags, knowledge sharing sessions, ship it days, 20% free time) helps _a lot_ (introduced by Atlassian)
- ….the bigger team is the more work from leader is required to maintain the same team efficiency, spirit and culture
- …understanding organisational behaviour is more crucial along the way
- …self-aware leader comes more in hand
2 thoughts on “cfp abstract review request: Lessons learned from scaling software”
Do you have any video of that? I’d like to find out some additional information.
Videos are available in polish version of post that you can find at http://blog.bnowakowski.pl/jezeli-chcesz-przybic-mi-piatke-lub-posluchac-mojej-prezentacji-w-kwietniu/. They’re there because videos have polish audio. I’ll have this presentation in english at http://cfp.devoxx.pl/2015/talk/XQH-5796/Lessons_learned_from_scaling_software from which I’ll upload video once it occurs (-;