As described in this book of section 5.3: Deliverable are unique and distinct. It means we can't list 2 deliverable the same. Right?
However, in Appendix E, we can found so many deliverable are the same, for example:
1.2.2, 1.3.2, 1.4.2 ... are all "Jacket"
1.2.3, 1.3.3, 1.4.3 ... are all "Piling"
...
It seems contradictory. Am I something misunderstanding? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Deliverable are allways unique and distinct. What you stated are activities for the oil and gas example inside the apendix E
...
1 reply by Chihui Wang
Sep 12, 2016 9:59 AM
Chihui Wang
...
Thanks for your answers. Appendix E is an example of WBS. According to my understanding, it should not contains activities. So do you mean it is not a good WBS example?
Deliverable are allways unique and distinct. What you stated are activities for the oil and gas example inside the apendix E
Thanks for your answers. Appendix E is an example of WBS. According to my understanding, it should not contains activities. So do you mean it is not a good WBS example? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
You are right. My mistake. Those are work packages.
...
1 reply by Chihui Wang
Sep 13, 2016 12:04 AM
Chihui Wang
...
I don't think it is a work package. The definition of work package of this book is: A deliverable or project work component at the lowest level of each branch of the work breakdown structure.
As it is not the lowest level, so it's not the work package.It is only a WBS element.
As WBS is deliverable oriented, whether all the WBS component should be deliverable? If so, work package should also be the deliverable, so it require unique too.
You are right. My mistake. Those are work packages.
I don't think it is a work package. The definition of work package of this book is: A deliverable or project work component at the lowest level of each branch of the work breakdown structure.
As it is not the lowest level, so it's not the work package.It is only a WBS element.
As WBS is deliverable oriented, whether all the WBS component should be deliverable? If so, work package should also be the deliverable, so it require unique too. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Because there is not an explicit explanation about the examples you can say each component is what you think it is (not what it is). That is because each WBS must be completed with the WBS dictionary. On the other side, this is a practice standard so you can create the WBS with the orientation that best fits in your initiative in the real world.
...
1 reply by Chihui Wang
Sep 13, 2016 10:22 AM
Chihui Wang
...
Thanks. "create the WBS with the orientation that best fits in your initiative in the real world", it is exactly my purpose. However, it's really hard to start with the theory, so I study the examples with the purpose to better understand the theory. But it make me more confuse :(
Because there is not an explicit explanation about the examples you can say each component is what you think it is (not what it is). That is because each WBS must be completed with the WBS dictionary. On the other side, this is a practice standard so you can create the WBS with the orientation that best fits in your initiative in the real world.
Thanks. "create the WBS with the orientation that best fits in your initiative in the real world", it is exactly my purpose. However, it's really hard to start with the theory, so I study the examples with the purpose to better understand the theory. But it make me more confuse :(
...
1 reply by Sergio Luis Conte
Sep 13, 2016 10:31 AM
Sergio Luis Conte
...
No problem. I understand your point. In fact, when you go to PMBOK and see the chapter 5 Project Scope Management, when you see all related to WBS, the confusion could be higher. If you ask me, what I never, never, never skipped to create in every project is the WBS dictionary. Like the project charter is a document that give the possibility to survive the project to me.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Sep 13, 2016 10:22 AM
Replying to Chihui Wang
...
Thanks. "create the WBS with the orientation that best fits in your initiative in the real world", it is exactly my purpose. However, it's really hard to start with the theory, so I study the examples with the purpose to better understand the theory. But it make me more confuse :(
No problem. I understand your point. In fact, when you go to PMBOK and see the chapter 5 Project Scope Management, when you see all related to WBS, the confusion could be higher. If you ask me, what I never, never, never skipped to create in every project is the WBS dictionary. Like the project charter is a document that give the possibility to survive the project to me.
...
1 reply by Chihui Wang
Sep 14, 2016 7:21 AM
Chihui Wang
...
Got it. I also study how to make the dictionary before.
No problem. I understand your point. In fact, when you go to PMBOK and see the chapter 5 Project Scope Management, when you see all related to WBS, the confusion could be higher. If you ask me, what I never, never, never skipped to create in every project is the WBS dictionary. Like the project charter is a document that give the possibility to survive the project to me.
Got it. I also study how to make the dictionary before. Saving Changes...
