Comments on: Estimating time for Web Projects more accurately: Part 1

By: thesambarnes

thesambarnes — Thu, 03 Jun 2010 21:11:34 +0000

Glad you like it Andrew :)

By: Andrew

Andrew — Wed, 02 Jun 2010 13:52:07 +0000

Great Article Sam! Such an important issue for Freelancers. Looking forward to part II

By: News: Websites, articles, jobs and feeds | Website and Web Project Management tips | Web Project Management Junkie | thesambarnes

Wed, 08 Jul 2009 22:35:04 +0000

[...] to the popularity of my Estimating Time for Web Projects series I decided to re-write the two articles into one and submit to Smashing Magazine for [...]

By: Estimating time for Web Projects more accurately: Part 1 | Web Project and Website Management advice | Web Project Management Addict | thesambarnes « Netcrema - creme de la social news via digg + delicious + stumpleupon + reddit

Sat, 27 Jun 2009 20:40:34 +0000

[...] Estimating time for Web Projects more accurately: Part 1 | Web Project and Website Management advice…thesambarnes.com [...]

By: Paul West

Paul West — Wed, 24 Jun 2009 08:33:13 +0000

No, I managed to keep up! My problem is that I am with an agency that has a strong off line and design pedigree. Getting peeps to think in terms of functionality and content first rather than design first is a real challenge. Most jobs are sold on a few visuals and ball park quote which fits the budget. Not great with you find out when you find out – to use your phrase – they want facebook for £4000!

By: thesambarnes

thesambarnes — Tue, 23 Jun 2009 21:33:05 +0000

@Paul, thanks for your comments. Hope I didn’t lose you after Part II :)

By: links for 2009-06-19 « Mandarine

links for 2009-06-19 « Mandarine — Sat, 20 Jun 2009 04:11:22 +0000

[...] Estimating time for Web Projects more accurately: Part 1 (tags: business productivity management) [...]

By: Paul West

Paul West — Fri, 19 Jun 2009 09:38:20 +0000

First time on your site. Really like what I am reading, moving on to Part II now. You now have another fan!

By: thesambarnes

thesambarnes — Sat, 06 Jun 2009 16:13:54 +0000

@Richard, you’re right about getting a range. Often I’ll start with asking what kind of budget do they have, and if there is even slight hesitation to answer I’ll then ask for a range instead.

Good point, much better than mine in my article :)

By: Richard - Accessible Web Design and Test

Richard - Accessible Web Design and Test — Tue, 02 Jun 2009 10:41:58 +0000

I would echo the part about using a ball park figure if estimates are needed very quickly. However, I was taught that giving a range is better than giving a figure. In other words if I say the ballpark is approx £15K that is fine but the figure 15 tends to get lodged in the subconcious. It is better to say the range is approx £12K-£18K which as well as not fixing a particular figure, also gives an idea of the confidence in your estimate.

By: Branden Faulls

Branden Faulls — Wed, 29 Apr 2009 23:19:42 +0000

Great post padawan! Estimation is such a dark art and so rarely are the benefits and pitfalls illustrated so lucidly.

One of the things that makes estimation so difficult, and one of the ways that Agile methods excel, is that the person doing the estimation frequently has scant understanding of the rate of their team’s productivity. Agile cracks this by doing all estimation internally using a points based system and then measuring the team’s productivity, or ‘velocity’, over time. This gives a project leader an empirical measure of what can actually be achieved within budget.

The real benefit of having your team estimate using a system of sizing points vs hours/days, is that it removes the emotional dimension from estimation. Workers can get a gut feel for the ‘quantity of effort’ without having to acomodate unknowns like interruption, etc. We all know how inaccurate a proud developer’s estimate can be, and how charmed our boards/clients are when those estimates turn out to be works of fiction.

Great work. Can’t wait to read more.

By: thesambarnes

thesambarnes — Mon, 20 Apr 2009 20:48:51 +0000

Thanks for the comments guys! @Dina & Cola, I may have to check out them books, a black art it sure is!

@Danny, this post will probably make many feel it’s aimed at them because they know, like me, they’re guilty of taking the short route to compiling a quote from time to time ;-)

@Mike & Kathi, believe me, it’s as comforting to know I’m not alone too!

By: David Lydon

David Lydon — Mon, 20 Apr 2009 19:11:51 +0000

Thanks, looking forward to the follow-up!

By: Kathi

Kathi — Mon, 20 Apr 2009 13:15:09 +0000

Great Article. For me, estimating is the most hated part…JESUS. I realy hate it…

By: Mike Schell

Mike Schell — Mon, 20 Apr 2009 13:10:15 +0000

I take some comfort in seeing that it isn’t just me! This is spot on so far.

By: Abdurrahman Gemei

Abdurrahman Gemei — Mon, 20 Apr 2009 12:45:46 +0000

Nice post! I like your theme!

By: Danny Barnes

Danny Barnes — Mon, 20 Apr 2009 08:58:09 +0000

Why do I feel this is solely aimed at me? Roll on Part II.

By: Cola

Cola — Mon, 20 Apr 2009 08:33:13 +0000

Interesting post, Sam. I’m spending the next few days planning/estimating a project and as its the first large internal office one I’ve work on (as opposed to client-based) the time estimate is really, really important. I’m not familar with the book Dina recomends, but I do delve in and out of Catherine A. Tomczyk’s “Project manager’s spotlight on planning”. I’ll be watching for Part II!

By: Dina

Dina — Mon, 20 Apr 2009 01:22:12 +0000

Nice post! I’m a big fan of making project estimates… actually, I just find the topic really interestingand am always amazed at how quickly and carelessly people rush through this critical phase of a project. Probably the best book I’ve read on the topic is Steve McConnel’s “Software Estimation: Demystifying the Black Art”. I look forward to reading part II!

-dina