Project manager

Solo disponible en BuenasTareas
  • Páginas : 10 (2491 palabras )
  • Descarga(s) : 0
  • Publicado : 15 de noviembre de 2011
Leer documento completo
Vista previa del texto

Scope Management Plan Template
This Project Scope Management Plan Template is free for you to copy
and use on your project and within your organization. We hope that you find this
template useful and welcome your comments. Public distribution of this document
is only permitted from the Project Management Docs official website at:

Scope ManagementPlan

Company Name
Street Address
City, State Zip Code


Table of Contents
Introduction 3
Scope Management Approach 4
Roles and Responsibilities 4
Scope Definition 5
Project Scope Statement 6
Work Breakdown Structure 7
Scope Verification 8
Scope Control 8
Sponsor Acceptance 9


Scope Management is the collection of processes which ensure that the projectincludes 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 five step process; CollectRequirements, Define Scope, Create WBS, Verify Scope, and Control Scope.

1) 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 withmeeting 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.
2) Define Scope – this step is critical to project success as it requires thedevelopment of a detailed project/product description to include deliverables, assumptions, and constraints and establishes the framework within which project work must be performed.
3) Create WBS – this process breaks project deliverables down into progressively smaller and more manageable components which, at the lowest level, are called work packages. This hierarchical structure allows for moresimplicity in scheduling, costing, monitoring, and controlling the project.
4) Verify Scope – this is the process by which the project team receives a formalized acceptance of all deliverables with the sponsor and/or customer.
5) Control Scope – this is the process of monitoring/controlling the project/product scope as well as managing any changes in the scope baseline. Changes may benecessary to the project scope but it is imperative they are controlled and integrated in order to prevent scope creep.

The Scope Management Plan provides the scope framework for this project. This plan documents the scope management approach; roles and responsibilities as they pertain to project scope; scope definition; verification and control measures; scope change control; and the project’swork breakdown structure. Any project communication which pertains to the project’s scope should adhere to the Scope Management Plan.

This project is for designing, programming, and testing a new software product which will be used to track the company’s finances and improve various financial processes. This includes design of the software, all programming and coding, and testing/validation ofthe software. No external resources or outsourcing are anticipated for this project.

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
tracking img