Scope Management is the collection of processes which ensure that the project includes all the work required to complete it while excluding all work which is not necessary to complete it. The Scope Management Plan details how the project scope will be defined, developed, and verified. It clearly defines who is responsible for managing the projects scope and acts as a guide for managing and controlling the scope. Project Scope Management follows a six-step process; Plan Scope, Collect Requirements, Define Scope, Create WBS, Verify Scope, and Control Scope. (In this assignment focus on three) Collect Requirements: This first step is the process by which we define and document the requirements needed to meet all project objectives. The foundation of this process is the project charter and stakeholder register. From these, the team can identify requirements, collectively discuss details associated with meeting each requirement, conduct interviews and follow-on discussion to clarify the requirements, and document the requirements in sufficient detail to measure them once the project begins the execution phase. This documentation also serves as an input to the next step in the process which is to define scope. Define Scope: This step is critical to project success as it requires the development of a detailed project/product description to include deliverables, assumptions, and constraints and establishes the framework within which project work must be performed. Create WBS: This process breaks project deliverables down into progressively smaller and more manageable components which, at the lowest level, are called work packages. SCOPE MANAGEMENT APPROACH: It is important that the approach to managing the projects scope be clearly defined and documented in detail. This section provides a summary of the Scope Management Plan in which it addresses the following: Who has authority and responsibility for scope management? How the scope is defined (i.e. Scope Statement, WBS, WBS Dictionary, Statement of Work, etc.) How the scope is measured and verified (i.e. Quality Checklists, Scope Baseline, Work Performance Measurements, etc.) The scope change process (who initiates, who authorizes, etc.) Who is responsible for accepting the final project deliverable and approves acceptance of project scope ROLES AND RESPONSIBILITIES: In order to successfully manage a projects scope, its important that all roles and responsibilities for scope management are clearly defined. This section defines the role of the Project Manager, Project Team, Stakeholders and other key persons who are involved in managing the scope of the project. It should state who is responsible for scope management and who is responsible for accepting the deliverables of the project as defined by the projects scope. Any other roles in scope management should also be stated in this section. SCOPE DEFINITION: The scope definition section details the process of developing a detailed description of the project and its deliverables. This can only be completed after the requirements have been identified and defined during the requirements definition process. This section should explain the process you followed to develop the detailed description of the project and its deliverables. If you used other documents such as the Project Charter, Preliminary Project Scope Statement or Requirements Documentation you should identify them, and all other documents used. You should tie the scope definition process back to the requirements definition as the projects scope answers the requirements for the project. PROJECT SCOPE STATEMENT: The project scope statement details the projects deliverables and the work necessary to create these deliverables. The Project Scope Statement should contain the following components: Product Scope Description describes what the project will accomplish Product Acceptance Criteria describes what requirements must be met in order for the project to be accepted as complete Project Deliverables detailed list of deliverables the project will result in Project Exclusions description of work that is not included in the project and outside of the scope Project Constraints lists limits on resources for time, money, manpower, or equipment (capital) Project Assumptions describes the list of assumptions the project team and stakeholders are working under to complete the project WORK BREAKDOWN STRUCTURE: (Already created in Excercise1, in this assignment include WBS dictionary) The Work Breakdown Structure (WBS) and Work Breakdown Structure Dictionary are key elements to effective scope management. This section should discuss how the project scope is to be subdivided into smaller deliverables in the WBS and WBS Dictionary and how these smaller components are managed during the life of the project. SPONSOR ACCEPTANCE: This section details the sponsors approval (date, sponsors name/title and signature and/or email documenting their approval). Create a Scope Management Plan based on the above information on thebiometric system .(20 marks)