The document discusses the importance of properly defining a project's scope through a written scope statement. It states that the first task for a project manager is to develop a scope statement that forms the basis of agreement between parties, will be used to determine if the project is complete, and will be the basis for project decisions. It also explains that the scope statement identifies deliverables and objectives, and that the project manager must understand the project before writing the statement by reviewing documents and clarifying responsibilities.
The document discusses the importance of properly defining a project's scope through a written scope statement. It states that the first task for a project manager is to develop a scope statement that forms the basis of agreement between parties, will be used to determine if the project is complete, and will be the basis for project decisions. It also explains that the scope statement identifies deliverables and objectives, and that the project manager must understand the project before writing the statement by reviewing documents and clarifying responsibilities.
The document discusses the importance of properly defining a project's scope through a written scope statement. It states that the first task for a project manager is to develop a scope statement that forms the basis of agreement between parties, will be used to determine if the project is complete, and will be the basis for project decisions. It also explains that the scope statement identifies deliverables and objectives, and that the project manager must understand the project before writing the statement by reviewing documents and clarifying responsibilities.
success of any project, especially in terms of time and money. The first tasks of any project manager is to develop a written scope statement.
The scope statement:
• forms the basis for agreement between customer and supplier • will be the basis for all project related decisions • will be used to determine whether the project has been completed.
V. C. DATEY PROJECT SCOPE MANAGEMENT 1
PROJECT SCOPE IDENTIFICATION The written scope statement identifies both the project deliverables and project objectives and provides a basis for confirming or developing common understanding among the stakeholders. The project manager must have a clear understanding of the project before writing the scope statement. • He will have reviewed the contract. He will have understood the project assignment given to him by the project sponsor He will have clarified and documented the responsibilities between customer and supplier He will have identified any constraints and work that is specifically excluded from the scope. He will have had discussions with the sponsor, the customer and other major stakeholders. He will have had meetings with the sales and negotiation teams.
V. C. DATEY PROJECT SCOPE MANAGEMENT 2
PROJECT SCOPE IDENTIFICATION Scope definition involves subdividing the project deliverables into smaller components. The smaller components can also be subdivided into even smaller groups of self contained work tasks. Breaking up of the project deliverables into smaller easier to manage components is called a ‘Work Breakdown Structure’. Work breakdown structure (W.B.S.) Is a deliverable oriented grouping of project elements that organises and defines the total scope of the project
V. C. DATEY PROJECT SCOPE MANAGEMENT 3
PROJECT SCOPE IDENTIFICATION
The identified ‘deliverables’ must have the
following characteristics: Tangible – real objects that can be seen, felt & sensed and are not imaginary, vague or elusive. Should be definable and easily understood by project participants. Measurable - can be used to measure progress in quantitative terms using standard measurements. Verifiable – the specified measures should be verifiable by any agency at the time of delivery and acceptance.
V. C. DATEY PROJECT SCOPE MANAGEMENT 4
PROJECT SCOPE IDENTIFICATION
The 100% Rule: captures all
deliverables – internal, external, and interim – in terms of the work to be completed. The WBS should not include any work that falls outside the actual scope of the project Planned outcomes instead of planned actions : define WBS elements in terms of outcomes or results. Mutually exclusive elements : no overlap in scope definition between two elements of a WBS.