ScopeManagementPlan.docx

1、ScopeManagementPlanScope-Management-PlanScope Management Plan TemplateThis Project Scope Management Plan Template is free for you to copyand use on your project and within your organization. We hope that you find thistemplate useful and welcome your comments. Public distribution of this documentis o

2、nly permitted from the Project Management Docs official website at: Management PlanCompany NameStreet AddressCity, State Zip CodeDateTable of ContentsIntroductionScope Management is the collection of processes which ensure that the project includes all the work required to complete it while excludin

3、g 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 Managemen

4、t follows a five step process; Collect Requirements, 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 c

5、harter 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

6、 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 the development of a detailed project/product description to include deliverables, assumptio

7、ns, 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

8、for more simplicity 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 pr

9、oject/product scope as well as managing any changes in the scope baseline. Changes may be necessary 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 document

10、s the scope management approach; roles and responsibilities as they pertain to project scope; scope definition; verification and control measures; scope change control; and the projects work breakdown structure. Any project communication which pertains to the projects scope should adhere to the Scop

11、e Management Plan. This project is for designing, programming, and testing a new software product which will be used to track the companys finances and improve various financial processes. This includes design of the software, all programming and coding, and testing/validation of the software. No ex

12、ternal resources or outsourcing are anticipated for this project.Scope Management ApproachIt 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: Wh

13、o has authority and responsibility for scope management How the scope is defined . Scope Statement, WBS, WBS Dictionary, Statement of Work, etc.) How the scope is measured and verified . Quality Checklists, Scope Baseline, Work Performance Measurements, etc.) The scope change process (who initiates,

14、 who authorizes, etc.) Who is responsible for accepting the final project deliverable and approves acceptance of project scopeFor this project, scope management will be the sole responsibility of the Project Manager. The scope for this project is defined by the Scope Statement, Work Breakdown Struct

15、ure (WBS) and WBS Dictionary. The Project Manager, Sponsor and Stakeholders will establish and approve documentation for measuring project scope which includes deliverable quality checklists and work performance measurements. Proposed scope changes may be initiated by the Project Manager, Stakeholde

16、rs or any member of the project team. All change requests will be submitted to the Project Manager who will then evaluate the requested scope change. Upon acceptance of the scope change request the Project Manager will submit the scope change request to the Change Control Board and Project Sponsor f

17、or acceptance. Upon approval of scope changes by the Change Control Board and Project Sponsor the Project Manager will update all project documents and communicate the scope change to all stakeholders. Based on feedback and input from the Project Manager and Stakeholders, the Project Sponsor is resp

18、onsible for the acceptance of the final project deliverables and project scope.Roles and ResponsibilitiesIn 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,

19、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 s

20、hould also be stated in this section.The Project Manager, Sponsor and team will all play key roles in managing the scope of this project. As such, the project sponsor, manager, and team members must be aware of their responsibilities in order to ensure that work performed on the project is within th

21、e established scope throughout the entire duration of the project. The table below defines the roles and responsibilities for the scope management of this project. NameRoleResponsibilitiesJohn DoeSponsor-Approve or deny scope change requests as appropriate-Evaluate need for scope change requests-Acc

22、ept project deliverablesJane DoeProject Manager-Measure and verify project scope-Facilitate scope change requests-Facilitate impact assessments of scope change requests-Organize and facilitate scheduled change control meetings-Communicate outcomes of scope change requests-Update project documents up

23、on approval of all scope changesBob JonesTeam Lead-Measure and verify project scope-Validate scope change requests-Participate in impact assessments of scope change requests-Communicate outcomes of scope change requests to team-Facilitate team level change review processJohn SmithTeam Member-Partici

24、pate in defining change resolutions-Evaluate the need for scope changes and communicate them to the project manager as necessaryTom BrownTeam Member-Participate in defining change resolutions-Evaluate the need for scope changes and communicate them to the project manager as necessaryTable , Scope Ma

25、nagement Roles and ResponsibilitiesScope DefinitionThe 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.

26、 During the requirements definition process three documents were created; Requirements Documentation, Requirements Management Plan and a Requirements Traceability Matrix. You can refer to these documents when defining the projects scope.This section should explain the process you followed to develop

27、 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 req

28、uirements definition as the projects scope answers the requirements for the project.You should also document the tools and techniques used to define the project scope such as expert judgment, product analysis, alternatives identification or facilitated workshops.The scope for this project was define

29、d through a comprehensive requirements collection process. First, a thorough analysis was performed on the companys current software applications based on employee and user feedback. From this information, the project team developed the project requirements documentation, the requirements management

30、 plan, and the requirements traceability matrix for what the new software application must accomplish. The project description and deliverables were developed based on the requirements collection process and input from subject matter experts in software design, technical support, programming and bus

31、iness applications. This process of expert judgment provided feedback on the most effective ways to meet the original requirements of providing a new software platform from which the company can improve its financial tracking and internal financial processes.Project Scope StatementThe project scope

32、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 th