Floating Development Schedules

The forum for ranting, raving, complaining and praising
User avatar
ghostrunner
GOAT
Posts: 30873
Joined: April 18 06, 9:40 pm

Re: Floating Development Schedules

Post by ghostrunner »

planet, I think the lesson here is that you need to push for less accountability for your department

TimeForGuinness
Hall Of Famer
Posts: 20007
Joined: April 18 06, 7:38 pm

Re: Floating Development Schedules

Post by TimeForGuinness »

Arthur Dent wrote:
planet pujolsian wrote:More times than not, the developers themselves are asked what is a realistic time frame for completion
In my experience, more often than not, when engineers or engineering managers are asked to project project completion, they are required to do so under intense pressure from business folks to make best case projections. If everything went perfectly, you might be able to get it done by day X. That is what they want to hear. We always explain that there is a high risk of not meeting that deadline or of producing a flawed product (which in my world means hundreds of thousands of dollars and months of delay) to fix predictable issues. And that doesn't even account for the unpredictable issues, which are more or less guaranteed to occur. But they want to hear the best case scenario, so they can make promises to customers, therefor virtually guaranteeing that they will be pissed off later when the foolish promises cannot be met. As a customer, I'd much prefer to hear a longer delivery time and then be pleasantly surprised if things come in early, than to be promised something quickly and then be denied. If you know that these schedules are consistently going to be missed, why are are you still promising them to customers, and then blaming the problem on the developers?

So, I think you may want to try and understand what issues your developers are facing rather than assuming that it is just a matter of accountability.
bingo

User avatar
TheoSqua
Next Gen Wart
Posts: 8951
Joined: April 22 06, 6:53 pm
Location: St. Louis
Contact:

Re: Floating Development Schedules

Post by TheoSqua »

Agreed with Kyle. Generally when i'm developing a script for the web. Writing and getting the page functioning takes about 60% of the time, beating out the quirkly little bugs that pop up in different browsers once the actual "program writing" is complete is a good 40%.

jim
Red Lobster for the seafood lover in you
Posts: 50393
Joined: May 1 06, 2:41 pm

Re: Floating Development Schedules

Post by jim »

I'm not sure what the levels of complexity, both in terms of size and interacations with other sytems, people have. But I can pretty much nail an estimate of one script, or a couple of scripts, or even dozens of related scripts. Where things get complicated is when you are dealing with 5 sub components of a system, each comprised of hundreds of modules each of which are hundreds or thousands of lines of code that deal with pieces that are not well understood. I am often dealing with black boxes, and if you don't spec those out exactly right then anything down stream is going to be affected. Example, our node registration system is being changed to interface with a new DNS appliance to support DNSSEC. This was not properly spec'ed out to us, and the middleware layer we need to write is constantly changing because as we write it and test we realize that there is some small but significant difference in how we thought it worked and how it actually works. Part of this problem is that the group responsible for giving us this information is learning as they go, and there is another problem where we don't speak the same language as well as they do. They have often accurately described something but not in sufficient detail. We have also encountered at least 2 show stopper bugs in the appliance API and a couple of other ones we could work around but were far from ideal, and that has pushed our schedule back as we wait for them to duplicate it on their end (not always easy as they have to have our environment set properly) and then a commitment from them to fix it and then finally the fix and release. We've taken pre-release stuff just because we need to get going, and of course we've found problems in that as well.

My management is wondering why it's late, and I tell them, and they don't always like or accept it, but that's life. If you want something where you can spec things out perfectly and get a perfect estimate then go be a ditch digger manager.

Post Reply