Category: estimation

Some thoughts after another pleasant conversation with Colin Hammond of ScopeMaster.

Estimation and a tiny bit of code. ScopeMaster took up my challenge.

I don't like estimates in this world. Perhaps you do. If so, and you're so inclined, pick up this challenge. I'll tell you everything I know to help you.

Today we'll try to fix the collision logic to accommodate our origin changes, and to make the invaders explode.

Despite my concerns about experienced coaches advocating against practices that are often quite useful, there are a few things where I'd at least advise great caution.

A Twitter conversation and some reading has triggered some new, and probably some old, thoughts on estimation and the #noEstimates tag and meme.

This is a small excerpt from The Nature of Software Development. It's a good reminder of some ways to think about value.

I wrote this in response to some tweets from an esteemed colleague, who I think is a bit less sensitive to dangerous ideas than I'd prefer our 'thought leaders' to be.

Another little tweet-storm about estimation. I think it's useful and not as easy to use as some people think it is.

Yesterday, I tweet-improvised the following thread. I had intended to write it up later as an article on my site, and here it is. It received a number of replies and comments, and I'll address some of those here as well.

You're probably wondering what I've said about estimates and the NoEstimates movement. Well, wonder no more. (bumped)

Generalizing from a few results isn't proof. In this article I'm going to prove that by generalizing from a few results. Wait, what?

Kate and Dan estimate a new project. Or do they?

The Estimate-Commitment relationship stands in opposition to collaboration. It supports conflict, not teamwork.

After a lot of email and blogging, Steve McConnell and I "Came out by the same door where in we went".

Semantics is important. Or is it 'are'?

In which we search for common ground and disputed ground.

Steve makes some great points. I think I'd make somewhat different ones.

A recent Twitter conversation bugged me (and bugged Clarke Ching even more). Here's why.

Apparently the word 'estimates' is not clear. Here's what I mean and don't mean.

You keep using that word. I don't think it means what you think it means.

Slicing is easier and better than estimation for projecting done. And slicing adds value, while estimation does not!

Keep seeking better ways.

The conversion from XProgramming.com to RonJeffries.com is essentially complete. Let's look at some learnings.

A few thoughts in response to a discussion on the Scrum Development list.

We've been working on the XProgramming replacement project since late September, so let's talk about estimation.

Project Description as posted on github pages.

Overcoming the Estimation Obsession