K
kas
I've been working as a contractor in support of Project Managers who are
going through the Project Server Learning Curve.
I've not had the opportunity yet to set up a plan from ground zero, but look
forward to being able to do this.
As I've been working with the plans, I am NOT confident that things are set
up correctly... weird things keep happening and the results don'[t make
sense... I can't explain
NOTE: We are having the infamous "Work continues to increase" situation
where team members enter time into PWA, PM updates into plan and the work
increases, and work that was previously 0 suddenly ressurrects with a value
greater than 0.
To be honest, I think it's making me look bad in the eyes of the client.
I would like to join al.ponds QUEST to determine if this is a process and
standards issue PMs are experiencing or a system related issues beyond our
control....OR..... maybe both!!! Whatever it is,,,,, let's identify what the
problem is and get a solution out there!!!
Time reporting is critical yadda yadda yadda.... I'll get off my soap box.
I would like to validate something that just does not look right to me...
The PWA Tracking Settings compared to the Entperprise Template Option
Settings in Project Professional.
Tracking Settings
Default method of reporting progress on tasks = Hours of work done per day
or per week: Resources reporting the hrs worked on each task during each
time period.
Lock down defaults = force project managers to use the progress reporting
method specified above for all projects.
Time period settings
Week starts on Monday(NOTE: In Professional Tools, Options, Calendar Tab,
it starts on Sunday.) What impact does this have?
Managed Periods - Allow only PWA users to update actuals during open period
Managed Timesheet Periods are defined
start..... finish..... status
((defined as Mon-Sun, except on last day of the month, whereby time is
reported regardless of the day it lands on. For example, August... time was
submitted and updated on 8/28 for period 8/21-8/27. Then last day of month
for August landed on Thursday; therefore time was submitted and updated for
period 8/28-8/31 on 9/1.
Resources should report their total hours worked during the entire time
period set up above.
Maximum number of hours that can be entered per day for a single task (enter
"0" for no limit): = 24
Define current tasks
for current tasks, include tasks that start up to 10 days from the current
date.
Now, in Project Professional.... Tools Options
Tools, Options:
Calculation Tab
Mode = automatic
calculate all open projects
Checked Updating task status updates resource status
Earned Value....
NAME OF PRoject Plan. Published
Default task Earned value method: % Complete
Baseline for Earned Value calculations: Baseline (last saved on Tues 6/27/06)
Checked Inserted Projects are calculated like summary tasks
Checked Actual costs are always calculated by MS Office Project
Default fixed costs accrual: Prorated
Tasks are critical if slack is less than or equal to 0 days
CALENDAR TAB
Week starts on Sunday***NOTE**** Week starts on Monday in PWA*****
Fiscal year starts in January
Default Start Time 8 a.m.
Default End Time 5 p.m.
Hours per day 8.00 in some plans
40 hours / week
20 days / month
also seen as
Start time 8 a.m.
end time 3 p.m.
hours per day 6.5 in other plans
hours / week 32
20 days/month
also seen as
start 8 a.m.
end 4 p.m.
hours per day 7
hours / week 35
20 days / month
NOTE: Three plans checked had different parameters on the Calendar tab;
however, all had Monday - Sunday work week.
While PWA is set up for Sunday - Monday.
All three plans had same parameters on Calculation tab.
Now on the Schedule TAB:
Showing Scheduling messages
show assignement units as a percentage
New tasks start on current date
Duration is entered in days
work is entered in hours
default task type is fixed work
autolink inserted or moved tasks
splitr in-progress tasks
tasks will always honor their contraint dates
show that tasks have estimated durations
I would surely appreciate some additional eyes on this. I'm not the most
technical person, and could use some technical insight. The Time periods
don't sound right.
I really enjoy the work I'm doing with Project Server 2003, and really would
like to stay on this assignment for awhile. But I've heard rumors the client
is thinking of pulling it..... ouch! They are not confident with the
reporting data, specifically project hours. Any suggestions on how I might
validate/quality assure the process and tool and convince the client
differently. I don't mind the work!
Any input from anyone will be greatly appreciated.
going through the Project Server Learning Curve.
I've not had the opportunity yet to set up a plan from ground zero, but look
forward to being able to do this.
As I've been working with the plans, I am NOT confident that things are set
up correctly... weird things keep happening and the results don'[t make
sense... I can't explain
NOTE: We are having the infamous "Work continues to increase" situation
where team members enter time into PWA, PM updates into plan and the work
increases, and work that was previously 0 suddenly ressurrects with a value
greater than 0.
To be honest, I think it's making me look bad in the eyes of the client.
I would like to join al.ponds QUEST to determine if this is a process and
standards issue PMs are experiencing or a system related issues beyond our
control....OR..... maybe both!!! Whatever it is,,,,, let's identify what the
problem is and get a solution out there!!!
Time reporting is critical yadda yadda yadda.... I'll get off my soap box.
I would like to validate something that just does not look right to me...
The PWA Tracking Settings compared to the Entperprise Template Option
Settings in Project Professional.
Tracking Settings
Default method of reporting progress on tasks = Hours of work done per day
or per week: Resources reporting the hrs worked on each task during each
time period.
Lock down defaults = force project managers to use the progress reporting
method specified above for all projects.
Time period settings
Week starts on Monday(NOTE: In Professional Tools, Options, Calendar Tab,
it starts on Sunday.) What impact does this have?
Managed Periods - Allow only PWA users to update actuals during open period
Managed Timesheet Periods are defined
start..... finish..... status
((defined as Mon-Sun, except on last day of the month, whereby time is
reported regardless of the day it lands on. For example, August... time was
submitted and updated on 8/28 for period 8/21-8/27. Then last day of month
for August landed on Thursday; therefore time was submitted and updated for
period 8/28-8/31 on 9/1.
Resources should report their total hours worked during the entire time
period set up above.
Maximum number of hours that can be entered per day for a single task (enter
"0" for no limit): = 24
Define current tasks
for current tasks, include tasks that start up to 10 days from the current
date.
Now, in Project Professional.... Tools Options
Tools, Options:
Calculation Tab
Mode = automatic
calculate all open projects
Checked Updating task status updates resource status
Earned Value....
NAME OF PRoject Plan. Published
Default task Earned value method: % Complete
Baseline for Earned Value calculations: Baseline (last saved on Tues 6/27/06)
Checked Inserted Projects are calculated like summary tasks
Checked Actual costs are always calculated by MS Office Project
Default fixed costs accrual: Prorated
Tasks are critical if slack is less than or equal to 0 days
CALENDAR TAB
Week starts on Sunday***NOTE**** Week starts on Monday in PWA*****
Fiscal year starts in January
Default Start Time 8 a.m.
Default End Time 5 p.m.
Hours per day 8.00 in some plans
40 hours / week
20 days / month
also seen as
Start time 8 a.m.
end time 3 p.m.
hours per day 6.5 in other plans
hours / week 32
20 days/month
also seen as
start 8 a.m.
end 4 p.m.
hours per day 7
hours / week 35
20 days / month
NOTE: Three plans checked had different parameters on the Calendar tab;
however, all had Monday - Sunday work week.
While PWA is set up for Sunday - Monday.
All three plans had same parameters on Calculation tab.
Now on the Schedule TAB:
Showing Scheduling messages
show assignement units as a percentage
New tasks start on current date
Duration is entered in days
work is entered in hours
default task type is fixed work
autolink inserted or moved tasks
splitr in-progress tasks
tasks will always honor their contraint dates
show that tasks have estimated durations
I would surely appreciate some additional eyes on this. I'm not the most
technical person, and could use some technical insight. The Time periods
don't sound right.
I really enjoy the work I'm doing with Project Server 2003, and really would
like to stay on this assignment for awhile. But I've heard rumors the client
is thinking of pulling it..... ouch! They are not confident with the
reporting data, specifically project hours. Any suggestions on how I might
validate/quality assure the process and tool and convince the client
differently. I don't mind the work!
Any input from anyone will be greatly appreciated.
