[UPHPU] Software Development Scheduling advice

[John David Anderson]

On Jan 30, 2007, at 1:18 PM, David Boucha wrote:

> I'm having to put together a software development schedule here at
> work. I'm working on version 2.0 of an app and now my boss wants a
> schedule. I'm having a hard time estimating how long tasks will take.
>
> I'm looking for techniques and advice on how to set this up. Any  
> ideas?

Estimates for any project that is even moderately long are just  
fantasies.

I like to work in iterations on the front end for as long as the  
client wants. Changes are easy, and the templates you have at the end  
of the process can be kept for use in the real application.

Once you've nailed down the interfaces and the client has browsed  
through them with a browser, you can work on the back end. Estimates  
for a front end that has been well-prototyped and iterated are much  
easier, much more realistic, and the end product is much more  
satisfying to the client.

Mostly because they're able to feel like the thing isn't set in stone  
once you start doing any coding at all.

This is also good, because you get paid an hourly rate to prototype  
and estimate, and those estimates are much, much more accurate. It  
saves you time and money on both ends of the project.

-- John