Are Inaccurate Estimates Killing Your Business?
This is something that happened yesterday and today that I want to share with you.
We were working on creating estimates for a fair sized project, perhaps a 3 or 4 month engagement. While we were getting estimates, we had different developers giving us times for the same aspects of the project to check against one another. We ask production team members, developers, designers, project
Testing New Developers
But when we get a new developer, we don’t always tell them exactly the process. We tell them, “Take a look at the scope, put in your hours.”
What we ended up this time was about normal for most developers. The new developer didn’t really want a take at the whole thing scope of work. They breezed over it then they just came back and they
A More Experienced Developer (That We Trained)
The more experienced developers, whom we had trained on our process, reviewed the document very
“I think is gonna be more than that. I think it’s gonna be a bigger project than you’re expecting” I replied.
In typical developer fashion he responded, “I’ll take a look. You may be right.”
He reviewed the document very thoroughly and put all his hours in
“Perfect, that’s exactly what I expected.” I responded.
Here’s the moral.
Very often, developers, designers, production people, are gonna take a look at something and give it a broad stroke. With a quick
Take a look at the SaaS Costing Guide!
So, as an agency owner or project manager, you must make production team members delve into your information architecture and ask about every single feature, then estimate them down to the fifteen-minute increment. When production team members do this they almost ALWAYS find that the project is going to take a lot longer than they initially expected.
That means you need to write a full project scope for your website or application!
If you don’t write break down your project granularly how will your team calculate hours on a piece-by-piece basis
If you do write it out, it will give you the most accurate estimates you can get on your website or application project.
Otherwise, you’re going to end up estimating your project duration at a month, and it’s going to take three (sound familiar?).
Then you’re gonna be months behind on your timeline, thousands behind on budget, and have a
So avoid a lot of pain and a doomed project from the start by taking the time to plan out your project thoroughly from the beginning and get granular estimates. This way, everyone is happy, especially you.
For a thorough explanation on how to scope a website, software, SaaS, or web-application project take a look at either this