1. Diploma Project Management
Captain Cook College
Sharon Boyle

2.  Clarify & emphasize assessment items
 De-brief previous day’s role play
 Variation on Fred’s shed
Morning tea
 Quality plan for Fred’s shed – review the Quality plan on LMS
and assess if it is application to this project
 How could this be amended
Lunch
 Leadership & PM - video
 To follow
 Project Management Plan – started for some
 Close out report – started today for some
 Status report – started today for some
 Conclude Quality

3.  I need to see from you
◦ Project Meeting minutes –
 Meeting 1. was yesterday
 there will be another opportunity
◦ Project Management Plan –
 I suggest you find a template
 Includes at least one Variation Request
◦ Close out report – required in Cost & Time Units
◦ Status report – required in Cost & Time Unit
 I suggest choose a single project & staying with it
 I will be adjusting each unit in the LMS to
compensate

7.  Why important?
 What can go wrong?
 Relationship to other aspects of project
management?

8.  The establishes an orderly and effective
procedure for
◦ tracking the submission,
◦ coordination, review, evaluation,
◦ categorization, and
◦ approval for release of all changes to the project’s
baselines.

11.  Apply to Fred’s Shed or other identified
project
 How could this plan be used ?
 How to improve
◦ Submit 5 points/improvements on the Quality
template shown in the LMS in project –
◦ Today

12.  If project management is about getting
people to do things
 Leadership is required
 Maybe a different take is useful…
 Video on Leadership

13. ◦ I need to see from you
 Project Meeting minutes –
 Meeting 1. was yesterday
 there will be another opportunity
 Project Management Plan –
 I suggest you find a template
 Includes at least one Variation Request
 Close out report – required by Cost & Time Units
 Status report – required by Cost & Time Unit
 I suggest choosing a single project & staying
with it

14.  Quality objectives
◦ negotiated trade-offs between cost, schedule and
performance
◦ requirements from a higher project authority
◦ requirements from the client and other
stakeholders
◦ those quality aspects which may impact on
customer satisfaction

15.  Quality management plan includes
◦ authorisations
◦ responsibilities for quality control
◦ continuous improvement
◦ established processes
◦ quality assurance

16.  benchmarking
 brainstorming
 charting processes
 control charts
 defining control
 flowcharts
 group work activities
 processes that limit and/or indicate variation
 undertaking benefit/cost analysis
◦ & lots more which are project specific

17.  On-going through out project
 Causes identified recommend actions
 Quality control
◦ monitoring conformance with specifications
◦ monitoring of regular inspections by internal or
external agents
◦ recommending ways to eliminate causes of
unsatisfactory performance of products or
processes

18.  Review processes
◦ implement agreed changes
◦ throughout the project life cycle
◦ ensure continuous quality improvement
 Review project outcomes against
performance criteria
 Assess the effectiveness of quality
management processes and procedures
 Identify and document lessons learned
 Recommend improvements

19. Element Description
Date The date the CR was created
CR# Assigned by the Change Manager
Title A brief description of the change request
Description Description of the desired change, the impact, or benefits of a change should also be
described
Submitter Name of the person completing the CR Form and who can answer questions regarding
the suggested change
Phone Phone number of the submitter
E-Mail Email of the submitter
Product The product that the suggested change is for
Version The product version that the suggested change is for
Priority A code that provides a recommended categorization of the urgency of the requested
change (High, Medium, Low)

20. Priority Description
High <Insert the definition the project assigns to a high priority CR>
Medium <Insert the definition the project assigns to a medium priority CR>
Low <Insert the definition the project assigns to a low priority CR>
<priority> <Insert the definition the project assigns to this level of priority CR>

21. Type Description
Scope Change affecting scope
Time Change affecting time
Duration Change affecting duration
Cost Change affecting cost
Resources Change affecting resources
Deliverables Change affecting deliverables
Product Change affecting product
Processes Change affecting process
Quality Change affecting quality
Change requests are evaluated