Re: PWA Timesheet and not entering a Zero value in actual Work

Tech-Archive recommends: Speed Up your PC by fixing your registry

Thank you Dale.

Sorry about posting in the wrong newsgroup.

I got more information about this few hours after I posted my question.

The idea to entering a zero is use as an easy way for the project manager to
known if a ressource did not work on a task and avoid asking the question if
the resource only forget to enter his time. Forcing the resource to enter a
zero confirm that he not forget.

Thank you for you advise.

Bye

"Dale Howard [MVP]" wrote:

Regis --

In the future, please post your Project Server questions in the
microsoft.public.project.server newsgroup as this newsgroup is devoted to
the Microsoft Project desktop application only. To answer your question,
the grapevine information you have been given is in error. For example, if
a team member worked 8 hours on a task on Monday, did not work on it Tuesday
and Wednesday, and then worked on it again for 8 hours on both Thursday and
Friday, the team member could simply enter 8 hours on Monday, Thursday, and
Friday and submit the update to the PM for approval. When the PM approves
the task update and processes it into the Microsoft Project plan, the system
will automatically enter the Actual Work on the task as follows:

M T W Th F
8 0 0 8 8

You can see the above information in the Task Usage view in Microsoft
Project. Notice above that the system will automatically enter zeroes for
both Tuesday and Wednesday, as this is what is implied by how the team
member entered his/her actuals by not entering anything on Tuesday or
Wednesday. Hope this helps.

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


"Regis" <Regis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:02CD028D-EB2D-4ED8-8185-CE095148A1B6@xxxxxxxxxxxxxxxx
Hi

We are going to start using PWA for the first time in our enterprise and
I'm
a newbie with tools.

I heard through the grapevine that if an assigned resource on a current
task
doesn't enter the value 0 in the act. work, this could have an impact on
the
schedule or in the way background calculation is done. In other word, if
no
value is entered (keeping the field to NULL), we can have some issue.

I want to ask to resources to enter a zero when they have not work on a
task
during a day.

As you can imagine, they will probably be have some objections to do it
asking to me why PWA doesn't understand a null to be as a zero.

What is the impact of not enter a zero. Is the impact is affecting the
schedule?
I did some test and the progress into MS-Project is working correctly
using
Null or a zero in Percentage completed.

Is the impact is then more related on budget or on resource usage
calculation?

Can you please, explain to me the importance to enter a zero instead of
just
keeping the null value into PWA?

Thank you to all for you great support thought this forum.






.

Quantcast