Leading software teams
Successful software projects need two things:
- The ability to learn: a feedback loop and quick iterations to learn how to solve the problem you’re faced with)
- Cohesion of people and purpose: clarity on the problem to solve, confidence in colleagues, and trust in how the team works together
Some teams spontaneously succeed at both of these. Often, they’re very experienced or have succeeded together before. In all other scenarios, someone has to wear the leadership hat to keep the team pulling together, in the same direction.
Below, my ever-evolving hypothesis of how I build effective, creative, and fun teams that deliver ambitious software.
- Teams at the top of their game
- Six easy pieces on Shape Up
- Make peace with estimating software projects
- More of a strongly worded date than a deadline, tbh
- More on my principles
- Keep a backlog, but not too deep
- Delegate, don’t dictate
- So your estimates were wrong – don’t worry, do try one of these ideas.
- Don’t let mythologies of friction develop
- A parable of two adventurers
- Hurry up and flub your first fifty projects