Textbook Notes (270,000)
CA (160,000)
Ryerson (10,000)
ITM (800)
ITM 750 (20)
Chapter 5

ITM 750 Chapter Notes - Chapter 5: Project Plan, Requirements Management, Project Charter

Information Technology Management
Course Code
ITM 750
Tim Mc Laren

This preview shows page 1. to view the full 5 pages of the document.
Chapter 5 – Project Scope Management
- Scope: refers to all the work involved in creating the product of the project and the
processes used to them then
- Project scope management: includes the processes involved in defining and
controlling what works is not included in the prodict
-There are six main scope management:
1) Project scope management involves determining how the projects scope and
requirements will be managed.
2) Collecting requirements involves defining and documenting the features and
functions of the products for the project as well as the processes used for
creating them.
3) Defining scope involves reviewing the scope management plan, project charter,
requirements documents, and organizational process assets to create a scope
statement, adding more information as requirements are developed and change
requests are approved. The main outputs of scope definition are the project
scope statement and updates to project documents.
4) Creating the WBS involves subdividing the major project deliverables into
smaller, more manageable components. The main outputs include a scope
baseline (which includes a work breakdown structure and a WBS dictionary) and
updates to project documents.
5) Validating scope involves formalizing acceptance of the project deliverables. Key
project stakeholders, such as the customer and sponsor for the project, inspect
and then formally accept the deliverables during this process. If the deliverables
are not acceptable, the customer or sponsor usually requests changes. The main
outputs of this process, therefore, are accepted deliverables, change requests,
work performance information, and updates to project documents.
6) Controlling scope involves controlling changes to project scope throughout the
life of the project—a challenge on many IT projects. Scope changes often
influence the team’s ability to meet project time and cost goals, so project
managers must carefully weigh the costs and benefits of scope changes. The
main outputs of this process are work performance information, change requests,
and updates to the project
-It can be informal and broad or formal detailed , based on the needs of the project
-There are two output documents: scope management plan and requirements
management plan
-A scope management plans includes the following information:
oHow to prepare a detailed project scope statement
oHow to create a WBS
oHow to maintain and approve the WBS
oHow to obtain formal acceptance of the completed project deliverables
oHow to control requests for changes to the project scope
- Requirements: conditions or capabilities that must be met by the project or present in
the product, service or result to satisfy an agreement or other formally imposed
-The requirements management plan can include the following information
oHow to plan, track, and report requirements activities
You're Reading a Preview

Unlock to view full version

Only page 1 are available for preview. Some parts have been intentionally blurred.

oHow to perform configuration management activities
oHow to prioritize requirements
oHow to use product metrics
oHow to trace and capture attributes of requirements
-It is the most difficult
-People often don’t have a good process for collecting and documenting project
-Methods of collecting requirements
oInterviewing stakeholders, Focus groups, workshops, group creativity and
decision making techniques
- Requirements traceability matrix: is a table that list requirements, their various
attributes and the status of the requirements to ensure that all are addressed
-A good scope definition is very important to product success because it help improve the
accuracy of time, cost, and resource estimates
-The key inputs include project charter, scope management plan, requirements
documentation, organizational process assets
- Project scope statements: should include at least a product scope description, product
user acceptance criteria, and detailed information on all project deliverables
oAlso include project boundaries, constraints, and assumptions
-The scope of a project should become clear and specific and an update to date scope
statement is an important
- Work breakdown structure: is a deliverable oriented grouping of the work involved in a
project that defines its total scope
oit is important to organize and drive the work into logical parts based on how the
work will be performed
othe WBS is the foundation document in project management
othe main tool or technique is decomposition: that is subdividing project
deliverables into smaller pieces
othe outputs of the process of creating the WBS are the scope baseline (approved
project scope management) and project documents updates
oWBS is often depicted as a task oriented tree of activities, similar to an
organizational chart
- Work package: is a task at the lowest level of the WBS
You're Reading a Preview

Unlock to view full version