ch05
TRANSCRIPT
Information Technology Information Technology Project Management, Sixth Project Management, Sixth EditionEdition
Note: See the text itself for full citations.
Copyright 2009
Understand the importance of good project scope management
Discuss methods for collecting and documenting requirements in order to meet stakeholder needs and expectations
Explain the scope definition process and describe the contents of a project scope statement
Discuss the process for creating a work breakdown structure using the analogy, top-down, bottom-up, and mind-mapping approaches
Information Technology Project Management, Sixth Edition 2
Copyright 2009
Explain the importance of verifying scope and how it relates to defining and controlling scope
Understand the importance of controlling scope and approaches for preventing scope-related problems on information technology projects
Describe how software can assist in project scope management
Information Technology Project Management, Sixth Edition 3
Copyright 2009
Scope refers to all the work involved in creating the products of the project and the processes used to create them
A deliverable is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes
Project scope management includes the processes involved in defining and controlling what is or is not included in a project
Information Technology Project Management, Sixth Edition 4
Copyright 2009
Initiation involves committing the organization to begin a project or continue to the next phase of a project. An output of initiating processes is a project charter, which is a key document.
Scope Planning defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them
Information Technology Project Management, Sixth Edition 5
Copyright 2009
Scope Definition subdividing the major project deliverables into smaller, more manageable components. The project team creates a work break down structure (WBS) during this process.
scope Verification involves formalizing acceptance of the project scope. Key project stakeholders (sponsor) formally accept the deliverables of the project.
Information Technology Project Management, Sixth Edition 6
Copyright 2009
Scope change control : controlling changes to project scope throughout the life of the project. Scope changes , corrective action, and lessons learned are outputs of this process.
Information Technology Project Management, Sixth Edition 7
Information Technology Project Management, Sixth Edition 8
Copyright 2009
Scope planning involves developing documents to provide the basis for future project decisions.
Project charter, descriptions of the products involved in the project and project constraints are inputs to the scope planning process.
Outputs of this process are the written scope statement, including supporting detail and a scope management plan.
Information Technology Project Management, Sixth Edition 9
Copyright 2009
Project Scope Statement is a document used to develop a common understanding of project scope.
Include a project justification, a brief description of the project’s products, a summary of all project deliverables, and project success criteria.
Information Technology Project Management, Sixth Edition 10
Copyright 2009Information Technology Project Management, Sixth Edition 11
Copyright 2009
Define the work required for the project and to break it into manageable pieces.
It defines a Baseline for performance measurement .
The output of the scope definition process is the work breakdown structure for the project.
Information Technology Project Management, Sixth Edition 12
Copyright 2009
A WBS is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project
WBS is a foundation document that provides the basis for planning and managing project schedules, costs, resources, and changes
Decomposition is subdividing project deliverables into smaller pieces
A work package is a task at the lowest level of the WBS
Information Technology Project Management, Sixth Edition 13
Copyright 2009Information Technology Project Management, Sixth Edition 14
Copyright 2009Information Technology Project Management, Sixth Edition 15
Copyright 2009Information Technology Project Management, Sixth Edition 16
Copyright 2009Information Technology Project Management, Sixth Edition 17
Copyright 2009Information Technology Project Management, Sixth Edition 18
Copyright 2009
Using guidelines: some organizations provide guidelines for preparing WBSs
The analogy approach: review WBSs of similar projects and tailor to your project
The top-down approach: start with the largest items of the project and break them down
The bottom-up approach: start with the specific tasks and roll them up
19
Copyright 2009
• Many organizations provide guidelines and templates for developing WBSs, as well as examples of WBSs from past projects. Microsoft Website and other sites have many WBS templates.
• PMI developed a WBS Practice Standard to provide guidance for developing and applying the WBS to project management.
• If guidelines for developing a WBS exist, it is very important to follow them.
Information Technology Project Management, Sixth Edition 20
Copyright 2009
• A WBS is first created by looking for a similar project done in the past and using its WBS as a starting point.
• Some organizations keep a repository of WBSs and other Project documentation on file to assist people who will work on future projects.
• Many Project Management software including Ms-Project include sample files to assist users in creating a WBS and Gantt Chart .
Information Technology Project Management, Sixth Edition 21
Copyright 2009
• Top-down Approach start with the largest items of the project and break them into their subordinate items.
• This process involves refining the work into greater and greater levels of detail. After finishing the process, all resources should be assigned at the work package level.
• Top-down approach is best suited to project managers who have vast technical insight and a big-picture perspective.
Information Technology Project Management, Sixth Edition 22
Copyright 2009
• The team first looks at the list of objectives from the Project Charter and generates a list of low-level activities that will be needed to complete the objectives.
• The team then groups together the tasks by deliverable. This process continues untill all relevant tasks have been grouped into subgroups that directly tie to a major objective.
• Project Managers often use this approach for projects that represent entirely new Systems or approaches to doing a job.
Information Technology Project Management, Sixth Edition 23
Copyright 2009Information Technology Project Management, Sixth Edition 24
Copyright 2009
The existence of a similar project – would lead you to the analogy Approach , which if done correctly, is the fastest and most accurate method.
For entirely new systems use bottom up approach.
Experience level of the project manager and team choose the Top-down approach
Information Technology Project Management, Sixth Edition 25
Copyright 2009
Many WBS tasks are vague and must be explained more so people know what to do and can estimate how long it will take and what it will cost to do the work
A WBS dictionary is a document that describes detailed information about each WBS item.
The approved project scope statement and its WBS and WBS dictionary form the scope baseline, which is used to measure performance in meeting project scope goals
Information Technology Project Management, Sixth Edition 26
Copyright 2009
Scope verification involves formal acceptance of the completed project scope by the stakeholders.
To receive formal acceptance of the project scope, the project team must develop clear documentation of the project’s products and procedures for evaluating if they were completed correctly and satisfactorily.
Information Technology Project Management, Sixth Edition 27
Copyright 2009
Scope control involves controlling changes to the project scope.
Goals of scope control are to:◦ Identify the factors that cause scope changes◦ Assure changes are processed according to procedures
developed as part of integrated change control◦ Manage changes when they occur
Variance is the difference between planned and actual performance
Information Technology Project Management, Sixth Edition 28
Copyright 2009
Project scope management includes the processes required to ensure that the project addresses all the work required, and only the work required, to complete the project successfully
Main processes include:◦ Collect requirements◦ Define scope◦ Create WBS◦ Verify scope◦ Control scope
Information Technology Project Management, Sixth Edition 29