@johncutlefish I’ve managed software development with no estimates. I don’t see how “why estimates” makes sense in that context. #NoEstimates clearly states that I’ve worked without estimates. Like saying “Gluten free” vs “Why gluten?”.
@johncutlefish Or saying “Coke Zero” vs “Why Coke without sugar”. Coke Zero means this drink has #NoSugar. In this context it would be a bit nonsensical to say to say “this drink has Why sugar”. It can have no sugar, or less sugar, or the normal amount, or even extra sugar.
@johncutlefish Once the #NoEstimates hashtag started growing in usage I have used it as marker for a bigger conversation: “Let’s talk about why we do the things we do, with particular attention on the things we do without questioning or verification as to their benefit.”
@johncutlefish But at its heart is this simple start: “I’ve managed software development without estimates, I’m interested in talking with others who have done the same. Let’s compare notes.” It’s worked very well this way.
@johncutlefish I see little value in debating or arguing the usefulness of estimates for software development. Some people believe it has value to them, and I’m pleased for them work in any way they want. There is no benefit to me to convince them otherwise, and I have no interest in doing so.
@johncutlefish On the other hand, I love collaborating with folks who are willing to explore working without estimates. It’s worked well for me, and I’m interested in hearing about how others approach working without estimates in their own environment. What might I learn? #NoEstimates
@johncutlefish #NoEstimates and #WhyEstimates are about two different conversations. #NoProjects and #WhyProjects would also be about two different conversations. I certainly have seen how some folks are “turned off” by #NoEstimates. So as they say, to each their own.
