This book is for software engineering leaders who are responsible for leading teams. It also dives into the unique complexity and challenges that comes with leading, aligning and supporting multiple software teams. This book aspires to provide you with helpful and reusable approaches that can be leveraged to bring about a greater level of efficiency into your role as a leader. There are many books written around leading teams or leading people, this book takes a lens of what specific practices and initiatives you should be investing your time into when leading software engineering teams.
The book has been inspired by the many people I have worked with, learnings from practices I have implemented, as well as books and blogs I have read over the years. I see this is a book that leads itself to many iterations and should evolve as I discover new practices and techniques that help me improve the way I lead software teams. Regardless of the size of your software team, if you find yourself needing to better balance both the technical and people aspects of leading teams, or guidance on initiatives you could be running to improve team alignment, effectiveness and engagement then this book is written for you.
About the author
I’ve been working with and leading software engineering teams for the last 2 decades. I focused the first part of my career with all things technical, and still work on many software development projects in my spare time. However, I chose to refocus my career towards leading software teams throughout a range of different organizations including Yahoo, NewsCorp and William Hill. I've led teams with just a few software developers in a single team startup to leading around 150 software developers, testers and architects in many teams across multiple countries. When leading software teams I focus on context, not control, in that I will work hard to ensure my teams have the context they need to own decision making in their entirety within the team without me.
I aspire to be a software leader who has a reputation for building software teams that people positively remember being part of, where they were technically challenged, where they owned their decision making and had an opportunity to progress their career while still adding value to the wider organization.