D
dmac156
One thing that seems very odd about MS Project is that it is designed to
start on todays date, put in how long it takes to do a task, then tells you
when it's done.
That's great, but I'm usually given a due date for my project. I prefer to
work backwards from that date. However MS project seems to be a nightmare if
you approach it that way. Am I missing something?
Here's an example of what I run into. Let's say I have a website release in
October 1st, and I know it takes 2 weeks for content development, 2 weeks for
programing and 2 weeks for QA. It would be easy to put in October 1st as the
finish date, put in the durations of the tasks, link them and have it spit
out the start date. I know how I can do this, but I have to force it, and it
becomes a huge mess on a large project.
How do people deal with this? Do you build your dependencies and duration
then just keep pushing the start date out until you hit the finish date?
That seems backwards, but then this is from the company that forces me to hit
"Start" to shut down my computer......
start on todays date, put in how long it takes to do a task, then tells you
when it's done.
That's great, but I'm usually given a due date for my project. I prefer to
work backwards from that date. However MS project seems to be a nightmare if
you approach it that way. Am I missing something?
Here's an example of what I run into. Let's say I have a website release in
October 1st, and I know it takes 2 weeks for content development, 2 weeks for
programing and 2 weeks for QA. It would be easy to put in October 1st as the
finish date, put in the durations of the tasks, link them and have it spit
out the start date. I know how I can do this, but I have to force it, and it
becomes a huge mess on a large project.
How do people deal with this? Do you build your dependencies and duration
then just keep pushing the start date out until you hit the finish date?
That seems backwards, but then this is from the company that forces me to hit
"Start" to shut down my computer......