1. Purpose of a Project Scope/ Baseline
Project Cost and Budget Management
Assignment 1: In- Class Lab
* One-page paper. * Summarize : 1. Purpose of a project scope/ baseline. 2. Reasons for project changes. 3. Options for managing change.
Defining project scope is the process of developing a detailed description of the project and product. The processes used to manage project scope, as well as the supporting tools and techniques, vary by application area and are usually defined as part of the project life cycle. The approved detailed project scope statement and its associated WBS and WBS dictionary are the scope baseline for the project. This baseline is then monitored, verified, and controlled throughout the lifecycle of the project. The purpose of project scope is to provide the project organization and the project manager with a road map of both the work to be completed, as well as the types of final deliverables sought. In some cases the scope document and the SOW are practically identical. For example, while the scope document may describe the end product or service to be produced and delivered by the project, it should not be treated as a document for technical specifications. Changes happen as a result of several reasons: As the result of initial planning errors- Because many projects involve significant technology risks and uncertainty, it is often impossible to accurately account for all potential problems or technological roadblocks. As a result, many projects require midcourse changes to specifications when they encounter unsolvable problems or unexpected difficulties. As a result of additional knowledge of project conditions- The project team or client may enter into a project, only to
Assignment 1: In- Class Lab
* One-page paper. * Summarize : 1. Purpose of a project scope/ baseline. 2. Reasons for project changes. 3. Options for managing change.
Defining project scope is the process of developing a detailed description of the project and product. The processes used to manage project scope, as well as the supporting tools and techniques, vary by application area and are usually defined as part of the project life cycle. The approved detailed project scope statement and its associated WBS and WBS dictionary are the scope baseline for the project. This baseline is then monitored, verified, and controlled throughout the lifecycle of the project. The purpose of project scope is to provide the project organization and the project manager with a road map of both the work to be completed, as well as the types of final deliverables sought. In some cases the scope document and the SOW are practically identical. For example, while the scope document may describe the end product or service to be produced and delivered by the project, it should not be treated as a document for technical specifications. Changes happen as a result of several reasons: As the result of initial planning errors- Because many projects involve significant technology risks and uncertainty, it is often impossible to accurately account for all potential problems or technological roadblocks. As a result, many projects require midcourse changes to specifications when they encounter unsolvable problems or unexpected difficulties. As a result of additional knowledge of project conditions- The project team or client may enter into a project, only to
References: Venkataraman, R & Pinto J., (2012). Cost and Value Management in projects. John Wiley and Sons, INC., Hoboken, NJ.