R
RichardG
Hi,
I have been experimenting with EV in a test project and come across an
issue and would like some advice.
I work for a company that produces hardware and based on past experiences we
allow a certain amount of time for several rounds of de-bugging and
re-testing. I normally have one task for each of the de-bugging phases when I
produce the initial schedule. When we get to the actual de-bugging phase and
the exact problems are known, I then break the task down into more details.
The problem is when I do this, there are no equivalent tasks in the
base-line. Is there any way for Project to handle this or do I have to create
a new base-line when ever I need to break tasks down in this way?
I have been experimenting with EV in a test project and come across an
issue and would like some advice.
I work for a company that produces hardware and based on past experiences we
allow a certain amount of time for several rounds of de-bugging and
re-testing. I normally have one task for each of the de-bugging phases when I
produce the initial schedule. When we get to the actual de-bugging phase and
the exact problems are known, I then break the task down into more details.
The problem is when I do this, there are no equivalent tasks in the
base-line. Is there any way for Project to handle this or do I have to create
a new base-line when ever I need to break tasks down in this way?