Project Management

Please login or join to subscribe to this thread

Construction scheduling

linkedin twitter facebook   Construction   Procurement Management   Scheduling   Work Breakdown Structures (WBS)  
avatar
Kristian Soini Australia
G'day project managers

I'm starting my fourth project now and have some questions on scheduling using MS Project.

How much detail is enough? My schedule is about 100 lines, which is about the most I can comfortably read when printed on A3 size paper.

Also, would it be better to group items by
a)
design
-item A
-item B
procurement
-item A
-item B
manufacturing
site install

or rather
b)
Item A
-design
-procurement
-manufacturing
-site install

I am sure the answer is "it depends" but what would your choice be and why?
Sort By:
< 1 2 3 >
avatar
Allan Laranang Electrical Designer| WSP Canada Winnipeg, Manitoba, Canada
Definitely Option B and breakdown each group to detailed task in order of scope/task priority.
avatar
Eric Simms Senior Program Manager Baltimore, Maryland, United States
Question: "How much detail is enough?"
Answer: As much as you need to feel you have complete control over every aspect of your project. You're the one responsible for its outcome, after all.
avatar
Daire Guiney Dublin, Dublin, Ireland
Some people require different levels of detail to complete their assigned task so you need to find a happy medium that provide sufficient detail but is not overly elaborate and busy with information. A Project Manager role is not to have complete control over every aspect of the project but to have confidence in those that he or she manages to complete their assigned task according to the level of standard and quality that the project management team has agreed to adhere to. Each member of the project team is responsible for the outcome of the assigned task, after all its adults your managing not children.
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
Once I have my work and activities broken down to less than the status reporting period (weekly, every second week, monthly, ...), I stop.There is little additional project management value to go further.

Having said that, your team leader may want to decompose further to make it easier to manage the work.
avatar
Mark Bilyeu Project manager | Edward J. Rice Co. Mo, United States
I would use B. It is the netter method to keep the two deliverables A & B separate. many of my projects are orders for two identical machines in a single order. they rarely have the same schedule due to competing resources, so in effect they are two sub-projects and need to be managed as two parts of the whole.
While I agree with the other responses regarding using PMBOK standards and the recently published Practice Standard for WBS, they are guidelines not set in stone rules. Use them to tailor your specific method to ensure you have a solid schedule based on a WBS that covers all needed deliverables to effectively capture the scope of your project. Hope this helps and doesn't sound to preachy.
avatar
Kimberly McCoy Project Manager| TekSystems - Contractor Zanesville, Oh, United States
So when you are adding details into MS Project, it will really depend on two things.
1. Do you have enough information to continue your PM duties throughout the project?
2. Does it provide enough information for your team to understand what needs to be done, and the information they need to complete their tasks/jobs

The amount of lines normally does not matter to me, as I am currently working on a plan that has over 1000 lines within the plan, just because of how big it is and complex the project is. Now this is for a task listing.

In my personal opinion, I would choose your first option for grouping because 1, it is pretty easy to see the milestones you are probably creating. From my project experiences, we go through the design phase for multiple pieces first before we can move to the next phase, especially when all the pieces are interconnected. If you happen to need to complete Item A before Item B can begin, then I would suggest grouping by your second option. So here is where the depends comes in. :)

In regards to the grouping, my methodology is that you want to complete a phase/stage prior to moving to the next. I understand this is not always possible, but the best way to be able to close something out prior to moving on, helps me to ensure nothing in that phase was missed.

Hope this helps!
avatar
Vincent Guerard Coach - Trainer - Speaker - Advisor| Freelance Mont-Royal, Quebec, Canada
One thing, I suggest is no task should be bigger than a reporting period.

How the WBS is presented is up to you or what is better for the project leader.
avatar
Vladimir Liberzon R&D Director| Spider Project Team Moscow, Russian Federation
We use multiple WBS and so the question on the best WBS just does not exist.
Typical construction project consists of many thousands activities.
Small number may permit to control if contract requirements are met but is not sufficient for proper management and reporting.
avatar
MONICA TREJO Monterrey, Nuevo Leon, Mexico
as someone mentioned above, the more detail the better, so that way you will not lose visibility or see where the bottleneck is (if applicable).
avatar
Ruth Marina Lopez Perez Responsable TI| INSTITUTO DE PREVISION SOCIAL MILITAR - NICARAGUA Masaya, Los Madrigales, NindirĂ­, Nicaragua
I vote for option A. However, all depend of the WBS. A good WBS built will offer you a good schedule. Then, you can control the schedule and budget and obtain Earned Valued and other keys with MSProject.
You must include at members of team of the project for obtain a good WBS with levels enough and measurables.
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"A noble spirit enbiggens the smallest man"

- Jebediah Springfield

ADVERTISEMENT

Sponsors