B
Bill Cole
Does anyone use PWA for the team to submit status reports to their manager?
I have required status reports for my team for a couple years. We used to
have a Word template with certain fields
that gave me information on high level progress, including hours worked on
each task, estimated hours remaining and some
verbiage on overall progress, roadblocks, successes, etc. I also asked that
whenever I gave a resource a little non-project
assignment that they put it on their status report and not remove it until
it was done - this prevented these things from being
forgotten as the weeks went by.
Now that we have moved to Project Server and PWA for tracking the project, I
have all the info I need on hours applied and
hours remaining on the individual tasks, and we are using the Status Report
feature of PWA to give the verbal overview of the
individual's status.
The PWA status reporting seems inferior to our previous Word based method,
the status reports I am getting are briefer and less
informative. I have tried to figure out why and the main flaw seems to be
that you do not start with your status report from the
previous week - instead you start with a blank slate. Therefore engineers
don't start with their list of high level tasks and status from the previous
report and expand upon it. Also the ability to keep track of long term low
priority tasks by having it on your status report has been lost
(yes, I know PWA has a TODO list capability which may work for that).
I am interested in hearing if anyone else has used the Status Report or TODO
list capabilities of PWA and what you think of them.
If anyone has used the Status Report capabilities and knows of an easy way
to start with the report from the previous week instead of
a blank page, let me know.
Thanks,
Bill
I have required status reports for my team for a couple years. We used to
have a Word template with certain fields
that gave me information on high level progress, including hours worked on
each task, estimated hours remaining and some
verbiage on overall progress, roadblocks, successes, etc. I also asked that
whenever I gave a resource a little non-project
assignment that they put it on their status report and not remove it until
it was done - this prevented these things from being
forgotten as the weeks went by.
Now that we have moved to Project Server and PWA for tracking the project, I
have all the info I need on hours applied and
hours remaining on the individual tasks, and we are using the Status Report
feature of PWA to give the verbal overview of the
individual's status.
The PWA status reporting seems inferior to our previous Word based method,
the status reports I am getting are briefer and less
informative. I have tried to figure out why and the main flaw seems to be
that you do not start with your status report from the
previous week - instead you start with a blank slate. Therefore engineers
don't start with their list of high level tasks and status from the previous
report and expand upon it. Also the ability to keep track of long term low
priority tasks by having it on your status report has been lost
(yes, I know PWA has a TODO list capability which may work for that).
I am interested in hearing if anyone else has used the Status Report or TODO
list capabilities of PWA and what you think of them.
If anyone has used the Status Report capabilities and knows of an easy way
to start with the report from the previous week instead of
a blank page, let me know.
Thanks,
Bill