Lecture Ch 5

Lecture Ch 5 - Information Technology Project Management,...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Information Technology Project Information Technology Project Management, Sixth Edition Management, Sixth Edition Note: See the text itself for full citations.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
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
Background image of page 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
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
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
Background image of page 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 organizational process assets to 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 Information Technology Project Management, Sixth Edition 5
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Copyright 2009 Information Technology Project Management, Sixth Edition 6
Background image of page 6
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) For some IT projects, it is helpful to divide requirements development into categories called elicitation, analysis, specification, and validation It is important to use an iterative approach to defining requirements since they are often unclear early in a project Information Technology Project Management, Sixth Edition 7
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Copyright 2009 Information Technology Project Management, Sixth Edition 8
Background image of page 8
Interviewing Focus groups and facilitated workshops Using group creativity and decision-making techniques Questionnaires and surveys
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 01/30/2011 for the course OM 493 taught by Professor Murray during the Fall '10 term at George Mason.

Page1 / 36

Lecture Ch 5 - Information Technology Project Management,...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online