One of the key basics is to develop a strategic programme with defined milestones that gives the PM targets to go for. The PM needs to have something useful to help him to complete the project on time. All planners must be aware of this and so aim to be useful to the PM.
A 2000 activity network with 3000 logic links is not useful and will mean that your programmes will not be used. The PM needs to know what in broad terms are the key elements to the works.
i think PBS should be between steps 4 & 5, to be able to define 6, 7.
ther is a difference, between WBS used in project management and that one used by P3. WBS is not a must, while PBS is a must. in fact, it’s an effective recommendation.
regards, Mohd
Member for
24 years 9 months
Member for24 years9 months
Submitted by Ernesto Puyana on Sat, 2002-03-16 05:43
I agree. Imposing a WBS on a small project is not always beneficial.
However, the thecnique of breaking down project scope into smaller elements for organization, control, estimating purposes is allways a good idea, even on the smallest project.
Thats what I meant when I ask for WBS development. What if we call it PBS (project breakdown structure), and ask again: what about PBS development?
Member for
23 years 8 months
Member for23 years9 months
Submitted by Daryl Walcroft on Fri, 2002-03-01 07:54
I agree with that, only use a WBS when the project warrants it. A half hearted attempt at introducing a WBS on a small project will result in increased cost and very little benefit. Use Primavera P3’s coding structure to categorize elements for filtering, layouts etc.
That said, a good WBS is invaluable for analysis of individual work elements and the discipline of WBS coding helps the definition of project scope.
In my brief of setting up project, I did not include WBS as a requirement although it can be used.
Reasoning behind this is that sometimes when small contractors try to set up WBS, it becomes a costly and cumbersome process. If a WBS dictionary is readily available it doesnt hurt to add it, otherwise stick to contract requirements which most of the time do not require a WBS.
Is this procedure intended to cover the prebid stage of estimating and scheduling, or the postbid stage, once the contract has been awarded. It seems to me there some aspects of both stages have been mixed together.
Member for
24 years 6 monthsRe: Basics on Project Setup
One of the key basics is to develop a strategic programme with defined milestones that gives the PM targets to go for. The PM needs to have something useful to help him to complete the project on time. All planners must be aware of this and so aim to be useful to the PM.
A 2000 activity network with 3000 logic links is not useful and will mean that your programmes will not be used. The PM needs to know what in broad terms are the key elements to the works.
Member for
24 years 3 monthsWBS & PBS
refering to the basic steps,
i think PBS should be between steps 4 & 5, to be able to define 6, 7.
ther is a difference, between WBS used in project management and that one used by P3. WBS is not a must, while PBS is a must. in fact, it’s an effective recommendation.
regards, Mohd
Member for
24 years 9 monthsRe: Basics on Project Setup
I agree. Imposing a WBS on a small project is not always beneficial.
However, the thecnique of breaking down project scope into smaller elements for organization, control, estimating purposes is allways a good idea, even on the smallest project.
Thats what I meant when I ask for WBS development. What if we call it PBS (project breakdown structure), and ask again: what about PBS development?
Member for
23 years 8 monthsRe: Basics on Project Setup
I agree with that, only use a WBS when the project warrants it. A half hearted attempt at introducing a WBS on a small project will result in increased cost and very little benefit. Use Primavera P3’s coding structure to categorize elements for filtering, layouts etc.
That said, a good WBS is invaluable for analysis of individual work elements and the discipline of WBS coding helps the definition of project scope.
Member for
24 years 8 monthsRe: Basics on Project Setup
In my brief of setting up project, I did not include WBS as a requirement although it can be used.
Reasoning behind this is that sometimes when small contractors try to set up WBS, it becomes a costly and cumbersome process. If a WBS dictionary is readily available it doesnt hurt to add it, otherwise stick to contract requirements which most of the time do not require a WBS.
Member for
24 years 6 monthsRe: Basics on Project Setup
WBS is critical.
There are a lot of planners using CBS instead of WBS without understanding the impact. A well prepared WBS makes life easier for everyone.
Member for
24 years 9 monthsRe: Basics on Project Setup
How about WBS development?
Member for
24 years 9 monthsRe: Basics on Project Setup
Is this procedure intended to cover the prebid stage of estimating and scheduling, or the postbid stage, once the contract has been awarded. It seems to me there some aspects of both stages have been mixed together.
How about WBS development?