I read many article about Scope vs Requirement. Someone says Scope is superset of Requirement and others says viceversa. Now, I would like to put up this question to the best of Management World. Let me see, what's your opinion on this... Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Michelle's example shows how you can work from a set of needs, select a solution, then scope out the work to implement the work. This is a typical scenario from a pure business analysis point of view.
When you are working with an external client, you may be coming at it a different way. It is not unusual to start with a project scope, usually determined between the RFP and the proposal, followed by requirements elicitation and, finally, solution selection/development.
The project scope is really meant as a tool to decide whether something is in or out. In Michelle's example, part of the scope could have included; "Unicycles will not be considered." Saving Changes...
David BiegBusiness Analysis & Requirements Program Manager (Consultant)| Project Management InstitutePittsford, Vt, United States
As Sergio pointed out in his initial response, its important to recognize the difference between "project" scope and "product" scope. As defined in Business Analysis for Practitioners: A Practice Guide, project scope is the work performed to deliver a product, service or result with the specified features and functions. While product scope is the features and functions that characterize a product, service or result. Therefore the requirements describe the features and functions of the product for the project. The 2 go hand in hand! There is a direct relationship between the # of requirements and the product scope, hence more approved requirements = a larger product scope which in turn = a larger project scope. Saving Changes...
Ranmali KirindeProject Manager| Virtusa Pvt LtdColombo 09, Sri Lanka
I agree with Stéphane's view. The project scope defines the boundaries of the project. In a vendor / client situation it is important to clearly define what is part of the scope, and what is not.
As Sergio noted, the requirements are the features and functions of the solution / product that will be built. Not all of the requirements of a product will necessarily be part of the scope. The available budget can determine the features and functions to be included based on priority. The work that needs to be done to build those requirements will define the project scope. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Requirements are what the customer wants, scope is what he gets (if the PM delivers on promise).
Needs are what he wanted if he knew better (e.g. asked a BA).
Agree to the other explanations. Saving Changes...
Requirements are what the stakeholders need from a project to meet project objectives.
The scope could comprise all the requirements or a part of it as agreed by stakeholders to meet project objectives. The requirements not covered in the scope are out of scope. Saving Changes...
HENDRY CHARLES.AAdditional Chief Engineer| BANGALORE METRO RAIL CORPORATION LTDThillai Nagar,Managiri, Tamil Nadu, India
Very simple answer . Clear explanation Saving Changes...
Wade HarshmanScrum Master| GDITIndianapolis, In, United States
The difference is that requirements are automatically 80% waste when they're first defined, whereas the scope is initially all productive and gradually expands with waste.
(Let me exit now before someone punches me.) Saving Changes...
