Canceling Tasks

[scottsoo9]

I have some tasks in my project that have been cancelled. I want t
continue to show the task but was wondering if there was a way t
actually have a line go through that task to show it is no longer neede
and was cancelled. Right now, I have the task and just put a note tha
the task was deleted or cancelled and have it at 100% complete. I kno
this is probably not the best way. Is there a better way to go abou
this? I appreciate all the help I have already recieved from all m
questions. (Rob Schneider in paticular) Thanks, Scot

 

[Rob Schneider]

I'd keep it simple. Put an entry into the project change log about the
change in scope. Then delete the task(s) from the project plan--and fix
any logic changes that this requires.

I wouldn't show them as complete because they are not. They simply
reduced the scope of the project. Removing from the Project MPP file
will of course change the computed cost, total hours, change
assignments, and perhaps even changed the computed end date--but that's
the true aspect of the change.

--rms

www.rmschneider.com

 

[Jim Aksel]

This feature will be available in P2010. For now, you can set the remaining
work to 0 and mark the task 100% complete. Change the font as you desire.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com

 

[Rob Schneider]

Jim,

Your post made me remember the possibility that the tasks were already
partially done. I like you approach in that case.

--rms

www.rmschneider.com

 

[Jim Aksel]

Thanks Rob. I've been bit with this one. Also, before a task begins
work=remaining work so in either case setting remaining work to 0 does the
trick.

One other thought, if the task is truly obsolete, then we also need to
remember to steer the schedule logic around the task. Another approach is to
also set remaining duration to 0 as well. However, doing so changes the task
to a milestone (where as it used to be a "real" duration task) which can be
confusing.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com

 

[Rob Schneider]

Yes, that's why I would go to the effort of deleting the task (unless
work alredy started) as it will almost always have an affect on plan.
If there was no affect, then why bother not doing the task?

--rms

www.rmschneider.com

 

[Jan De Messemaeker]

Hi,

I'm fully with you... but you can check out "Mark task as Milestone" which
solves the final dilemma.

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[Jim Aksel]

Exercise cautin when deleting tasks with a baseline. You need to unbaseline
them first otherwise there is no way to get them out.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com

 

[Jack Dahlgren MVP]

This is the best way as it does not affect any actual work or baseline
information.
Rob's suggestion to put a note about it in the project log is also good.

-Jack

 

[Michael.Tarnowski]

Hi folks,
with much interest I follow this thread. Jack wrote

This is the best way as it does not affect any actual work or baseline
information.

Jack, which posting do you mean?

Cheers Michael