Assessment_2_Brief_Plans
ASSESSMENT 2 BRIEF
Subject Code and Title Project Planning and Budgeting
Assessment Project Scope and Quality Management Plans
Individual/Group Group (2 Students)
Length 1300 words
Learning Outcomes The Subject Learning Outcomes demonstrated by successful
completion of the task below include:
(a) Evaluate and apply a range of project management
tools, techniques and practices to diverse global
projects.
(b) Evaluate budgetary and planning outcomes against
project success measures, including stakeholde
expectations.
(c) Develop effective communication methods to
articulate planning outcomes to key stakeholders.
Assessment Task
In a group of 2 students, devise project scope and quality management plans that articulate the
scope and quality approaches for the project in the assigned Case Study provided by your Learning
Facilitator.
Please refer to the Instructions for details on how to complete this task.
Context
The backbone of a project manager’s work is the Project Management Plan. This plan details the
project's execution, monitoring, and control. It combines all of the planning's sub-plans and
aselines. You and your group will create a Project Management Plan for your assigned Case Study in
this assessment. Applying scope and quality tools and techniques to develop the scope statement
and scope and quality management plans of a project is a crucial part of project planning. One of the
keys to project success is effective scope management. Project Scope Management includes
processes to ensure that the project includes all work required to complete it successfully.
A project's quality management plan defines quality requirements, standards for the project and its
deliverables, and how the project will demonstrate compliance. One of the main benefits of this
process is that it provides guidance and direction on how quality will be managed and validated
throughout the project.
Instructions
1. Connect with your assigned group members (provided by your Learning Facilitator).
2. Analyse the project from your own perspectives as up-and-coming project manage
3. Your group will devise subsidiary Project Management plans and Quality, using the
assigned Case Study provided on Blackboard by your Learning Facilitator.
a) Although all students will receive the same case study, you are expected to
complete this task and create a distinct set of plans in your group.
) Quality management plans and supporting documentation must include, but not
e limited to, the following components:
● Quality Responsibilities
● Approaches to Quality Assurance, Control and Improvement
● Quality Metrics
4. Write 2600 words and describe the processes, tools, and techniques used in your scope
and quality management plans, as well as your justification for the quality metrics
selected.
5. You can use the template in this subject’s Learning Resources or create your own to
devise the subsidiary project scope and quality management plans.
6. After completing your plans and supporting documentation, each member of your group
should reflect on your respective contributions to the assessment and then (individually)
complete the Group Contribution Survey.
Referencing
It is essential that you use the most recent edition of APA style for citing and referencing research.
Please see more information on referencing in the Academic Skills webpage.
Submission Instructions
Submit your answers in an academic style, including both in-text citations and a full reference list
using the co
ect APA style of referencing.
https:
li
ary.to
ens.edu.au/academicskills/apa/tool
JP_Red Bank Case Study(1)
J.P - Red Bank Project
The Red Bank is a key player in Australia financial market. With
consideration of continuous raise of cash rate, the Red Bank plans to
improve its risk management practice in loan approval and repayment
control. J.P Consultancy upholds its exceptional world- wide reputation
in providing financial consultation services and advice to commercial
anks. Therefore, when the Red Bank approaches J.P to seek its
services, J.P’s Business Development Executive (Lachlan Smith)
suggested a four-month end to end project to assist the Red Bank to
eform its risk management system, processes and practices.
The objectives for the project include: (1) to research and customise a
isk management framework for the Red Bank; (2) to on-site deliver the
newly designed risk management framework and ensure the
implementation in the Red Bank; (3) to evaluate the new framework and
eady for whole organisation rollout.
The project contains five phases and multiple hurdles to be crossed. A
drafted action list is presented in Table 1. Potential budgetary allocation
is suggested in Table 2. J.P has a sufficient talent pool, and many
capable staff could be assigned to this project. The available staffing mix
is shown in Table 3.
Your tasks:
This case study provides you with an opportunity of drawing on you
acquired project planning, scheduling, budgeting and quality
management skills and materials covered in this course. You are
esponsible for addressing all tasks and requirements listed in Section 1
and Section 2, in addition to Assessment
iefs, according to the case
study.
1-2) Quality management planning
● Develop the quality management
planning components of you
Quality Management Plan.
● Select at least Three work ID to
develop Quality Assurance
activities accordingly.
● Apply quality management tools
to ensure the project
performance is consistent with
the quality management plan.
Justify your selection.
Table 1 – The Project
Activities
ID Descriptio
n
Duratio
n
(Day)
Predecesso
Phase 1: Project engagement setting
1.1 Touchpoint to J.P BDE for potential services 3 NA
1.2 J.P. consultant internal
iefing XXXXXXXXXXSS+1)
1.3 Client meeting for problem
isk identification 12 1.2
1.4 Agreement and contract with cooling off period
of 5 days
XXXXXXXXXX
Phase 2: Structure a J.P Project Team
2.1 Lachlan Smith appoints Project Manager XXXXXXXXXXSS)
2.2 Project manager forms a team 15 2.1
2.3 Project team skills mapping XXXXXXXXXX
2.4 Conduct Project team and Consultant
workshops
10 2.3
2.5 Assign and agree responsibilities XXXXXXXXXXFF+2)
Phase 3: Production plan
3.1 Assessment of Red Bank risk management
maturity level
XXXXXXXXXXSS+8)
3.2 Analysis of the Enterprise Risk Register 5 3.1
3.3 Research cu
ent risk management practice inindustry and similar consultancy projects XXXXXXXXXXSS+2)
3.4 Customise a risk framework for the Red Bank 6 3.3
3.5 Modify existing frameworks to fit in the new one 3 2.5 FF, 3.4
3.6 Check APRA compliance XXXXXXXXXXFF)
3.7 Finalise the product XXXXXXXXXX
Phase 4: On-site (Red Bank) delivery
4.1 Presentation and validation of the J.P-Red
Bank risk framework
3 3.7+3
4.2 Explain implementation roadmap 2 4.1
4.3 Key risk management personnel nomination 5 4.2
4.4 Conduct Responsibilities workshops XXXXXXXXXXSS)
4.5 J.P and Red Bank system integration and
adaption
20 4.4
4.6 De-bug (discrete work XXXXXXXXXXFF)
4.7 Launch and manage a Pilot work 5 4.6
4.8 Project de-
ief for Red Bank senio
management
2 4.7 (FF)
Phase 5: Lessons Learned and Closure
5.1 Evaluation platform set-up 5 4.6
5.2 Lessons learned data collection J.P 10 5.1
5.3 Lessons learned data collection Red Bank XXXXXXXXXXSS)
5.4 Problems solving and/or disputes 5 5.2
5.5 Closure and Sign-off 1 5.4
PM2-Template.v3.Quality_Management_Plan
LOGO
Organisation [Name]
Department [Name]
Quality Management Plan
Project Name
Date:
Doc. Version:
Template version: 3.0.1
This artefact template is aligned with the PM² Guide V3.0
For the latest version of the templates visit:
https:
www.pm2alliance.eu/publications
The PM² Alliance is committed to the improvement of the PM² Methodology and of its supporting artefact. Project
management best practices and community contributions & co
ections are incorporated in the
PM² Alliance’s artefact templates.
Join the PM² Alliance and visit the PM² Alliance GitHub to provide your feedback & contribution:
https:
github.com/pm2alliance
Project Name> Quality Management Plan
Document Control Information
Settings Value
Document Title: Quality Management Plan
Project Title:
Document Author:
Project Owner (PO):
Project Manager (PM):
Doc. Version:
Sensitivity:
Date:
Document Approver(s) and Reviewer(s):
NOTE: All Approvers are required. Records of each approver must be maintained. All Reviewers in the
list are considered required unless explicitly listed as Optional.
Name Role Action Date
Approve / Review
Document history:
The Document Author is authorized to make the following types of changes to the document without
equiring that the document be re-approved:
● Editorial, formatting, and spelling
● Clarification
To request a change to this document, contact the Document Author or Owner.
Changes to this document are summarized in the following table in reverse chronological orde
(latest version first).
Revision Date Created by Short Description of Changes
Configuration Management: Document Location
The latest version of this controlled document is stored in
.
These notes should be deleted in the final version :
Notes for Templates:
● Text in : has to be defined.
● Text in
lue>: guidelines and how to use the Template. Should be deleted in the final
version.
● Text in green: can be customised. Should be recolored to black in the final version.
Date: 2 / 15
Doc.Version: Project Name> Quality Management Plan
TABLE OF CONTENTS
1. INTRODUCTION 4
2. QUALITY MANAGEMENT OBJECTIVES 4
3. QUALITY MANAGEMENT PROCESS 4
3.1. Quality Management Roles and Responsibilities 8
4. TOOLS AND TECHNIQUES 9
5. QUALITY ASSURANCE ACTIVITIES 9
6. METRICS 10
7. QUALITY CONTROL 11
7.1. Quality Reviews 11
7.2. Deliverables Reviews 11
7.3. Other Quality Control Activities 11
8. QUALITY RECORDS 11
9. CONFIGURATION MANAGEMENT 11
10. RELATED PM² PLANS 13
APPENDIX 1: REFERENCES AND RELATED DOCUMENTS 15
Date: 3 / 15
Doc.Version: Project Name> Quality Management Plan
1. INTRODUCTION
The PM² guide describes a light Quality Management section of the Project Handbook. However, the
usage of this Quality Management Plan template is advised in case of complex or risky projects
where quality activities are of special importance for the project.
The objectives of this document are:
● To outline the quality strategy, approach and process to be used for the project;
● To identify the roles and responsibilities related to project quality management;
● To identify the major project management artefacts and deliverables;
● To define the quality assurance and control activities and to plan them throughout the
project;
● To support the agreement on project quality requirements and metrics, and the method to
evaluate them;
● To specify the methodology, standards, tools and techniques used to support quality
management.
Note that in the PM² Guide, the Quality Management Plan is mainly described as a part of the
Project Handbook. However the Project Manager (PM) can decide, given the size or complexity of the
project, to use a separate document to capture the quality attributes for the project and in this case
we propose to use this template.
2. QUALITY MANAGEMENT OBJECTIVES
Project quality management aims to ensure that the cu
ent project will meet the expected results in
the most efficient way and that deliverables will be accepted by the relevant stakeholders. It involves
overseeing all activities needed to maintain a desired level of excellence. This includes creating and
implementing quality planning and assurance, as well as quality control and quality improvement.
This project will follow the PM2 quality management process that comprises the activities related to
the identification, planning, execution, and monitoring & control of project quality related activities.
The main project quality objectives are:
● The project's quality characteristics are defined, agreed and achieved throughout the
project;
● Quality assurance activities are performed as planned;
● Assure compliance with the organisation’s rules and regulations, as well as with relevant
governmental and industry rules, regulations and legislation;
● Any non-conformity (or opportunity for quality improvements) is identified and
implemented;
● Deliverables are accepted by the relevant stakeholders based on the defined
quality/acceptance criteria.
Please customise the above quality objectives as per your project o
and organization needs.
3. QUALITY MANAGEMENT PROCESS
Please tailor the quality management process if necessary (complete description or delete activities that are
not applicable to the project.
The project quality management process comprises all activities (related both to processes and
deliverables) that will increase the ability to meet the project expected results identified in the
Project Charter.
The quality management process for this project is comprised of five key steps:
● Define (Project) Quality Characteristics;
Date: 4 / 15
Doc.Version: Project Name> Quality Management Plan
● Perform Quality Assurance;
● Perform Quality Control;
● Perform Deliverables Acceptance; and
● Perform Final (Project) Acceptance.
Step 1: Define Quality Characteristics
The purpose of this step is to identify the objectives, approach, requirements, activities and
esponsibilities of the project's quality management process and how it will be implemented
throughout the project. These are documented in this plan based on the project objectives,
approach, deliverables, expected benefits and resources available (as defined in the Business Case,
Project Charter, Project Handbook, Project Work Plan, and other relevant plans).
The Quality Management Plan includes the description of the:
● Quality objectives, approach and requirements;
● Quality standards, guidelines, tools and techniques, e.g. the Quality Review Checklist and the
Deliverables Acceptance Checklist;
● Quality assurance activities and related responsibilities, e.g. Project Review Meetings,
monthly activities reports, compliance verification and audits to contractors' quality
assurance activities, among others;
● Quality control activities for continuous improvement, e.g. project management artefacts
eview and quality plans reviews;
● Configuration procedure related to project artefacts and deliverables.
Any quality activities related to project management artefacts are documented in the Quality
Management Plan, while quality assurance and control activities related to project deliverables can
e found in separate documents as e.g. test plans. These documents are project domain specific and
therefore not part of the PM² . Quality Control activities in the context of formal custome
acceptance of the deliverables are documented