Manage Program Risk: BSBPMG632
Manage Program Risk: BSBPMG632
Manage Program Risk: BSBPMG632
GUIDE
BSBPMG632
MANAGE PROGRAM RISK
BSBPMG632 Manage program risk | 2
First published 2021
Version 1.0
RTO Works
www.rtoworks.com.au
[email protected]
This resource is copyright. Apart from any fair dealing for the purposes of private study, research, criticism or review
as permitted under the Copyright Act 1968, no part may be reproduced by any process without written permission as
expressed in the RTO Works License Agreement.
The information contained in this resource is, to the best of the project team’s and publisher’s knowledge true and
correct. Every effort has been made to ensure its accuracy, but the project team and publisher do not accept
responsibility for any loss, injury or damage arising from such information.
While every effort has been made to achieve strict accuracy in this resource, the publisher would welcome
notification of any errors and any suggestions for improvement. Readers are invited to write to us at
[email protected].
Business Works is a series of training and assessment resources developed for qualifications within the Business
Services Training Package.
Contents
Overview 4
Topic 1: Planning for program risks 5
Topic 2: Managing program risks 19
Topic 3: Assessing program risk outcomes 25
The Student Guide should be used in conjunction with the recommended reading and any further
course notes or activities given by the trainer/assessor.
Learning goals
Learning goals include:
In this topic we will look at how program managers plan risk management programs. The risk
management process involves:
Firstly, to plan for risk, you need to identify potential, actual and residual risks. The following table
highlights the difference between each type of risk:
x These are risks that could be likely to happen and that could cause
Potential risk a project to fail or not achieve its goals. Risks may relate to cost,
to a program time, technology, resources. These can occur from poor or
inaccurate planning.
Actual risks x These are known risks that can be taken into account.
All of these risks must be identified during the planning process so that they can be managed.
Activity: Read
Reference information generated by others who are part of this framework when they make
risk-related decisions.
The design of the risk management framework must take into consideration:
Accountabilities the team etc has for performance, production, service delivery and similar.
The Risk Management policy of the organisation as it applies to the specific work area.
Resources needed for the work unit to do the jobs expected of it.
The framework used should support managing program risk as it applies a structured,
methodological, formal process followed by all project managers.
The AS/NZS ISO 31000: 2018 provides organisations with principles and general guidelines to be
considered when developing risk management frameworks and programs. See the link in the next
activity on the principles, framework and. Process for the standard.
Use of or adherence to this standard is not mandatory but is considered ‘best practice’ or the
benchmark against which an organisation’s risk management practices can be judged.
Stakeholder involvement
Methods to be employed
This requires planning on which the risk management approach will be used in managing risks of
the program.
Risks impact project costs, time, quality, and scope of work and so can program opportunity.
Program opportunities can result in cost and time savings without compromising the quality or
scope of program works.
As per Project Management Book of knowledge (PMBOK), both risks and opportunities are
managed using same methodologies.
In this unit, we will follow a risk management methodology for managing potential risks and
opportunities in a program.
Team level – each team is responsible for identifying, assessing and mitigating risks that are
pertinent to their teams. These teams can be sub-project teams and come from different parts
of the organisation or diverse organisations.
o Risk sensitivity in terms of likelihood or probability of risk occurrence e.g. low, medium or
high.
A note on stakeholder consultation:
A program manager will need to consult with stakeholders for their views on risk management
planning. A stakeholder can include team members, clients, senior management, decision
makers, authorities or any other person who has an interest in the project. A program manager
may need their input for:
Gaining stakeholder’s input can highlight critical factors or issues as well as views that can either
support or hold back an organisation’s ability to manage risk.
You will see that throughout each phase of the risk management process, the program manager
carries out a number of consultations to identify, document and analyse program level risks.
What is risk index priority and what are some advantages of prioritising risks?
o What are the key elements used in mapping risks on each matrix?
o What are some general rules of thumb that can be used in calculating or
working out impact and probability of risks?
Do you think risks should be assessed at both team and program levels?
Support your answers with reasons.
Your trainer/assessor will facilitate a discussion about the outcomes from the
research.
Risk identification
Requires program and project managers and other key stakeholders to consult with each
other to be objective and brainstorm to recognise risks.
This is done after the project scope, milestones and elementary requirements of the program
have been established but before the business case and program budget is prepared.
Managing risks can require additional time and money, therefore must be identified prior to
finalising program costs.
Potential sources of risks include technology, politics, environmental, legal, sponsors, timing or
schedule, technology, budget or costs, etc.
Source: https://opentextbc.ca/projectmanagement/chapter/chapter-16-risk-management-planning-project-management/
Risk documentation
Risks can be recorded on a risk register with details of its cases, events and effects of risks on
overall program.
It shows that a thorough and systematic approach was adopted to identify risks.
Helps review and update risks throughout the life of the program.
The risk register with details from past projects can be useful in identifying what worked, what
did not and what must not be repeated in other projects. Other reasons include:
Letting risks fall through the cracks can impact project outcomes significantly.
Learning from mistakes and not repeating them can save costs and time.
Improves product quality, saves time and money in the long run.
A dynamic risk register can help to avoid identified risks through different project teams utilising a
process that will keep track of risks within their areas of specialisation, providing more data to help
identify and mitigate potential risks across a program.
A dynamic risk register is one that is kept up to date with all of the of the most important risks the
project faces and how the each of the
project management team will deal with
them. The risk register is usually in a table
form and lists risks, their analysis and risk
treatments.
Risk management software can allow a
risk register to be dynamic, as it can be
managed and coordinated across multiple
projects in a structured and controlled
platform. The alternative would be to use
a spreadsheet that is accessed by all
Activity: Watch
Discuss the use of a dynamic risk register across a program and its benefits in
class.
Note key learnings form video and discussion.
Your trainer/assessor will facilitate a discussion about the outcomes from the video.
Analyse risks
Risks are categorised in three forms. It is important to register the first two forms of risks as it
permits time to address the unknowable risks when it occurs. It is advisable to factor in a
percentage of cost and time to address unknowable risks even when they are unpredictable.
This gives your budget and delivery time some buffer to respond to any situational surprises.
o Known risks – risks known by many persons as it is evident in the early phases of
program planning.
o Unknown risks – risks that are known by a limited number of people and not recognised
in the planning phase.
o Unknowable risks – risks are completely unforeseen and surprising.
o Quantitative analysis – uses numbers to measure the overall impact of risks on the
program. E.g. the numerical scale or cost measures
o Qualitative analysis – uses words to describe the overall impact of risks on the program.
E.g. high, medium or low impact.
Source: https://www.pmi.org/learning/library/practical-risk-management-approach-8248 and
https://www.izenbridge.com/blog/differentiating-quantitative-risk-analysis-and-qualitative-risk-analysis/
Treatment of risks
The program manager and the project managers must consult other key stakeholders and
work together to identify possible responses to risks.
They must develop strategies and plans that will be implemented to treat the risks.
o Acceptance – allow the risk to persist and deal with it when it eventuates
o Where will the additional costs of treatment be funded from and who will authorise it?
Directing – this form of management will be required with new project managers who have
minimum or no experience in managing risks. This can be termed providing instructions and
doing a follow up to check if the tasks are understood and executed properly.
Support and coaching – this form of management can be adopted either with new or
experienced project managers in the following ways:
o Go above and beyond to assist them.
o Empathise and work as a team player not necessarily as a boss or a someone who works
above them.
o Back them up and investigate if project managers have problems with clients.
o Encourage project managers to take risks to build their confidence or learn from mistakes
together.
o Create a learning environment and new experiences.
Mentoring – this form of management is encouraged when you have semi to experienced
project management who can work with little or minimum guidance.
o Be a good role model and communicate with your team.
Managing risks
Program managers need to ensure risk management is visible and dynamic across the program so
that risks are assigned and managed in a timely manner. This done by developing a risk
management structure.
1. 2. 3. 4. 5. 6.
Risk Risk Management Make risks Chunk Assign
management acceptance commitment visible organisation cluster
policies & tolerance manager
procedures
Incorporating multiple risks into the organisational risk management’s big picture
Chunking the organisation into parts with objectives to deliver project outcomes in a timely
manner.
Clustering risk activities by team, tolerance levels and assigning them to relevant project
managers or individuals. This person is called the cluster manager who will be responsible for
managing risk activities.
Source: https://www.riskdecisions.com/assigning-responsibility-managing-risk-using-risk-management-clusters/
Cluster manager makes the chunk of the organisation aware of risks and ensures its visible.
The cluster manager can make risk plans visible by distributing the risk management plan
electronically, communicating about the tolerance levels and impacts of risks in informal or
formal conversations, printing out the plan and pining it in near scrum area or project
storyboard or noticeboard.
It allows clusters of the organisation to focus on deliverables whilst managing risk activities and
ensures risks are identified and risk treatment plan is executed in a timely manner.
Risks can emerge, change or disappear as an organisation’s external and internal context
changes. Risk management should therefore be dynamic so that it can anticipate, detect,
acknowledge and be responsive to those changes and events in an appropriate and timely manner.
The risk management framework should be dynamic, so that when there are changes to the
environment, it can be updated to reflect these changes.
If a standard approach is taken to risk management, then it allows risks to be appropriately
prioritised across all operations, resulting in effective controls.
Appropriate and timely involvement of stakeholders enables transparency and can result in
improved awareness and informed risk management.
Executing the planned risk treatment plan in a timely manner reduces frustration and stress
build up.
Addressing the risk treatment plan sometimes requires work in cross teams. The cluster managers
must ensure any team interdependences are clearly worked out and service level agreements are
put in place and risk treatment plans are executed effectively without wasting time.
The project teams must review the risk register or list regularly, for example on a fortnightly basis.
Stage one – Use of critical path - show which tasks have high impact on outcomes, its
Define project interdependence on tasks and duration. This helps identify high-risk
scope and activities.
goals
Use of Gantt Chat – shows relationships between tasks and their
interdependencies. Unless one task is completed, the next task will have
to wait. This can also assist with outlining risks and making mitigation
and contingency plans.
Stage two – Project managers and key stakeholders break up a major task into single
Detail work activities. During this phase, additional risks can be identified. Along with
breakdown allocation of many single activities, risks are also assigned to project
teams.
Stage three – Risks associated with resources such as personnel and finance are
Resource and identified.
budget
scheduling
Stage four – Project workflow is monitored and any further risks are identified,
Execution of registered and or mitigated as per plan.
deliverables
Stage five – Identified risks are escalated to sponsors during reporting project
Reporting on progress. Any predicted changes to project completion time or budget is
deliverables communicated.
The success or failure of risk treat plans are also reported to sponsors
and key stakeholders.
Stage seven – This stage must be a formal process because it forms the basis for best
Project close practice to learn mistakes and experiences of managing risks.
out
Microsoft project
Workzone
Clarizen
Smartsheet
Monday.com
Airtable.
Divide into pairs. Read the following article and write down notes on how you could
plan to respond to risks associated with the following:
Quality
Destructive stakeholders
Link: https://pmbasics101.com/3-powerful-risk-management-examples/
Your trainer/assessor will facilitate a discussion after you have completed the activity,
ensure to participate and share your responses.
You are to work as part of a team to manage program risk in preparation for your
assessment. At the end of each topic, you will be given an activity to complete to
support your learning. Your trainer/assessor will support you to undertake the activity
and provide your group with feedback.
During your group work you will need to:
Ensure to plan and schedule your activities appropriately and within the
timeframes allocated by your trainer/assessor.
Submit to your trainer/assessor for feedback upon completion of the activity, but
within the timeframe allocated.
This topic is all about managing program risk including managing agreed risk management plans,
reviewing progress, achieving objectives, monitoring and assessment, and responding to program
risk through authorised remedial actions.
Risk context
Reporting
Compliance/audits
Historical data
Assumptions: these statements are the basis on which the project risk is based. Such as,
“How many previous projects with similar components have been completed successfully?” or
“What expertise or prior experience does the company have in this work?”
Risk Breakdown Structure: this is a categorical listing of the major categories of risk, and it
highly specific to the industry.
Probability Impact Matrix: gives a more detailed definition of the probability and impact
structure used by the risk register. The matrix considers both factors and sets the stage for the
determination of numerical probability and impact values for each risk event.
Accuracy (or Confidence) Estimates: an analysis by the risk management team (or project
manager) of the potential deviation from the project plan. They can be as simple as
low/medium/high probabilities or as complex as statistical analysis of the probability of meeting
deadline dates
Risk Register: contains a listing of the most important risks the project faces and how the
project management team will deal with them. The risk register is usually in table form.
Activity: Research
Source a program risk management plan and review its contents. How does it differ
from a project risk management plan?
Your trainer/assessor will facilitate a discussion.
Activity: Read
A program must remain within the budget with a variance of no more than 5%.
A program must keep to the schedule including adhering to the project deadline of 25 th
September.
It is important to set these objectives so that you can review the performance results at progress
points or milestones of a program. For example, if the program is reviewed and there is over 5%
variance of the budget then you would need to initiate a risk response to deal with the variance.
In order to review progress of projects, program managers need real-time data to match against
planned outcomes. This can be accessed on a project management software dashboard and the
generation of reports. The reports can provide a snapshot of each stage of the project.
Some key variables to analyse from dashboards and reports include but are not limited to:
Accuracy in achieving milestones and deadlines (for example from a Gantt Chart).
Recording, escalating and sharing the information with respect to project managers and key
stakeholders.
Because of the dynamic risk environment, it is important that these reviews are continually carried
out and monitored so that risk responses can be initiated in a timely manner.
Change management – identifying root causes of change and executing change requests.
Project management risk – capability and capacity of project team to effectively manage
projects.
Portfolio risks – managing the program should have positive returns on investment.
Opportunity management – taking advantage of any opportunities in the market that can add
value to the program and/or organisation.
Activity: Read
Use various modes of communication to keep teams updated with project progress and
potential old and new risks.
Fix regular meeting to manage risks. This can be done face-to-face and followed up using
emails and project management tools.
Assess risk regularly as their impacts can either intensify or become low during the lifecycle of
the projects.
Using project management software to monitor and report on each individual project at
milestones or agreed dates.
A program manager will need to coordinate, track and collaborate with project managers to ensure
that strategies for monitoring risks are consistent and carried out according to the agreed
processes.
Matching organisation risk tolerance against the actual risk impact. The actual risk tolerance
can be worked out using qualitative risk analysis where the technical capability, costs and
schedule are assessed for achieving long-term program and organisation objectives.
A quantitative risk analysis includes use of tools such as decision trees to assist with working
out numerical rating to risks and activity risk assessment matrix.
Authorisation of remedial actions includes:
Having honest and open communication with program or project sponsors about actuated
risks and their impact on program deliverables and objectives.
The sponsors may agree to change request because they would rather continue with the
project as money has already been invested into it. They may agree to sponsor additional
costs or approve change requests. They can also choose to decline the change request and
stop the project because their organisations do not have the tolerance threshold for the
actuated risks. However, this can be used as a learning curve and used in management of
future projects.
The outcomes of decision must be communicated with the respective teams and actioned as
appropriate.
Change request approval and disapproval must be stored safely as it is an official document
i.e. an addendum to project contract.
Activity: Watch
confirmed risks are assigned and monitored across the program at agreed
intervals
Submit to your trainer/assessor for feedback upon completion of the activity, but
within the timeframe allocated.
For this last topic we will be looking at assessing program risk outcomes which includes
documenting program residual risk and communicating with stakeholders any transferred liability,
reviewing and analysing the program outcomes to assess the effectiveness of the risk
management methodology used, seeking and responding to feedback from relevant stakeholders
and finally documenting and recommending lessons learned.
A c k n o w le d g e th a t ris k s s till e x is t.
Communicating to stakeholders any transferred liability at the end of a program could be through
an end of program meeting using project management software reports and any further recorded
documentation (for example risk registers) to support what the risks are and why they remain.
reports or data analysis from information systems such as the risk register or risk treatment
plans
progress reports, reviews and outcomes from project meetings relating to risk management
performance.
Furthermore, there will be information from the way in which the risk management methodology
was undertaken in practice. If it was consistent across the organisation, if the processes and
systems worked effectively, what went wrong and why. To do this a program manager may need to
meet with the project managers, key stakeholders and sponsors or create a method for seeking
feedback via a questionnaire or requesting feedback.
The questions include but are not limited to:
Did the risk management methodology help with making the program/project successful?
Were all relevant risks identified, communicated and their impacts explained to key
stakeholders?
The information from these meetings or from feedback received can be used to understand what
needs to be improved or identify any gaps. For example:
The suitability of the framework, tools and techniques used to manage risk.
If the current risk management process is effective and how well it integrated across the
organisation.
If a different approach to risk management is required due to particular kinds of risk that exist
in the organisation.
To understand if the risk profile of the organisation varies from the actual risks reported.
Activity: Read
Read the following articles. These will be useful for both program and project
managers.
Questioning Techniques:
https://www.mindtools.com/pages/article/newTMC_88.htm
Managing communications effectively and efficiently:
https://www.pmi.org/learning/library/managing-communications-effectively-efficiently-
5916
Note key learnings from the articles and take any notes to summarise what you have
read and keep for future reference.
Lessons learned
The program manager can then use the
review and feedback to analyse and
document an evaluation report and
recommend lessons learned for future
programs.
Lessons learned is the knowledge that
has been collected and understood from
the program upon completion. Both the
negatives and positives of the program
can be used to ensure future programs
are improved.
a list of findings
recommendations
Activity: Watch
Watch the following video, highlighting the golden rules of knowledge management
that relate to lessons learned in project management.
Video: https://www.youtube.com/watch?v=pXEIyhwdsjQ (00:57)
Write down your key takeaways.
After watching the video take a moment to reflect on how knowledge management
can support lessons learned.
Would a wiki be a useful tool for communicating lessons learned? Research and
write down some strengths and limitations.
Your trainer/assessor will facilitate a discussion.
Residual risk.
Submit to your trainer/assessor for feedback upon completion of the activity, but
within the timeframe allocated.