Re: Reporting Mode

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Dale Howard [MVP] ("Dale)
Date: 06/30/04 

Date: Wed, 30 Jun 2004 14:51:14 -0600

OK --

If you are using the managed time periods feature of Project Server 2003,
then your company needs to develop a standard procedure for progress
reporting and when managed time periods are closed. One of my former
employers had a formal requirement that team members must enter project
progress no later than Tuesday morning at 10:00 AM for the previous
reporting period. At 10:00 AM the reporting period was closed and no
progress would be accepted by the system for that reporting period.
Obviously this process could not work unless there was a penalty for
non-compliance with this procedure. In my employer's case, repeated
non-compliance was considered grounds for termination...period. So,
whatever procedure you folks develop must have "teeth" so that everyone
participates fully in the reporting process.

Entering actuals for people who go on vacation is problematic. How can the
resource perform work if they are on vacation? If someone else is
performing the work on their behalf, doesn't the substitute resource need to
log and report the work on their own time***? Again, I believe your
organization will need to develop a methodology for handling this situation.

Also, each managed time period can only be closed by those with
administrator permissions in PWA. Hope this helps. 

-- 
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
Denver, Colorado
http://www.msprojectexperts.com
"We wrote the book on Project Server"
"OK" <OK@discussions.microsoft.com> wrote in message
news:1FAA451E-8A8F-4B54-9BC4-0979B5ECF6CD@microsoft.com...
> Dale,
>
> reporting period = managed period? Am I right?
> And who will close this period? Is it possible to enter the data if a
person is on vacation?
>
> Sorry, if it's another question.
>
>
> "Dale Howard [MVP]" wrote:
>
> > OK --
> >
> > If you are talking about reporting and updating actuals submitted by
team
> > members, then yes, it is very possible.  What I believe you have is a
> > training and performance issue, primarily.  Team members who need to
report
> > their task progress every day need to be taught how to do it properly
and
> > then be held accountable for their performance.  Likewise with those who
> > report only only once every 1 to 2 weeks.
> >
> > Concerning the latter group, however, I would strongly recommend that
they
> > enter and save their progress every day in Project Server, and then
submit
> > their progress at the end of the reporting period.  If they enter their
> > numbers only on the last day of that reporting period for the entire two
> > weeks of work, I would think that their "actuals" would be more like
> > "guesstimates" recorded from a hazy memory.  Just a thought.  Hope this
> > helps.
> >
> > -- 
> > Dale A. Howard [MVP]
> > Enterprise Project Trainer/Consultant
> > Denver, Colorado
> > http://www.msprojectexperts.com
> > "We wrote the book on Project Server"
> >
> >
> > "OK" <OK@discussions.microsoft.com> wrote in message
> > news:BDAA7056-2901-4D51-89FC-B3CEB4E0B96F@microsoft.com...
> > > We have 2 departments. One wants to report every day, another - just
once
> > in 1 ot 2 weeks. Is it possible to manage it on 1 server?
> >
> >
> >
Quantcast