A planned Task was to do 200+ tests. 70% completed. "Task" now s.

[E Michael Jakins]

I have a task on my Plan which was to do 200 tests over a 8 day period. 70%
have been completed, but time has run out and the task is being "closed" (The
tests are being added to latter work / section in the Project.) We want to
show the task as "stopped" but not 100% finished.

I have had this type of problem before where a task is stopped mid way
through planned work. It always seems to be wrong to mark it as 100%.
Particularly when as in this instance the time is still as in the original
period. Equally we I would not want to make this into 200 seperate tasks -
even then what would I do with the 60 which do not happen?

MS Project does not seem to have a way of properly reflecting this situation.

 

[Steve House [MVP]]

Show the duration that has been consumed with the tests that have been run
as the actual duration, set the remaining duration to zero. The task will
be marked 100% complete but remember that [% Complete] for all tasks ALWAYS
refers to duration, ie time spent, NOT the actual physical process. Project
has no way of knowing if that task was a sequence of 200 tests or 1 big test
and doesn't much care, all its concerned with is how long it takes and how
much it costs. Use the task notes feature to attach a note to the task
explaining that the tests were terminated short of the number originally
planned. If the duration is different from that originally budgeted for it,
the baseline you saved before beginning work (you did save a baseline,
right?) retains your original planned estimates for comparison purposes.

 

[Mike Glen]

You could then create a new task, set into the future, for the 60 tasks not
done. You won't lose track of them then.

Mike Glen
Project MVP

Show the duration that has been consumed with the tests that have
been run as the actual duration, set the remaining duration to zero. The
task will be marked 100% complete but remember that [% Complete]
for all tasks ALWAYS refers to duration, ie time spent, NOT the
actual physical process. Project has no way of knowing if that task
was a sequence of 200 tests or 1 big test and doesn't much care, all
its concerned with is how long it takes and how much it costs. Use
the task notes feature to attach a note to the task explaining that
the tests were terminated short of the number originally planned. If
the duration is different from that originally budgeted for it, the
baseline you saved before beginning work (you did save a baseline,
right?) retains your original planned estimates for comparison
purposes. --
Steve House [MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs

I have a task on my Plan which was to do 200 tests over a 8 day
period. 70%
have been completed, but time has run out and the task is being
"closed" (The
tests are being added to latter work / section in the Project.) We
want to
show the task as "stopped" but not 100% finished.

I have had this type of problem before where a task is stopped mid
way through planned work. It always seems to be wrong to mark it as
100%. Particularly when as in this instance the time is still as in
the original period. Equally we I would not want to make this into
200 seperate tasks -
even then what would I do with the 60 which do not happen?

MS Project does not seem to have a way of properly reflecting this
situation.