Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

10 day max duration

6 replies [Last post]
Wed, 2010-03-03 18:08
Craig Adams
User offline. Last seen 12 years 23 weeks ago. Offline
Joined: 11 Oct 2006
Posts: 71
Groups: Accreditation Editors
Hello everyone,

I have read good practice is to have tasks no longer than 10 days. I have just started with an organisation who’s projects typically run 3 to 5 years.

Many of the existing programmes have tasks such as council approval for development applications taking 12 months to process. Should I be delving into these and splitting them into 10 day tasks or are external tasks OK to leave with such long durations?
Top

Replies

Thu, 2010-03-04 07:19
#1
Craig Adams
User offline. Last seen 12 years 23 weeks ago. Offline
Joined: 11 Oct 2006
Posts: 71
Groups: Accreditation Editors
Bo,Mike and Samer,

Thanks for your advice guys.

Fairly new to full time programming and appreciate this forum and hope I can answer a few questions in the future.

Craig
Top
Thu, 2010-03-04 05:41
#2
Bo Johnsen
User offline. Last seen 8 years 7 weeks ago. Offline
Joined: 28 Feb 2006
Posts: 119
Groups: Building Information Modelling, Civil Engineering
Hi Mike,

Correct, no vertical drop line for progress in MSP similar to the one in Powerproject.

And yes, buffer task, like in Powerproject is not available in MSP either, however, a hammock task (for the buffer period) based on your milestone for "Design Complete" and your milestone for "Construction Start" could just be made in MSP instead.

I guess some "following-up" on Powerproject for my part is needed. Haven’t used it for some months.


Best regards,

Bo
Top
Thu, 2010-03-04 05:09
#3
Mike Testro
User offline. Last seen 5 weeks 1 day ago. Offline
Joined: 14 Dec 2005
Posts: 4418
Groups: Building Information Modelling, Content Moderators, GPCCAR Editors
Hi Bo

I was refering to the vertical drop line for progress - not available on MSP.

And Asta Powerproject is the only software that allows conversion of a standard bar to a buffer bar.

Best regards

Mike Testro
Top
Thu, 2010-03-04 05:05
#4
Samer Zawaydeh
User offline. Last seen 5 years 8 weeks ago. Offline
Joined: 3 Aug 2008
Posts: 1664
Groups: Civil Engineering, Regional Representatives
Dear Craig,

The PMI standard and the AACE standard links the duration to the reporting cycle. The Work Package duration is 2-3 times the reporting cycle and the Activity Duration is equal or less than the reporting cycle duration.

With kind regards,

Samer
Top
Thu, 2010-03-04 04:57
#5
Bo Johnsen
User offline. Last seen 8 years 7 weeks ago. Offline
Joined: 28 Feb 2006
Posts: 119
Groups: Building Information Modelling, Civil Engineering
"...say Design Complete and another - some twelve months later - for start construction..." - That must definitely be a dream come true. Haven’t yet experienced that on any projects. Most of the times nowadays it is either fast-track projects (design and construction running parallel, design slightly ahead) or ultra-fast track where construction ends before the design is complete.

Anyway, good thing with the buffer, but the statement about not being possible in MSP is most probably not correct. MSP can easily be configured to show how much time is left of the buffer / hammock period dependent of the progress / status date / current date.

Best regards,

Bo
Top
Thu, 2010-03-04 04:06
#6
Mike Testro
User offline. Last seen 5 weeks 1 day ago. Offline
Joined: 14 Dec 2005
Posts: 4418
Groups: Building Information Modelling, Content Moderators, GPCCAR Editors
Hi Craig

It is good planning policy to limit the duration of tasks that the contractor has control of where resources can be allocated and progress recorded.

It is different for programme bars where the contractor has no control - such a development applications.

In such cases I use milestones at the start and finish of the space in my programme that this period fills and cover it with a buffer task.

So I would have a milestone for say Design Complete and another - some twelve months later - for start construction.

If necessary these can be held appart by a + Leadlag set to calendar days.

When the start milestone is 100% complete the progress timeline will track across the period showing how much time is left. (Its a shame you can’t do this in MSP)

I use this technique for things such as provisional sums and service connections.

Best regards

Mike Testro
Top