Cheikh FAYE Microsoft Dynamics 365 Business Expert, CEO and owner| Eurêka TechnologiesDakar, Senegal
For a project to be successfully achieved, it requires to be accomplished in time, within budget and specifications. What about specifications? What do they truly include? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Is not especification, is project scope. Project scope is all the work needed and the only needed to complete the product scope. Business analyst is accountable for product scope while Project manager is accountable from project scope. Project scope is defined from product scope. Specification is the document where project requirements are stated. Project requirements are a component of project scope.
...
2 replies by Ajifowoke Olakunle and Ravi Kishan Paliwal
Feb 15, 2019 12:06 PM
Ravi Kishan Paliwal
...
Thanks Serigo for clarity between product and Project scope owner.
"Triple Constraint’ , you can also say the Project Management Triangle or The Iron Triangle.
The key attributes of the Triple Constraint are Scope, Cost and Time.
Scope - Project scope deals with the specific requirements or tasks necessary to complete the project. Scope is important to manage on any project, because if you can’t control the scope of the project, you’re not likely to deliver it on time or under budget. When managing scope it’s critical that you prioritize your tasks, enabling you to plan and assign resources effectively.
Cost- The financial constraints of a project, It is also known as the project budget.
Time- The schedule for the project to reach completion.
You cannot change one of the constraints without affecting either one or both of the other constraints.
...
1 reply by Cheikh FAYE
Feb 18, 2019 6:40 AM
Cheikh FAYE
...
Very well said Shadav, project scope deals with the specific requirements necessary to complete the project. Thank you for sharing.
Yo mean cost, time and scope. These are the three main constraints. Scope means do whatever you really need to do for that specific project. It may have to do with the spec. of deliverables and products, however, it is a broader concept. Saving Changes...
Ravi Kishan PaliwalProject Manager - UKI| IBM India Pvt LtdNew Delhi, Delhi, India
Agree with fellow members, basically triple constraints (Scope, Time, Cost) needs to be maintained/balanced through out the project any changes in any of these will have major impact on Project. Saving Changes...
Ravi Kishan PaliwalProject Manager - UKI| IBM India Pvt LtdNew Delhi, Delhi, India
Feb 15, 2019 8:09 AM
Replying to Sergio Luis Conte
...
Is not especification, is project scope. Project scope is all the work needed and the only needed to complete the product scope. Business analyst is accountable for product scope while Project manager is accountable from project scope. Project scope is defined from product scope. Specification is the document where project requirements are stated. Project requirements are a component of project scope.
Thanks Serigo for clarity between product and Project scope owner.
I agree with my colleagues that scope is the correct term and will try to clarify the difference.
As Sergio points out, specifications are product level requirements. They can come in many forms including textual descriptions, drawings, data tables, and models. We typically use what is called a Specification Control Document (SCD), to provide requirements to suppliers for their products used in our projects.
The scope for a project is the boundaries for all of what is included. The scope of a given project may only include some of the specifications for a product or much more.
A project may use an existing SCD for a new product, in which case much of the specification development and documentation phase is outside the scope of the project. A project might include developing an SCD for a supplied product as well as integrating their deliverable into a larger scale product, in which case the specifications are only a part of the larger scope.
I will partially disagree with Shadav that you cannot change scope without changing other constraints, because really there is a 4th constraint: Quality. You can sometimes offset scope increases in one area (add new features) with decreases in other areas (cancel including non-essential features). This changes the qualities of the product, as does increasing volume while decreasing precision. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Feb 15, 2019 12:06 PM
Replying to Ravi Kishan Paliwal
...
Thanks Serigo for clarity between product and Project scope owner.
You are welcome. I hope it help you and others. Saving Changes...
Is not especification, is project scope. Project scope is all the work needed and the only needed to complete the product scope. Business analyst is accountable for product scope while Project manager is accountable from project scope. Project scope is defined from product scope. Specification is the document where project requirements are stated. Project requirements are a component of project scope.
This explains it all....... Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Specifications can have different meanings (in PMI standards and guides as well as in life), it is in my view rather a document that groups a specific type of artifacts: requirements specification, test specification, design specification, business procedure specification etc. - and yes, it is related to product scope in my experience.
Requirements are defined by stakeholders, e.g. a customer and elicited by the BA/PM during the 'collect requirements' process in PMBoK Guide.
The 'Define Scope' process then selects these requirement that will be implemented. Not all requirements found will be implemented, there will be contradicting requirements, inconsistencies and the sum of possible requirements might not be implementable with the given schedule and cost constraints. Hence I never saw a project that implemented all requirements.
In procurement this is represented by the RfP includung a SOW (statement of work), produced by the buyer, and the proposal by the seller.
Requirements are the wish of the sponsor organization or customer, the scope statement is what they are promised by the project manager. In Germany, we distinguish this wish/promise pair by Lastenheft / Pflichtenheft.
...
1 reply by Keith Novak
Feb 19, 2019 12:19 PM
Keith Novak
...
Thomas. In English the wish/promise pair are called Requirements and Objectives (R&O).
Requirement definitions include the terms "must" or "shall" and are not optional. Objectives include the term "should" and are desirable, but not absolutely necessary.
Saving Changes...
Mikel SteadmanPMO Leader| Development Dimensions InternationalTroy, Nh, United States
When I hear specifications, my head goes to Quality Control.
When I hear scope, my head goes to guardrails to meet the charter or business case, and ideally the strategy. Saving Changes...
