Tracking two parter And the word "SHOULD"

[John Sitka]

Part 1.

So far the only definitative answer I can find concerning the difference
between

Default reporting method

A./ Actual work done and work remaining

vs.

B./ Hours of work done per day or per week.

1.) Gantt chart vs. Grid on the right hand side.
2.) B./ is compatable with Managed periods.

What other differences exist? I'm trying to learn of the role of protected
actuals, how they affect coping tasks,
Actual Start/ Actual Finish, status date etc.

Part2

Given A./ and B./ above

and using non managed periods

we are faced with setting
Resources should report their hours every day
Resources should report their total hours for a week
Resources should report their total hours worked during the entire time
perio set ip above

I can kind of imagine how this setting would interact with B./ as the Grid
may present itself with cells
by day/week/or period, how would it effect A./

And what is the meaning of the word "SHOULD" as in what if they don't how
long is a day? when is a day?
We are now multinational.

 

[Gary L. Chefetz \(MVP\)]

John:

It's a matter of what best fits your organization's requirements. Is weekly
estimation and entry accurate enough? Do you believe that there's a benefit
to daily collection? Have you asked your stakeholders these questions?

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-

 

[John Sitka]

Is weekly estimation and entry accurate enough?
A. NO

Do you believe that there's a benefit to daily collection?
A. YES after one day of trial we identified huge advantages.


To Start with I need direct confirmation that

Are all functionaly equivalent because they aren't definite.

Thanks


READ NO FURTHER UNLESS FOCUS ON THE ABOVE CAN BE ASSURED

long winded version.......

Real world is they want at least daily.

There are esentially 2X3 = 6 combinations,
each on of the 3 combination has a component of "SHOULD"

"SHOULD" is pretty vague.

Without additional understanding the only conclusion I can draw is,
they aren't defined.
So I first need someone to confirm that there are really only
2 functional options. The ones I listed below as A./ or B./,
I don't want to use %.work.

Put another way,

A confirmation that the other 3 settings containing the SHOULD modifier
are all capable of the same thing.

Then I need to know how the 2 (or 6) settings differ from each other
in terms of
handling incomplete tasks and the ensuing splits on a tracking update
handling tasks that started early
handling tasks that started late
handling of actuals booked against the above.

obviously not all the above need a novel
just a direct comment. So I can know where to look.

the above listed handlings may start from a discussion of this.
Thanks.

 

[Gary L. Chefetz \(MVP\)]

John:

Those three selections contribute to crafting different reporting solutions.
Based on your answers to my questions, you should select the first,
"Resources should report their hours every day." This causes the grid to
display and accept work in daily display/collection cells. Selecting
Resources should report their total hours worked for a week sets the grid to
accept work in weekly buckets while the third selection is used when you
want to collect time in non-weekly and non-daily time periods.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-

 

[John Sitka]

Woo Hoo,
Gary thanks,

Here are my settings.

Specify the default method for reporting progress on tasks
= Actual work done and work remaining: Resources report the actual work done
and the work remaining to be done on each task

Lock down defaults
= Force project managers to use the progress reporting method specified
above for all projects.

Time period settings
= Week starts on: Sunday

For projects that require resources to specify hours worked during each time
period, you can specify the default time periods that are displayed in
resources' timesheets.
Timesheets should span a period that is:
= Weekly

Number of weeks spanned: = 2

= Resources should report their hours worked every day

Maximum number of hours that can be entered per day for a single task (enter
'0' for no limit):
= 0

For current tasks, include tasks that start up to days from the current
date. 10


With this set up the only resource editable fields in "Tasks" at the moment
when set to Gantt Chart are...
Actual Work and Remaining Work available
In Timesheet view Act. Work are the rows that make up the grid. None of
these are editable.

The users are using Tasks / Gantt Chart view and entering Actuals in the
left hand table
The Gantt chart mis represents their tasks as it dosen't seem to show
splits.
I have not been able to get the left hand task table to publish start and
restart
I told them to make sure they sort by ID to get the proper order of
operations.

 

[John Sitka]

I have not been able to get the left hand task table to publish start and

restart

I meant Stop and Restart.

 

[Gary L. Chefetz \(MVP\)]

John:

With these settings, you should have the daily entry grid in the Timesheet
view. Keep in mind that projects created when the server had different
settings will continue to adhere to their prior settings until you republish
the assignments. In all cases where actual work has been posted to a task
assignment, the assignment tracking method will not change to reflect the
new settings and will continue track using the tracking method first
initiated.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-