FIT2002 Lecture Notes - Lecture 4: Human Resource Management, Deliverable
31 May 2018
School
Department
Course
Professor
FIT2002 - W4 Notes
•What is involved in project scope management, and why is good
project scope management so important for IT projects
!
Scope: all the work involved in creating the products of the project and the
processes used to create them
Deliverable: 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.
!
•What is involved in collecting requirements for a project? Why is it
often so difficult?
Requirements: need to be elicited, analysed, and recorded in enough
detail to be included in the scope baseline and be measured once project
execution begins
Difficult: users sometimes don't know what they want, have too much
information, cultures & politics (not sharing enough information)
Defining and documenting the features and functions of the products
produced during the project as well as the processes used for creating
them
!
•Describe different ways to develop a WBS
Using guidelines:
Analogy approach:
Top-down approach:
Bottom-up approach:
Mind-mapping:
!
•What is the main technique for validating scope?
Validating scope: formalising acceptance of the project deliverables
Formal acceptance of the completed project deliverables, customer
inspection and then sign-off on key deliverables
Use RTM to show to client for validation
!
•What processes are involved in project human resource
management?
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Fit2002 - w4 notes: what is involved in project scope management, and why is good project scope management so important for it projects. Scope: all the work involved in creating the products of the project and the processes used to create them. Deliverable: a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes. Requirements: need to be elicited, analysed, and recorded in enough detail to be included in the scope baseline and be measured once project execution begins. Dif cult: users sometimes don"t know what they want, have too much information, cultures & politics (not sharing enough information) De ning and documenting the features and functions of the products produced during the project as well as the processes used for creating them: describe different ways to develop a wbs. Validating scope: formalising acceptance of the project deliverables. Formal acceptance of the completed project deliverables, customer inspection and then sign-off on key deliverables.
