Original subtitles

Hello and welcome to Session 6, Part B of PMGT 823, Project Risk Management.

We are continuing with our discussion on implementing risk responses.

Let's get started with this section together.

In this part, we will focus on documenting the execution of risk

Good documentation is critical to track what actions were taken, who was

involved, and what results were achieved.

This process helps create transparency and supports future risk management

efforts. Let's begin exploring how to capture this information effectively.

An issue log is used to document any problems or unexpected events that come

during a project.

If a new issue appears while carrying out risk responses, it gets recorded

for tracking and resolution.

This helps the team stay organized and respond quickly to anything that might

disrupt the plan.

The next important document is the lessons learned register.

A lessons learned register helps capture valuable experiences, insights, and

knowledge gained during the project.

This information can prevent similar problems in future projects and support

continuous improvement.

By updating it during risk response execution, the team builds a stronger

foundation for managing risks more effectively next time.

risk responses are confirmed the project team needs to allocate the right

resources to carry them out this means assigning qualified and experienced

people to each action along with setting the budget timeline and any needed

technical support these documents help make sure the agreed upon risk responses

are actually put into practice and the risk register which is the most

important document here is a detailed document that keeps track of individual

project risks their status, and the chosen response strategies.

As the team implements risk responses, this register should be updated to show

any changed or new information.

Keeping it current helps everyone stay aligned and aware of how risks are being

managed throughout the project.

And ultimately, the risk report provides a high -level summary of the overall

risk exposure of the project and highlights key risk trends for

As risk responses are implemented, this report should be updated to reflect any

major changes or new concerns.

Keeping the risk report current helps decision makers stay informed and take

action if needed.

Okay, in this example, Rachel is managing a hospital infrastructure

a street waterfall approach.

She identified a key risk of delays in importing a backup generator and planned

a transfer strategy to handle it through specialized contractors.

When customs clearance became an issue, Rachel logged it, escalated with

suppliers, and set up a temporary generator plan.

She documented everything carefully in the issue log, the lessons learned

register, and the risk register.

Thanks to her structured and timely documentation, the generator was

just one week later without disrupting commissioning, and her efforts were

praised in the project audit.

All right, please make sure to complete the required readings before our next

session. You should review Kendrick chapters 8 and 10 as well as PMBOK

11 .6.

Also take time to go through the presentation materials once again to

what we have learned today.

And also please remember to reply in discussion board 3 to share your

Make sure to submit quiz 4 by the deadline and finally begin working on

milestone 4 for the group project to stay on track.

And this brings us to the end of this session. If you have any questions, feel

free to reach out or post them in the discussion board.

Thank you very much again for your attention and see you in the next