Timedora
Free Online Flashcard Deck

5 Risk Registers and Ongoing Monitoring Free Online FlashCards

Study 5 Risk Registers and Ongoing Monitoring with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

What is a project risk register?

Back

A shared record of project uncertainties, their potential effects, assessments, owners, and planned responses.

02
Front

What structure makes a risk statement useful?

Back

State the cause, uncertain event, and possible effect on an objective as distinct parts of the risk.

03
Front

What information commonly belongs in a risk register?

Back

Common fields include category and affected objective, likelihood, impact, priority, owner, response actions, trigger, contingency, status, trend, review date, and notes.

04
Front

What is the risk owner's responsibility?

Back

The risk owner is accountable for monitoring the risk and coordinating its response.

05
Front

What is a risk trigger?

Back

A trigger is an observable sign that a risk may be approaching or has occurred; it indicates when to review or activate a response.

06
Front

Why is a dated shipment warning a better trigger than “supplier delay”?

Back

“Supplier has not confirmed shipment by 15 May” is more useful because it is specific and checkable; “supplier delay” is vague.

07
Front

How should risk-response actions be made trackable?

Back

Give each action an owner and target date, then update its status during reviews.

08
Front

How do risk owners differ from action owners?

Back

The risk owner oversees the risk and response; action owners complete particular tasks.

09
Front

What should an ongoing risk review check?

Back

At planned intervals and after significant changes, check whether risks remain valid, new risks have emerged, triggers are near or reached, and actions are on track.

10
Front

Why use consistent criteria when reassessing risks?

Back

Use the same agreed criteria when reassessing likelihood and impact so that changes in ratings are meaningful.

11
Front

What determines how often a risk should be reviewed?

Back

Set review frequency to fit the project's pace, uncertainty, and risk level; high-exposure or fast-changing risks may need more frequent checks.

12
Front

How should a project manage a risk that has happened?

Back

Once a risk happens, it is an issue. Record and manage the actual problem, while retaining any remaining uncertainty as a risk if appropriate.