I am looking for a white paper, which explains when to use activity codes rather than the wbs in Primavera.
I spoke to a collegue about the fact that often one wbs is created in P3 which actually comprises of multiple structures and therefore becomes a beast of a thing...
When executing a project, I often use multiple activity codes to present the schedule, depending on the situation, instead of using the wbs function.
In my view, a project can be broken down into a number of ways (structures), such as by geographical area, by system, by phase, by company, by workpackage etc.
So, I’m looking for some published pieces to confirm my views...
I spoke to a collegue about the fact that often one wbs is created in P3 which actually comprises of multiple structures and therefore becomes a beast of a thing...
When executing a project, I often use multiple activity codes to present the schedule, depending on the situation, instead of using the wbs function.
In my view, a project can be broken down into a number of ways (structures), such as by geographical area, by system, by phase, by company, by workpackage etc.
So, I’m looking for some published pieces to confirm my views...