[Resolved] Timelines

[cbrknight]

I have a question for all you heavy coders out there...

What is the basic timeframe for writing and testing a site or project?

Every project my boss gives me he expects done in a day. I dont think that is possible for most of these projects. What should I tell him?

[Shrike]

Go up to your boss and do this: :rolleyes:

There is no set timeframes, every project is different. You should sit down and spec out each area, and come up with a time allowance for each area.

Again testing time depends on the complexity of the project. At my company we have a number of testing phases - at the unit test level, functional level, and UAT (user acceptance testing) level. Then you need to allocate further development time to fix the bugs which the testers found :)

[Elizabeth]

It depends on the depth and breadth of the project, how many other people are involved, and how many other projects are going on at the same time. (I had a boss once that would hand out major projects like they were candy, then say "why don't you have that done yet? You've had it for 3 weeks", as if that was the only project I had to work on).

One of my favorite phrases (stolen from the quality control guys) is "Nine women cannot make a baby in one month" - sometimes things just take time.

It's not just bosses that don't understand about things taking time - it can be clients too. If they really understood what it takes to complete the projects, then they'd be doing it themselves. One thing I do for my clients that seems to help is I spell out every sub-task and sub-sub task when giving them the quote or at the start of a new project. It helps me figure out what I need to do and how much I need to charge, and it helps my client understand what it takes to complete what they're asking. Don't know if that would help with your client, as some bosses could care less, they just want the job done. But you could always try!

hth

[cbrknight]

I think I will try this...

I am spelling out every little thing i have done and all the "little" changes he has asked for. The problem I run into is he thinks everything is simple. I am the only designer all the coding, graphics, and testing fall in my lap. I end up doing alot of changes "on the fly" I test as best I can and wait til a user does something I didnt think of then go and fix it. All the while waiting with clenched teeth for my boss to say "good... now can you make it do this???"

[pohopo]

IMHO,

What you do is create a project plan and with that you can not only determine how long it will take, but you can give your boss something to show how much work it is. Before you start the work make sure you have your boss sign off on the project plan. Any changes he requests once development starts should require a change control process.

Bosses love and need to know what is happening. They don't want to be suprised. So if you tell the boss things are running behind he/she should already have ideas on why because they are up to date with all the potential risks of the project.

And to answer your question, my projects average around 4 months long. If a project is really big it will be broken down to 4-6 month chunks.

[piersk]

Originally posted by Shrike
Go up to your boss and do this: :rolleyes:

Shouldn't that be: Go up to your boss and do this: http://www.computing.surrey.ac.uk/personal/ug/cs31bc/ffh3.gif



Please note I don't actually recommend doing this. You will probably get fired...