cost estimating

Software best practice: Never say “X% done”

Note: This is a post from 2007 that I just updated a little bit because I think there’s still some value in it.

A lot of people have written to say that it’s unfair that I think developers should never say “I’m 75% done,” or “I’m 90% done.”

So, to explain myself, here’s why I think you should never use a phrase like that:

Software cost estimating in an agile development environment (PDF)

I’m currently working on a trilogy of “books” (booklets) about software cost estimating, and the third book in the series is about estimating the time and cost of software development projects in an agile development environment. The book isn’t complete yet, and some of it may not make sense without the first two books in the series, but I thought I’d release it here today, as almost everyone has some sort of “agile” development environment going today (or at least I hope so).

Estimating software development projects

I tend to forget that I've written a lot of articles and tutorials that are out of the content management system that I now use to run devdaily.com, and last night I stumbled across an article I wrote on software cost estimating that I happen to think is pretty good. So, to make that article easier to find, here's a link to my software cost estimating tutorial.

(As you'll see from the look and feel of those web pages, those pages are formatted very differently, but you'll still be on the devdaily.com website.)

Software cost estimating - Cocomo model variables alvin August 8, 2011 - 2:49am

Over time I hope to write more posts about software cost estimating, but for today I just want to list some of the software cost estimating variables from the model of the Cocomo II software application:

Software metrics: A Tufte-inspired graph for software development projects

I couldn't sleep last night so I started reading Edward Tufte's "The Visual Display of Quantitative Information", and I started thinking about software project metrics that might be useful to the team members on a software development project (including developers, business analysts, domain experts, and stakeholders), and how I would show these metrics in simple but data-filled Tufte charts and graphs.

Software cost estimating with Function Point Analysis

Someone asked the other day if I've written any longer tutorials on software cost estimating and/or Function Point Analysis. Sometimes I forget that this site has grown pretty large, and things like this may not be easy to find with the current design.

To help solve that problem in the short term, here are links to two software cost estimating and Function Point Analysis (FPA) tutorials I've written:

Function Point Analysis resources (FPA)

Just cleaning up around here lately, it looks like I never really linked up to some of the cost estimating and Function Point Analysis (FPA) tutorials and slide shows I've created. So without any fruther ado, here are some links to my free FPA tutorials and presentations:

Software cost estimating - new tutorials

I've published a new software cost estimating tutorial. As much as any tutorial I've ever written, this one is a work in progress.

That being said, I hope it's off to a good start. As mentioned in the tutorial, I'll update several items when I can get to some IFPUG documents that are currently stored in a box about 5,000 miles from my current location.

Software cost estimating presentation slides updated

I've converted my Function Point Analysis (FPA) and software cost estimating slide presentations, and they now play much nicer with IE. They aren't perfect yet, but they are much better.

For the record those presentations are at these URLs: