Reporting Task Delays/Splits from PWA MyTasks 2007

[Gary Zag]

yWe have people updating their task status from PWA. This works great if the
can start and work on the task as scheduled. Reporting back when thing don't
go as planned is a different story. If the task is not started on time is
not an issue either. The person selects a new start date and sends it to the
project manager. All good.

Once a task is started and a person is unable to work on the task is where
we are having a reporting problem. If the person changes the finish date
after the task has started it adds additional hours to the tasks which is not
always the case. The person may just not be working on a task for a few days
before he gets back to it. Is there a way to show this from PWA? Similiar
to how you can split a task from Project Pro.

Gary

 

[Dale Howard [MVP]]

Gary --

The only effective way to handle this situation is to use the "Hours of work
done per period" method of tracking, set to track progress on a daily basis.
Using either of the two other available methods will simply not work for
you. Hope this helps.

 

[Gary Zag]

Dale,

Thanks for your reply. We are tracking tasks by hours of work per day. The
issue is when a task is started for a day or two and then they can not
continue for a few days. We are looking for a way for the resource to tell
PWA that they will not work on the task untile a new date which would then
calc the new finish date. Similiar to splitting a task in Project Pro but
having the resource do this from PWA.

We were able to do this in PWA 2003 by adding 0 hours for the day before you
were going to continue. This does not work in PWA 2007 because all days
defaults to 0 for work completed instead of blacks like PWA2003.

Gary

 

[Dale Howard [MVP]]

Gary --

Thanks for the extra info. I can't think of any automatic way to handle
this in Project Server 2007 from the team member's perspective. I think it
would be a good idea, however, to make sure your PMs know how to reschedule
uncompleted work from past time periods into the current reporting period.
They can do this using Tools - Tracking - Update Project. Hope this helps.

 

[Gary Zag]

Thanks Dale. I was hoping that the team members could input this data into
PWA as they may have a better idea on when tasks would resume instead of
having the PMs reschedule it into the next reporting period. Thanks for the
help.

 

[Gary L. Chefetz]

Gary:

Try having the resources submit zero hours for the the last date of the time
period that they did not work. I think this might cause the reschedule. It
really is the PMs job to do the rescheculing as part of their weekly
updates, as Dales says.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Gary Zag]

Gary,

Thanks for the reply. Posting zero hours to the day before they are going
to restart the task worked in PWA 2003 but not in PWA 2007. The diference is
that 2003 default was blank cells and in 2007 the default is zero hours.
Because of this it must not see it as a change to submit.

I am now curently working with the PMs to reschedule this work into the
future using Project Pro.