Resource Task Completion

[Steve Budzynski]

When uploading a project a particular resource is able to state what
percentage of work is done on any task for that particular project.

My problem is that some tasks require work to be done by other resources
before that particular person may begin their task. For example: throw away
trash would have to happen before someone can take out trash, therefore the
predecessor to take out trash is throw away trash but the resource who is
supposed to take out the trash is able to say whether or not their task is
complete before resource has stated the trash has been thrown away.

Is there anyway I can "lock out" the ability to update tasks whos
predecessors have yet to be completed? I only want my employee to be able to
update a task once the predecessor has been completed.

Please let me know if my question is not very clear. I apologize in advance
if this is an easy fix but I am very very new to MS Project!

Thank you,

 

[Dale Howard [MVP]]

Steve --

One of the limitations of Project Server is that it will not prevent a
resource from working on a successor task until the work has been completed
on the predecessor task. Therefore, you should make this a training and
performance issue with your team members. Hope this helps.

 

[Steve Budzynski]

Dale --

Thank you for answering in such a timely fashion. This is bad news for me
since training some of our employees has not been the most successful
approach (cough cough boneheads cough cough).

To get around this problem, would you suggest only publishing tasks with
resources assigned in phases as the project completes so that they will not
see tasks assigned to them all at once?

Please offer your input on this idea!

Thank you again,

 

[John Sitka]

How can your resources accomplish effort on a task that has a true predessecor
if the predecessor isn't complete?

Your trash example.

Are you saying that the person dosen't see the brand new trash bag in the can and decide for themselves that there is no need to
take out the trash?

More likely those boneheads might be whispering to you that the logical model is broken.
OR
the process to prevent working with the wrong stuff
-versions
-too hot/too cold/not cured
- not customer approved
is non-existant

 

[Steve Budzynski]

Let me give a different example.

We have a PM in baltimore that has to order chairs from a manufacturer.
After the PM completes that task our sales person in Florida can notify their
customers that the chairs have been ordered. We do not want our salesperson
notifying the customers prematurely. Though proper training could fix this
problem we want to make sure they do not make this error simply by not being
able to update the task on server until it's predecessor has been fufilled.

When you stated:

the process to prevent working with the wrong stuff
-versions
-too hot/too cold/not cured
- not customer approved
is non-existant

Could you explain what you meant to me. I am sorry but I do not understand,
I am still very new to project.

Thank you for your help!

 

[Dale Howard [MVP]]

Steve --

I love your sense of humor, my friend! To get around the bonehead
problem, you could ask your PM's to only publish the assignments for only
one deliverable or phase at a time, but this makes the process more
demanding on the PM's. Hope this helps.

 

[Steve Budzynski]

Thank you Dave!

We are currently implementing this idea in one of our upcoming projects.
We'll see how it goes! Thanks for all your help!

Steve

 

[Dale Howard [MVP]]

Steve --

My name is Dale, but you can call me Dave if you wish!

 

[Steve Budzynski]

haha llook like the pot was calling the kettle black

im very sorry dale!

thank you again,

--Steve aka bonehead