Purpose of a Project Scope/Baseline

Defining get word ground is the process of underdeveloped a detailed description of the go through and product. The processes used to manage jump out scope, as well as the supporting tools and techniques, vary by exertion atomic number 18a and atomic number 18 usually defined as part of the project life cycle. The approved detailed project scope statement and its associated west by south and WBS dictionary are the scope baseline for the project. This baseline is thus monitored, verified, and controlled throughout the lifecycle of the project.The purpose of project scope is to provide the project giving medication and the project manager with a road map of both the form to be completed, as well as the types of final deliverables sought. In whatever cases the scope document and the SOW are practically identical. For example, while the scope document whitethorn describe the end product or go to be produced and delivered by the project, it should non be treated as a documen t for technical specifications. Changes happen as a result of several(prenominal) reasonsAs the result of initial planning errors- Because many projects gather up portentous technology risks and uncertainty, it is often impossible to accurately account for all potence problems or technological roadblocks. As a result, many projects require midcourse channelizes to specifications when they come up unsolvable problems or unexpected difficulties. As a result of additive knowledge of project conditions- The project team or client may enter into a project, only to discover that specific project features or the development environment itself require midcourse changes to scope.Uncontrollable mandates- In some circumstances, events pass on outside the control of the project manager or team that mustiness be factored into the project as it moves forward. Client requests- As a projects clients learn more about the project, they often ask for profound alternations to address new needs. Also, reasons for changing the project may be light communication pressure/time constraints preventing effective definitive design contracts sign-language(a) when scope in not frozen changes from initial design ugly initial planning lack of project management tools and others.In straightforward terms, conformation management is the best understood as the Systematic counseling and Control of Project Change. The specific tasks of the contour management discipline are as follows * sort identification This process identifies all items uniquely at bottom the configuration, which establishes a successful method for requesting a change and ensures that no change takes place without authority.In addition, every configuration item should be physically labeled so that the label identifies that physical item as the adept recorded in the configuration register. In the case of large projects that involve numerous configuration items, it is important to establish a baseline configurati on to provide some structure and avoid confusion. * Configuration control This is a system through which changes may be made to configuration items.As change request begin to appear, the configuration control system ensures that no change is made without assessment of its impact, either by the people potentially affected by the change, or without approval by an appropriate authority. * Configuration status accounting- This process, which records and reports the current status and history of all changes to the configuration system, provides a complete record of what happened to the configuration system to date. * Configuration audit These audits are performed to ensure conformity between the items in the configuration and their specifications.Audits ensure not only a match between what is delivered and what was required, but also organic structure throughout all project documents. To avoid the cost and delays associated with uncontrolled changes, many organizations have set up for mal procedures to control them- and have but extended those procedures upstream to anticipate changes well before occur. Establishing a configuration control system provides such a framework for anticipating what may not be obvious.