I am kindly asking for your advice. Currently I am at the end of scope definition phase in my Project. I want to freeze all Scope documents in the form of Protocol.
My question would be: should this Protocol by signed by Business Owner Team only or maybe as well by any other role?
In this Project I am PM on customer side. So I manage the Business Team.
Regards,
Lukasz Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I will ask you to learn: what does mean "Scope documents in the form of Protocol"? I do not know what does mean. No matter that, to answer in more generic form, if you are in the customer side it does mean you are creating documents to sell project management and product creating to extermal company?
...
1 reply by Lukasz Pawelec
Nov 17, 2019 7:49 AM
Lukasz Pawelec
...
We have finished the project phase where the goal was to discuss requirements and respectively to assign solution. As the phase took a few weeks and the group of people were involved it is important to state what at the end becomes the Project Scope.
So it could be done in the form od document (protocol), which could include a group of other docs inbuilt if needed.
When I publish such document then the idea is:
a) to have project scope frozen/document
b) people who sign take responsibilty, so if needed they will check attachments once more
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Dear Lukasz
Interesting your question
Thanks for sharing
After reading what you have written you lead me to think that the development approach is predictive, ie any change in scope can only be made if:
- There is a change request
- If this change request is formally approved
In this situation it seems to me good that customer and supplier (which may be internal or external to the organization) sign the project scope documents (Scope Statement, WBS and WBS Dictionary)
...
2 replies by Lukasz Pawelec
Nov 17, 2019 7:52 AM
Lukasz Pawelec
...
You are right Luis, after the time Scope is stated then every change is processed as a Change Request
In my situation, it is as you say WBS docs are the main component of the protocol
I will ask you to learn: what does mean "Scope documents in the form of Protocol"? I do not know what does mean. No matter that, to answer in more generic form, if you are in the customer side it does mean you are creating documents to sell project management and product creating to extermal company?
We have finished the project phase where the goal was to discuss requirements and respectively to assign solution. As the phase took a few weeks and the group of people were involved it is important to state what at the end becomes the Project Scope.
So it could be done in the form od document (protocol), which could include a group of other docs inbuilt if needed.
When I publish such document then the idea is:
a) to have project scope frozen/document
b) people who sign take responsibilty, so if needed they will check attachments once more
...
1 reply by Sergio Luis Conte
Nov 17, 2019 8:23 AM
Sergio Luis Conte
...
Now I understood. Then, my comments. First: take into account that two types of scopes have to be taken into account: product scope and project scope. From product scope the project scope is defined. Bussiness Analyst is accountable for product scope, Project Manager is accountable for project scope. Second: you can not freeze anything in the project. Take a look to Barry Bohem´s Cone of Uncertainty and you will understand why. So, the only thing you can do, what I fully recommended, is to put clear the project change control process you will use and be aware that nothing can be feeze. Third:to request approval of all documents in your project you have to define a project governance process or, in other words, to define who will be on charge to approve each deliverable. Approval is an agreement about future changes will be evaluated through the project change control process.
Dear Lukasz
Interesting your question
Thanks for sharing
After reading what you have written you lead me to think that the development approach is predictive, ie any change in scope can only be made if:
- There is a change request
- If this change request is formally approved
In this situation it seems to me good that customer and supplier (which may be internal or external to the organization) sign the project scope documents (Scope Statement, WBS and WBS Dictionary)
You are right Luis, after the time Scope is stated then every change is processed as a Change Request
In my situation, it is as you say WBS docs are the main component of the protocol Saving Changes...
Dear Lukasz
Interesting your question
Thanks for sharing
After reading what you have written you lead me to think that the development approach is predictive, ie any change in scope can only be made if:
- There is a change request
- If this change request is formally approved
In this situation it seems to me good that customer and supplier (which may be internal or external to the organization) sign the project scope documents (Scope Statement, WBS and WBS Dictionary)
@Luis, do you think PM should sign as well? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Nov 17, 2019 7:49 AM
Replying to Lukasz Pawelec
...
We have finished the project phase where the goal was to discuss requirements and respectively to assign solution. As the phase took a few weeks and the group of people were involved it is important to state what at the end becomes the Project Scope.
So it could be done in the form od document (protocol), which could include a group of other docs inbuilt if needed.
When I publish such document then the idea is:
a) to have project scope frozen/document
b) people who sign take responsibilty, so if needed they will check attachments once more
Now I understood. Then, my comments. First: take into account that two types of scopes have to be taken into account: product scope and project scope. From product scope the project scope is defined. Bussiness Analyst is accountable for product scope, Project Manager is accountable for project scope. Second: you can not freeze anything in the project. Take a look to Barry Bohem´s Cone of Uncertainty and you will understand why. So, the only thing you can do, what I fully recommended, is to put clear the project change control process you will use and be aware that nothing can be feeze. Third:to request approval of all documents in your project you have to define a project governance process or, in other words, to define who will be on charge to approve each deliverable. Approval is an agreement about future changes will be evaluated through the project change control process. Saving Changes...
Make sure you have your assumptions listed about the requirements gathering process, one being that sign off constitutes a "freeze" on the scope (subject to change requests). Saving Changes...
Lonnie PacelliAuthor & President| ProjectManagementAdvisor.comBellevue, Wa, United States
The most important thing is to have all business areas represented that either directly or indirectly are impacted by your project sign off on scope. Saving Changes...
For us, the project sponsor (business owner) is responsible for developing the High Level Mandatory Requirements (HLMRs), and the Statement of Requirements (SOR). The PM is responsible for developing the Statement of Work (SOW) that includes the System Requirements Specifications (SRS or Technical Performance Requirements). A Requirements Traceability Matrix is a handy tool to ensure all technical performance requirements can be traced backed to the SOR and HLMR. A requirements management tool such as IBMs' DOORS will show traceability and show what was changed by who, and when. Saving Changes...
