Information Technology Project Management, Sixth Edition Note: See the text itself for full...
38
Chapter 5: Project Scope Management Information Technology Project Management, Sixth Edition See the text itself for full citations.
-
Upload
maude-hutchinson -
Category
Documents
-
view
221 -
download
0
Transcript of Information Technology Project Management, Sixth Edition Note: See the text itself for full...
Chapter 5:Project Scope Management
Information Technology Project Management, Sixth Edition
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
Learning Objectives
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
Learning Objectives (continued)
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 (i.e. project scope)
What is Project Scope Management?
Information Technology Project Management, Sixth Edition 4
Copyright 2009
Collecting requirements: defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them
Defining scope: reviewing the project charter, requirements documents, and create a scope statement
Creating the WBS: subdividing the major project deliverables into smaller, more manageable components
Verifying scope: formalizing acceptance of the project deliverables
Controlling scope: controlling changes to project scope throughout the life of the project
Project Scope Management Processes
Information Technology Project Management, Sixth Edition 5
Copyright 2009
Project Scope Management Processes
Information Technology Project Management, Sixth Edition 6
Copyright 2009
Scope management processes Summary
Information Technology Project Management, Sixth Edition 7
Copyright 2009
A requirement is “a condition or capability that must be met or possessed by a system, product, service, result, or component to satisfy a contract, standard, specification, or other formal document” (PMBOK® Guide, 2008)
It is important to use an iterative approach to defining requirements since they are often unclear early in a project
It costs much more to correct a defect that is found in later phases than to fix it in the requirements phase
Collecting Requirements
Information Technology Project Management, Sixth Edition 8
Copyright 2009
Relative Cost to Correct a Software Requirement Defect
Information Technology Project Management, Sixth Edition 9
Copyright 2009
Interviewing stakeholder one-on-one◦Effective but expensive and time-consuming
Focus groups and facilitated workshops◦ Faster and less expensive than one-on-one interviews
Questionnaires and surveys ◦Efficient as long as key stakeholders provide honest and
thorough information Observation ◦Good for projects that involve improving working
processes and procedures
Methods for Collecting Requirements
Information Technology Project Management, Sixth Edition 10
Copyright 2009
Prototyping ◦Used for software development projects
Software tools◦Several SW tools are available to assist in collecting and
management requirements
Methods for Collecting Requirements (cont.)
Information Technology Project Management, Sixth Edition 11
Copyright 2009
Genesys Telecommunications Laboratories uses Accept software, a product planning and innovation management application and winner of the Excellence in Product Management Award from 2006–2008
Accept helps them put a consistent, repeatable, and predictable process for new product definition and development
They can define what information comprises a requirement and enforce discipline around that process
What Went Right?
Information Technology Project Management, Sixth Edition 12
Copyright 2009
Requirements documents are often generated by software and include text, images, diagrams, videos, and other media;
They are often broken down into different categories such as functional, service, performance, quality, training requirements, and so on
A requirements management plan describes how project requirements will be analyzed, documented, and managed
A requirements traceability matrix (RTM) is a table that lists requirements, various attributes of each requirement, and the status of the requirements to ensure that all requirements are addressed
Documenting Requirements
Information Technology Project Management, Sixth Edition 13
Copyright 2009
Sample Requirements Traceability Matrix
Information Technology Project Management, Sixth Edition 14
Copyright 2009
Project scope is the work involved to create products that meet project requirements
Good scope definition helps◦Improve accuracy of time, cost, and resource
estimates◦Define baseline for performance measurement◦Determine clear work responsibility
Defining Scope
Information Technology Project Management, Sixth Edition 15
Copyright 2009
Main inputs◦Project charter◦Requirements documentation
The main outputs◦Project scope statement◦Project document updates
As time progresses, the scope of a project should become more clear and specific
Defining Scope (cont.)
Information Technology Project Management, Sixth Edition 16
Copyright 2009
Further Defining Project Scope
Information Technology Project Management, Sixth Edition 17
Copyright 2009
A WBS is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project
Decomposition: subdividing project work into smaller pieces
WBS is a foundation document that provides the basis for:◦Planning (project management plan)◦managing project schedules, costs, and resources◦Project changes management
Creating the Work Breakdown Structure (WBS)
Information Technology Project Management, Sixth Edition 18
Copyright 2009
WBS is the decomposition of the project work into smaller parts (tasks). It can be organized by:◦Product◦Project phases◦Project management process groups
A work package is a task at the lowest level of the WBS (can not be decomposed into smaller tasks)
WBS (cont.)
Information Technology Project Management, Sixth Edition 19
Copyright 2009
Sample Intranet WBS Organized by Product
Information Technology Project Management, Sixth Edition 20
Copyright 2009
Sample Intranet WBS Organized by Phase
Information Technology Project Management, Sixth Edition 21
Copyright 2009
Intranet WBS and Gantt Chart in Microsoft Project
Information Technology Project Management, Sixth Edition 22
Copyright 2009
Intranet Gantt Chart Organized by Project Management Process Groups
Information Technology Project Management, Sixth Edition 23
Copyright 2009
Executing Tasks for JWD Consulting’s WBS
Information Technology Project Management, Sixth Edition 24
Copyright 2009
Using guidelines: ◦ some organizations, like the DOD, provide guidelines for
preparing WBSs◦Many organizations use templates and examples provided
by Microsoft Project or PMI Analogy approach: review WBSs of similar
projects and tailor to your project◦McDonnell aircraft company uses 74 previous WBS to
create a new one for a new aircraft design Top-down approach: start with the largest items of
the project and break them down into smaller items Bottom-up approach: start with the specific tasks
and roll them up (integrate them)
Approaches to Developing WBSs
Information Technology Project Management, Sixth Edition 25
Copyright 2009
Mind-mapping approach: a technique that uses branches radiating out from a core idea to structure thoughts and ideas
Use MindManager software by Mindjet (www.mindjet.com) to create a mind-mapping WBS
Mindmanager software can export WBS to Microsoft Project 2007
Approaches to Developing WBSs (cont.)
Information Technology Project Management, Sixth Edition 26
Copyright 2009
Sample Mind-Mapping Approach for Creating a WBS
Information Technology Project Management, Sixth Edition 27
Copyright 2009
Project 2007 File with WBS Generated from a Mind Map
Information Technology Project Management, Sixth Edition 28
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
The WBS Dictionary and Scope Baseline
Information Technology Project Management, Sixth Edition 29
Copyright 2009
A unit of work should appear at only one place in the WBS
The work content of a WBS item is the sum of the WBS items below it
A WBS item is the responsibility of only one individual, even though many people may be working on it
The WBS must be consistent with the way in which work is actually going to be performed; it should serve the project team first and other purposes only if practical
Advice for Creating a WBS and WBS Dictionary
Information Technology Project Management, Sixth Edition 30
Copyright 2009
Project team members should be involved in developing the WBS to ensure consistency
Each WBS item must be documented in a WBS dictionary to ensure accurate understanding of the scope of work included and not included in that item
The WBS must be a flexible tool to accommodate inevitable changes while properly maintaining control of the work content in the project according to the scope statement
Advice for Creating a WBS and WBS Dictionary (continued)
Information Technology Project Management, Sixth Edition 31
Copyright 2009
It is very difficult to create a good scope statement and WBS for a project
It is even more difficult to verify project scope and minimize scope changes
Scope verification involves formal acceptance of the completed project scope by the stakeholders
Acceptance is often achieved by a customer inspection and then sign-off on key deliverables
To minimize scope changes, it is crucial to do a good job of configuration management and verifying project scope
Verifying Scope
Information Technology Project Management, Sixth Edition 32
Copyright 2009
Scope creep: the tendency for project scope to keep getting bigger and bigger
Lack of user involvement in the project scope Not using off-the-shelf hardware and software and
using unnecessary latest and greatest technology Failure to follow good project management
processes
Scope Problems
Information Technology Project Management, Sixth Edition 33
Copyright 2009
A project scope that is too broad can cause severe problems◦Scope creep and an overemphasis on technology for
technology’s sake resulted in the bankruptcy of a large pharmaceutical firm, Texas-based FoxMeyer Drug
◦ In 2001, McDonald’s fast-food chain initiated a project to create an intranet that would connect its headquarters (centers of admin) with all of its restaurants to provide detailed operational information in real time; after spending $170 million on consultants and initial implementation planning, McDonald’s realized that the project was too much to handle and terminated it
What Went Wrong?
Information Technology Project Management, Sixth Edition 34
Copyright 2009
1. Keep the scope realistic. Don’t make projects so large that they can’t be completed. Break large projects down into a series of smaller ones.
2. Involve users in project scope management. Assign key users to the project team and give them ownership of requirements definition and scope verification (Joint Application Development JAD).
3. Use off-the-shelf hardware and software whenever possible. Many IT people enjoy using the latest and greatest technology, but business needs, not technology trends, must take priority.
4. Follow good project management processes. As described in this chapter and others, there are well-defined processes for managing project scope and others aspects of projects.
Best Practices for Avoiding Scope Problems
Information Technology Project Management, Sixth Edition 35
Copyright 2009
Scope control involves controlling changes to the project scope
Variance is the difference between planned and actual performance
Goals of scope control are to:◦ Influence 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
Controlling Scope
Information Technology Project Management, Sixth Edition 36
Copyright 2009
Word-processing software helps create several scope-related documents
Spreadsheets help to perform financial calculations and weighted scoring models and to develop charts and graphs
Communication software like e-mail and the Web help clarify and communicate scope information
Project management software helps in creating a WBS, the basis for tasks on a Gantt chart
Specialized software is available to assist in project scope management
Using Software to Assist in Project Scope Management
Information Technology Project Management, Sixth Edition 37
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
Chapter Summary
Information Technology Project Management, Sixth Edition 38
![[PPT]PowerPoint Presentation - California State University, …pjl26399/ITPM_10.pptx · Web viewChapter 10:Project Communications Management Note: See the text itself for full citations.](https://static.fdocuments.net/doc/165x107/5addce7e7f8b9aa5088d52c9/pptpowerpoint-presentation-california-state-university-pjl26399itpm10pptxweb.jpg)
