Extending project duration

[goye1]

Hi,

My project duration is 2 years and I need to extend it to 2,5 years. Is there a simple way I can extend my project and have all the task and sub task extended proportionally? I'm using MS Project 2010.

Thanks!

 

[JulieInMaine]

I don't believe that is possible without automation through code. However, the question I would ask before thinking about just extending everything is why has your project increased by 25%?

Have you lost resources? Then change assignment units for the resources or remove resource.

Has the scope of the project increased? Then add the new tasks and link as appropriate.

 

[goye1]

Thanks for your answer Julie. To make it short, we have 2 projects. A 2,5 years project that is the real duration and a 2 years project that we give to the contractors (because we know there will be delays and they will finish it in 2,5 year. If we give them the 2,5 years project they will take 3 years to finish it)
So I have the 2 years project ready and know I have to prepare the 2,5 years project.

Thanks.

 

[PDQBach]

This is *not* the way I would go about managing the project. C. Northcote Parkinson's first law of economics is is particularly germane here.

In fact, your approach is so unacceptable that Project (which allows you to do so much) doesn't have the built-in functionality to let you do that.

But, having said that, if you absolutely insist on doing it the wrong way, here's a piece of VBA

Sub pdqbach()
Dim tsk As Task
Dim tmpType

For Each tsk In ActiveProject.Tasks
If Not tsk Is Nothing Then
If Not tsk.Summary Then
tmpType = tsk.Type
tsk.Type = pjFixedUnits
tsk.Duration = tsk.Duration * 1.25
tsk.Type = tmpType
End if
End If
Next
End Sub

Note that if you have already entered some actual data (i.e., entered actual work, entered %Complete or entered %Work Complete) then the predecessor/successor relationships for those tasks are now "locked" for the start date and will not reschedule correctly.

I deny all knowledge of having provided this workaround for your situation.

 

[SkipVought]

goye1,

The GREAT thing about tools like MS Project, is that they are so flexible, you can do so many great things with ease.

The WORSE thing about tools like MS Project, is that they are so flexible, you can do so many REALLY REALLY BAD, STUPID things with EASE. Well, relative ease, using a VBA procedure like PDQBach has very reluctantly shared.

I would think VERY LONG about bastardizing your project.


Skip,

_{Just traded in my old subtlety...
for a NUANCE!}

 

[JulieInMaine]

Hello goye1,
You wrote:
Thanks for your answer Julie. To make it short, we have 2 projects. A 2,5 years project that is the real duration and a 2 years project that we give to the contractors (because we know there will be delays and they will finish it in 2,5 year. If we give them the 2,5 years project they will take 3 years to finish it)
So I have the 2 years project ready and know I have to prepare the 2,5 years project.

I understand your concern that the unexpected can occur in a project. However, rarely does the expected occur with such regularity that every task increases by 25%. You certainly can run the macro that PDQ kindly provided. As both PDQ and Skip have noted, this is not recommended.

My suggestion: based upon experience in managing similar projects and in working with this particular contractors, I'd extend the duration of tasks that you anticipate are likely to run long. I would however, still hold the contractor to the original dates -- or find another contractor. A 25% over run is not acceptable in my world.

As food for further thought -- is the 2 year overall duration truly achievable? Should you negotiate a more realistic duration that is somewhere between 2 years and 2.5 years?

I hope this helps.

Julie