The most valuable question for your software project

Every time a software project is started, a dance starts: the dance of project approval. Decision makers and project delivery team take different positions at a table, some ask questions, others do their best to respond, given that these questions are typically about the future. Some of the questions are so much into the future …

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 …

Which do we need the most, Project Managers or Line Managers?

Should we organize around the delivery of products or along the structure of our organization? Which organizational paradigm is the most effective or efficient? This is a question that most managers struggle with regularly. At least when they are asked to “re-organize” their respective organizations. In Europe (and I suspect elsewhere) this has led to …

Using #NoEstimates when deciding which projects to take on

One of the questions (Part I, Part II) that emerged from the #NoEstimatesQuestions discussion on twitter was: “How do I choose between options or opportunities (without having estimates regarding the cost)?” The thinking goes: I can spend some time doing A or B, but which should I do first? To answer this question we can …

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 …

Patterns of Agility. How to recognize an Agile project when you see one…

Instead of fighting about “who’s agile” or “who’s more agile than whom”, it would be useful to create a set of patterns, that once recognized would help us define if we are or have been able to successfully implement an Agile life-cycle for our project and portfolio. These patterns or symptoms are useful for us …