Documenting Creeps into Project Scope

Hello,

We had developed a project plan for a software development project. After
moving into the development phase, our business owners decided to stop
development, re-visit and change some of the functionality of the tool.

My question is how do I represent the time spent on stopping, going back to
the design phase, re-developing some features, and then picking up where we
left off? At the end of the project, I will need to be able to show why we
missed our deadline, and why we're over budget.

Do I simply insert the new tasks at the point where we stopped to
re-evaluate? Or is there a better way to do this?

Thanks.

Rod
Fri Jan 28 14:59:13 CST 2005

I would insert a new summary task that is in itself a new mini project to
review the main project and decide go/no go. This is most realistic, so most
meaningfull and easy to understand. Halted tasks can be split into completed
and incomplete portions and linked to follow your new mini project summary
task.

--

Rod Gill
Project MVP


"T." <asdfasdf@adfasdf.com> wrote in message
news:O$luj5WBFHA.2640@TK2MSFTNGP14.phx.gbl...
> Hello,
>
> We had developed a project plan for a software development project. After
> moving into the development phase, our business owners decided to stop
> development, re-visit and change some of the functionality of the tool.
>
> My question is how do I represent the time spent on stopping, going back
> to the design phase, re-developing some features, and then picking up
> where we left off? At the end of the project, I will need to be able to
> show why we missed our deadline, and why we're over budget.
>
> Do I simply insert the new tasks at the point where we stopped to
> re-evaluate? Or is there a better way to do this?
>
> Thanks.
>