Software Development Best Practices Blog

Fail Yet Succeed?

If you build EXACTLY what “they” tell you, you do it in the timeframe they ask for, and at the cost they wanted to pay, is that a successful project? The project is On time On budget Delivers the requested functionality No defects The team is ready for the next project Is it successful? “Yes,” you say. Rightfully so. But what if I tell you that the above project (project A) was followed by another...

  1. Posted on September 16, 2009 12:42:PM by Earl Beede to Practicing Earl
  2. Testing & QA, Technique, project management, humor, context, quality, requirements, Management

Defining 'Done'

In software development, like many other areas of life, we need to decide when some item of work is done. The decision of "doneness" has wide impacts as under-done creates defects, downstream rework, and lost opportunity costs while over-done wastes time and resource and incurs its own lost opportunities. To be even more critical, in my review of documents from hundreds of clients I find that work items are often under-done in important areas and over-done in trivial ones. That is,...

  1. Posted on September 8, 2008 1:32:PM by Earl Beede to Practicing Earl
  2. Testing & QA, Technique, humor, quality, done

Quality Time

At Construx I teach both the Estimation seminar and the Advanced Quality seminar. One question I usually get during the Estimation seminar goes something like this, "How can I estimate how long quality will take?" Now this is a fascinating question in that it is so wrong and yet so important to the people asking it. Let's...

  1. Posted on October 2, 2007 6:50:PM by Earl Beede to Practicing Earl
  2. Testing & QA, humor, testing, quality