A project sponsor has requested a trend analysis of all risks that the project has monitored over the past 12 months. What should the agile project manager do?

The correct answer is A. Extract this from the project risk register tracking tool and issues log. To perform a trend analysis of monitored risks, the agile project manager should extract the necessary data from the project risk register and issues log.

Submitted by asante_acc· Apr 18, 2026Process

Question

Options

AExtract this from the project risk register tracking tool and issues log
BRefer the sponsor to the contract document
COrganize a stakeholder meeting to brainstorm on general project risks
DShare the annual report with the sponsor

How the community answered

(38 responses)

A
74% (28)
B
8% (3)
C
16% (6)
D
3% (1)

Why each option

To perform a trend analysis of monitored risks, the agile project manager should extract the necessary data from the project risk register and issues log.

AExtract this from the project risk register tracking tool and issues logCorrect

The risk register is the primary document where all identified risks, their status, and mitigation plans are recorded and tracked over time, making it the definitive source for trend analysis of risks. The issues log also provides data on risks that have materialized, contributing to a comprehensive trend analysis.

BRefer the sponsor to the contract document

The contract document primarily outlines agreements and terms, not a detailed, historical record of project risk monitoring and trends.

COrganize a stakeholder meeting to brainstorm on general project risks

Organizing a brainstorming meeting generates current risks but does not provide a historical trend analysis of risks monitored over the past 12 months.

DShare the annual report with the sponsor

An annual report might summarize risks, but it is not the detailed, dynamic source for raw risk data and trends over the past year like the risk register.

Concept tested: Risk monitoring and reporting

Topics

#Risk Management#Trend Analysis#Risk Register#Information Management

Community Discussion

Dervla O.Dec 27, 2025

A is correct because the risk register and issues log are exactly where historical risk data lives, and trend analysis means looking at how those risks evolved over time. C is a trap because brainstorming new risks does nothing for a trend analysis of risks already monitored. D is too vague and B is a non-starter since contracts have nothing to do with tracking monitored risks. When you see trend analysis in the stem, train yourself to look for the option that points to existing tracked records, not new conversations.

Mateus R.Jan 20, 2026

Think of it like a farmer asking for the last year of weather patterns to plan the next season. You wouldn't gather everyone to brainstorm about rain or point them to the land deed, you would pull out your almanac and your daily journal to show the actual history. In project terms, that almanac is your risk register tracking tool and the journal is your issues log, which is exactly what the sponsor needs for a trend analysis. Option C is the tempting distractor because brainstorming sounds agile and collaborative, but the sponsor specifically asked for historical data on monitored risks, not new ideas.

Prof. SaraDec 20, 2025

I first leaned toward C because brainstorming with stakeholders sounds like a collaborative agile move, but a trend analysis needs historical data, not new conversation. That is when I realized A is correct because the risk register and issues log are exactly where 12 months of monitored risk data lives, making them the only source that supports an actual trend review.

Bao N.Jan 4, 2026

A is the right call but the agile framing almost made me second-guess it since you don't see risk registers talked about much in agile prep materials. D is the trap because it sounds like something a sponsor would want, but a generic annual report won't have the risk-by-risk trend data you need from the register and issues log.

Full PMP Practice