Use #NoEstimates to create options and deliver value reliably

Why do I use #NoEstimates? Certainly the first reason is obvious in the name of this movement. But there are may other reasons. One of the reasons that does not get enough airtime is that it creates more options than using pre-estimated methods to manage software projects. Value is unpredictable, generate options to explore the …

Story Points Considered Harmful – Or why the future of estimation is really in our past…

This article is the companion to a talk that myself and @josephpelrine gave at OOP 2012. We have a lot to learn from our ancestors. One that I want to focus on for this post is Galileo.Galileo was what we would call today a techie. He loved all things tech and was presented an interesting …

Tired of useless boring planning meetings? Read on, I’ve got a solution for you

In a meeting today I was graphically reminded of how some of the basic concepts in software development still escape many of us. Case in point, the meaning of capacity. In many people’s minds capacity still means “how many man-hours we have have available for real work”. This is plain wrong. Let’s decompose this assumption …

The value Black Swan (or the killer improvement in software development)

Thinking back to how we value our work, we must recognize that, in software, quantity is not value! The number of things we do in a sprint does not vary too much, we can consider it a Gaussian (assuming correct and consistent measurement) — or in Black Swan (TBS) parlance: velocity is a variable from …