Delivering quality software products isn’t magic. It’s all about setting your teams up for success and focusing on what matters.
Building software is hard, but don’t let that stop you.
Telling developers what to code is the most expensive way of building a software product.
Mapping estimates on a timeline is the best way to create the most brittle plans.
Yet it’s precisely what most of us do.
There’s a lot of talk about self-organizing teams and long-term roadmaps. But we don’t talk enough about how to get there.
Plans are the lifeblood of software development.
A good plan puts teams in a position where they can make and keep promises.
A plan is not an upfront attempt at predicting the future but an iterative feedback system that helps us optimally allocate the team’s limited resources.
Without a plan, we’re just building stuff.
Every week I send out a free newsletter with practical ways to build actionable plans.
Technical leadership is a weird field to work in. It’s a formidable combination of deep technical insights and a wild variety of people. The managers who roll into tech have a hard time grasping the overwhelming landscape of frameworks and architectures. Coming from a non-technical background is the hardest path to technical leadership. But the […]
Building a product is an exercise in managing expectations. We gather ideas and turn them into a gadget that solves problems. These ideas can come from everywhere. — team members, customers, competitors — you name it. Even a small team with a single customer can generate an infinite stream of new ideas. Ideas are the cheapest renewable resource on […]
Dependencies are evil. They lead to domino effects and brittle plans. Instead of getting work done, they are the reason you can’t start just yet. In project management, a dependency is defined as a relationship between two tasks. When Task A needs to be completed before Task B can start, we say B depends on […]