Why is project statement of work missing as an input to process “Develop Project Charter” in Pmbok Guide v6?
Helmut SchneiderFounder and Owner| C.P.S. Consulting& ProjektmanagementLangweid, Germany
In Version 5 of Pmbok Guide there were 3 main inputs: Project SOW (to be provided by the REQUESTING organization), the business case and agreements.
In version 6 of he Guide the (project) SOW seems to be sorted out. In the glossary there is only the link to the procurement SOW. But these are two complete different things.
Where do I find the formal description what the requesting organization needs, incl. their business needs and success criteria?
KR Helmut Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
You will find references to SOW in several places into PMBOK. Perhaps the description that could help is inside 12.1.3.3 BID DOCUMENTS. But if you are talking about a detail description on the contents of SOW you will not find it inside the PMBOK. The proposed content could be inphere from some paragraph of session 12. Something that helped me is this: http://everyspec.com/MIL-HDBK/MIL-HDBK-020...HDBK-245D_1888/
...
1 reply by Helmut Schneider
Sep 21, 2018 9:42 AM
Helmut Schneider
...
Thank you Luis,
the references to the PROCUREMENT SOW (to be created by the PM) and it's content in chapter 12 of the guide are clear. But my question was why the PROJECT SOW (to be created by the customer/performing organization) was sorted out as input the process "Develop Project Charter".
Business Case is a better term for what is needed as an input to the project charter. SOW was always a bit fuzzy for me. Saving Changes...
Helmut SchneiderFounder and Owner| C.P.S. Consulting& ProjektmanagementLangweid, Germany
Thank you Kiron,
The SOW is needed to describe/calculate the BC. The SOW comes from the requesting organization. The BC is developed by the performing organization. SO if you say the SOW is somehow part of the BC, as it is needed as an input, I would agree. But why does PMI not state this?
When you come from V5 of the guide to V6 it is first of all a bit misleading.... Saving Changes...
Helmut SchneiderFounder and Owner| C.P.S. Consulting& ProjektmanagementLangweid, Germany
Sep 21, 2018 5:21 AM
Replying to Sergio Luis Conte
...
You will find references to SOW in several places into PMBOK. Perhaps the description that could help is inside 12.1.3.3 BID DOCUMENTS. But if you are talking about a detail description on the contents of SOW you will not find it inside the PMBOK. The proposed content could be inphere from some paragraph of session 12. Something that helped me is this: http://everyspec.com/MIL-HDBK/MIL-HDBK-020...HDBK-245D_1888/
Thank you Luis,
the references to the PROCUREMENT SOW (to be created by the PM) and it's content in chapter 12 of the guide are clear. But my question was why the PROJECT SOW (to be created by the customer/performing organization) was sorted out as input the process "Develop Project Charter". Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The key is in page 30 figure 1-8 inside Pre-project. I was part of the group of authors and revieiwers and I worked on the integration of key roles inside all the related guides: business analysit and project/program/portfolio manager. Pre-project activities are performed by business analyst to understand the business problem and to create posible solutions. That is the "needs assessment" activity. Solution is equal "the thing" to be created plus "the process" to create it. Project requirements must be defined from solution requirements. So, all you need to know to define project requirements is inside the busines case. Project SOW is not needed, Just in case as the decided approach (that must be defined as an output of "needs assessment" too) organization decide to buy something then one of the project activities (because it is a solution requirement) could be to create a procurement statement of work.
...
1 reply by Helmut Schneider
Sep 21, 2018 11:35 AM
Helmut Schneider
...
Hi Sergio, thank you for your detailed answer. Now the way of thinking is clear. I just assumed this but is was not 100% transparent for me. I was just confused as the Project SOW was described in V5 explicitly and in V6 it is not mentioned anymore.
This answers my question!
Saving Changes...
Helmut SchneiderFounder and Owner| C.P.S. Consulting& ProjektmanagementLangweid, Germany
Sep 21, 2018 11:10 AM
Replying to Sergio Luis Conte
...
The key is in page 30 figure 1-8 inside Pre-project. I was part of the group of authors and revieiwers and I worked on the integration of key roles inside all the related guides: business analysit and project/program/portfolio manager. Pre-project activities are performed by business analyst to understand the business problem and to create posible solutions. That is the "needs assessment" activity. Solution is equal "the thing" to be created plus "the process" to create it. Project requirements must be defined from solution requirements. So, all you need to know to define project requirements is inside the busines case. Project SOW is not needed, Just in case as the decided approach (that must be defined as an output of "needs assessment" too) organization decide to buy something then one of the project activities (because it is a solution requirement) could be to create a procurement statement of work.
Hi Sergio, thank you for your detailed answer. Now the way of thinking is clear. I just assumed this but is was not 100% transparent for me. I was just confused as the Project SOW was described in V5 explicitly and in V6 it is not mentioned anymore.
This answers my question!
...
1 reply by Sergio Luis Conte
Sep 22, 2018 5:39 AM
Sergio Luis Conte
...
Good to read it has helped you. I agree with you that it is not clear. The guide that could help to understand how both roles (business analyst and project manager) interacts is the "Business Analysis Practitioners Guide" reading inside the guide the topic "collaboration point". I have proposed to the PMI to deliver a document explaining the work done to integrate both roles through all related guides but it was not accpeted. As you know, in this type of initiatives you work as volunteer but there is a standards committee composed by PMI people that take the decisions.
Saving Changes...
Helmut SchneiderFounder and Owner| C.P.S. Consulting& ProjektmanagementLangweid, Germany
Thank you all for your help and replies.... Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Sep 21, 2018 11:35 AM
Replying to Helmut Schneider
...
Hi Sergio, thank you for your detailed answer. Now the way of thinking is clear. I just assumed this but is was not 100% transparent for me. I was just confused as the Project SOW was described in V5 explicitly and in V6 it is not mentioned anymore.
This answers my question!
Good to read it has helped you. I agree with you that it is not clear. The guide that could help to understand how both roles (business analyst and project manager) interacts is the "Business Analysis Practitioners Guide" reading inside the guide the topic "collaboration point". I have proposed to the PMI to deliver a document explaining the work done to integrate both roles through all related guides but it was not accpeted. As you know, in this type of initiatives you work as volunteer but there is a standards committee composed by PMI people that take the decisions. Saving Changes...
"Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
