Improving the world with software
Better software. Better questions.
Essays on software development, teams and the craft of building things that last.
Essays from September 2014
3 essays from September 2014
-
The No Estimates principle: The importance of knowing when you are wrong
You started the project. You spent hours, no: days! estimating the project. The project starts and your confidence in its success is high. Everything goes well at the start, but at some point you find the project is late. What happened? How can you be wrong about estimates? This story very common in software projects. …
-
The Release Paradox: releasing less often makes your teams slower and decreases quality
Herman is a typical agile coach. He works with teams to help them learn how to deliver high-quality software quickly. Many teams want to focus on design, architecture, or (sometimes) even on business value. But they are usually not in a hurry to release quickly. Recently Herman conveyed a story to me that illustrates how …
-
How to create a knowledge worker Gemba
I am a big fan of the work by Jim Benson and Tonianne Barry ever since I read their book: Personal Kanban. In this article Jim describes an idea that I would like to highlight and expand. He says: we need a knowledge worker Gemba. He goes on to describe how to create that Gemba: …
Nothing matches that yet.
Keep the conversation going
The essays work best in company. Join the community to keep the questions coming.