Re: Updating via timesheet

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Mike --

Even though he's using Project Server in his environment, I don't think his
question is really a Project Server question. In fact, I think it could be
answered just as well or better in THIS newsgroup, because his question gets
at the heart of how to create a good schedule in the Microsoft Project
application. Based on the years of valuable experience that the Microsoft
Project desktop app users have in this group, I'd love to hear their
opinions. Just a thought. :)

--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We wrote the book on Project Server"


"Mike Glen" <glenATmvps.org> wrote in message
news:OhKC00feGHA.3484@xxxxxxxxxxxxxxxxxxxxxxx
Hi Jan,

Try posting on the server newsgroup. Please see FAQ Item: 24. Project
Newsgroups. FAQs, companion products and other useful Project
information can be seen at this web address:
http://project.mvps.org/faqs.htm

Mike Glen
Project MVP


Jan M. wrote:
Hi everyone,

I need some expert judgement on this one:

We use "Hours of work done per day or per week" as the method of
tracking. Each week, the resources adjust both actual and remaining
time in the web access. Then, we expect Project to do is job of
forecasting a new finish date for us.

I personnaly think MS Project is very good at that especially when:

-there is only one resource per task(exept for fixed duration tasks
like meetings, training...)
-assignment unit is really significant (preferably 100%).

People here seem to think that detailed planning is not worth the
effort. Our schedules are not broken down enough (in my opinion) and
we always end up with many resources assigned to each task (high
level deliverables). Tasks durations are often ridiculously long due
to the low capacity of certain of our resources who have to perform
recurring activities each week ( very few are 100% available for
project).

The result is a lot of manual updating in order to keep the model
valid. It seems to me that we're not using the software to its full
potential.

Am I missing something?

Is there a way I can satisfy executives by keeping schedules roughly
detailled and at the same time, get the most of MS Project modeling,
forcasting and tracking(Server timesheets) capabilities?

Thanks in advance

Jan M.





.

Quantcast