Q1. The PMBOK Guide addresses four elements related to scope. List and explain them
The scope is the most important element to understand about any project. All planning andallocation of resources are anchored to this understanding. Scope creep is a significant risk insoftware development projects. We discuss why this is so, and how to avoid or at least mitigatethe risk. New software is usually developed as a result of a customer identifying a need. Thenext step is to specify how the software will meet that need; specifically, what functionality willbe developed. The scope and budget are set, the team knows what they're delivering, andeveryone is ready to begin. The Project Management Institute Project Management Body of Knowledge (PMBOK) defines product scope as the features and functions that are to beincluded in a product or service. It defines project scope as the work that must be done todeliver a product with the specified features and functions. Project scope management isdefined as the processes required to ensure that the project includes all the work required, andonly the work required, to complete the project successfully. The PMBOK Guide addresses four elements related to scope:Scope: Scope is the summation of all deliverables required as part of the project. This includesall products, services and results. Project Scope:
This is the work that must be completed to achieve the final scope of the project, namely theproducts, services and end results. Scope Statement:
This is a document that provides the basis for making future decisions such as scope changes.The intended use of the document is to make sure that all stakeholders have a commonknowledge of the project scope. Included in the document are the objectives, description of thedeliverables, end result or project, and justification of the project. The scope statementaddresses seven questions who, what, when, why, where, how and how money. This documentvalidates the project scope against the statement of work provided by the customer. Statement of Work:
The statement of work (SOW) is a narrative description of the work required for the project.The complexity of the SOW is determined by the desires of top management, the customer,and / or user groups. A statement of work describes the actual work that is going to beperformed on the project which, when combined with specifications, usually from the basis fora contractual agreement on the project. As a derivative of the WBS, the statement of work(sometimes called scope of work) describes what is going to be accomplished, a description of the tasks, and the deliverable end products that will be produced, such as hardware, software,tests, documentation and training. The statement of work also includes reference tospecifications, directives or standards, that is, the guidance to be followed in the project work.The statement of work includes input required from other tasks involving the project and a keyelement of the customer „s request for proposal there can be misinterpretation of thestatement of work which can affect the results of the project adversary.
Common causes of misinterpretation are:
* Mixing tasks, specifications, approvals, and special instructions. * Using imprecise language (“nearly, “optimum”, “approximately” etc.”). * No pattern, structure or chorological order.
* Wide variation in size of tasks.
* Wide variation in how to describe details of the work.
Failing to get third party review.Misinterpretations of the statement of work can and will occur no matter, how careful everyonehas been, the result is creeping scope. Which is likely to upset costs and schedules? The bestway to control creeping scope is with a good definition of requirements up front. Integration:
The project control process is built on the concepts of integrating data related to scope,performing organization, and cost and of producing performance metrics by assimilating andevaluating all...
Please join StudyMode to read the full document