Skip to the essays
All essays

Joel on Software gets close to “a universal truth” software development

The important phrase is at the end of this paragraph… Wow, That’s really on the spot. That’s exactly the same time we saw at our company (average of many projects) a validation/testing/debuging phase takes… when you use waterfall!!!! Lately we’ve got the period from “last feature added” to “release” in a lot less time (no …

The important phrase is at the end of this paragraph…

Wow, That’s really on the spot. That’s exactly the same time we saw at our company (average of many projects) a validation/testing/debuging phase takes… when you use waterfall!!!! Lately we’ve got the period from “last feature added” to “release” in a lot less time (no statistics yet though), this happened after a transition to Agile (we are using a Scrum-like method).

Debugging is the science phase. Science is difficult to schedule because you’re looking for things, and predicting when you’re going to find them is remarkably difficult. Unless you know in advance how many bugs you’re going to find, you don’t have an ice cube’s chance in the Sahara to work out a detailed estimate of how long this phase will take. Here at Fog Creek we’ve learned that for a new release of FogBugz, this phase takes at least 12 weeks, sometimes a little more, and we just leave it at that.

Check the full post here.

Keep the conversation going

The essays work best in company. Join the community to keep the questions coming.

The #NoEstimates book and its companion volumes

Chapter 1 · Free PDF

What if better planning started with a different question?

The first chapter of #NoEstimates argues that the “deliver on time” challenge is answered by a different question. Read it, and see whether it changes how you plan the next piece of work.

Free PDF of chapter 1. No purchase, no library access. How we handle your details