JimAksel
Thu Mar 13 23:02:01 CDT 2008
These can get tricky, and you have identified two common methods to handle
the problem.
1. Add a task loop for rework. This is the way we usually do it. The idea
is that if you run a test and the test fails, it is not the fault of the
tester. Blame lays with the development team, not the test team. So, we
only allow the developers to take 80% credit until test is passed, then both
test and development take 100%. The testers always get credit for running
the test, regardless of outcome. Sometimes they have to run "retest" other
times they do not.
2. Keep development open, along with test until passed. Sometimes we do it
that way.
Either way you present yourself with a dilema. First, you are admitting
quality is not what it should be if you have a retest/rework loop. That's a
political problem. To me, the real issue is if you have rework loops as part
of your baseline, you are adding time to the cycle that may not belong there.
From experience, we are learning how long it really takes to go through
test. In our case we have a long period of dry runs before formal test.
This is helping. So, the idea is to eventually get to a point where
sufficient time is allowed for test/rework so we don't show all this Level of
Effort type rework.
On the positive side, if you are able to pass a test first time through, and
you had rework time in the schedule, then everyone is happy. What's the
downside of that?
--
If this post was helpful, please consider rating it.
Jim
Visit
http://project.mvps.org/ for FAQs and more information
about Microsoft Project
"Jason" wrote:
> This is a general question on best pratices that I am just looking for some
> insight on.
>
> I am in the process of redoing several Project task lists/templates and I am
> coming across lots of approval, QC and rework loops. I am trying to
> determine the best way to handle these loops.
>
> So far my two choices are to insert a new task and call it rework. Or to
> just not allow the user to close the prior task but that seem to have
> problems too.
>
> What is the recomended way to do this? I am sure everyone runs across these.
> Open to thoughts and suggestions!
>
> Thanks
> Jason