September 5, 2008
Walking On a Wide Line
So, many times in the past I have made mistakes about how to quote projects and learned quickly that I need to walk on a very wide line. That means I need to give myself plenty of room to fail on a quote. The problem lies in the fact that you really can’t quote something that has never been done. I have over 10 years experience and so it’s not that I don’t have the experience to give an accurate quote. We are on target much of the time but the times we aren’t on target have really hurt us in the past.
So, my partner suggested we only guarantee a sprint and quote projects in a certain amount of week sprints like a 4 week sprint or something like that. That’s something we have been forcing ourselves to do and also turning down work that doesn’t allow us to be agile in sprints like this. We’d rather not deal with the possibility of a big mess. It’s time software developers set standards and put their foot down and say “Look, we can’t be 100% sure that we will be on target with our estimate because we can’t assume we know everything about the project at it’s onset.” This is where the business people cry because you don’t know a budget. So, best to set a budget and then allow for a 20% bend so you have a target. Without a target your budget will turn in to a nightmare. If you have enough experience you should be able to pick out certain peices of a project which you know how long will take. You should mark the parts of a project you don’t have much experience with as unknown or risky.
At the end of a quote you should then know around about how much the whole project will take given the information you have. But you really should only guarantee accuracy and the quote for the first sprint and re-quote at the end of the sprint for the next sprint. Each sprint should be quoted as if it were it’s own project. This may be hard for some clients to accept but you have to make them understand that it’s not only for your protection but for their protection too. The only time I would say this is not necessary is for a very short project that doesn’t take that long. Like a 4-6 week project doesn’t really need to be broken up in to sprints.
Comments Off
Loading ...