The correct answers are A and E .
In AgilePM, effective risk management depends on shared responsibility, continuous awareness, and proactive behaviour across the whole team. Risk is not something handled only by one role, one document, or one event. It is woven into the way the team works every day.
Why A is correct
“Team members should adopt a collaborative mindset, sharing responsibility for identifying and mitigating risks.”
This aligns strongly with AgilePM. Risks emerge from many areas:
Because of that, the best way to manage risk is for the team to work collaboratively and raise concerns early. Different people see different risks:
Mira may see value or prioritization risk,
Sukra may see architecture or integration risk,
Hira may see coordination or dependency risk,
Wanida may see compliance risk,
Developers may see delivery feasibility risks.
AgilePM encourages a culture where risks are surfaced openly and addressed together rather than left to a single person.
Why E is correct
“Risk management should be proactive and part of daily activities, not a separate process.”
This is also a core AgilePM principle. Risk management is most effective when it is:
continuous,
visible,
built into team discussions,
and handled as part of normal delivery activity.
That means risks should be considered during:
planning,
backlog discussions,
reviews,
daily collaboration,
dependency conversations,
and stakeholder feedback.
AgilePM does not treat risk as something only reviewed in occasional formal meetings. The team should be alert to emerging issues and respond before they become major problems.
Why the other options are incorrect
B. Hira should have sole responsibility for managing all risks with clear accountability.
This is incorrect. Hira, as Project Manager, has an important role in coordinating risk management, but AgilePM does not place all risk responsibility on one person. Risk management is shared across business, technical, and delivery roles.
C. Developers should resolve all risks collaboratively and promptly without escalation.
This is incorrect because some risks should be escalated. AgilePM encourages teams to resolve issues at the right level, but not to avoid escalation when broader decisions, sponsorship, governance, or cross-team intervention are needed.
D. Sukra Aroon should handle all technical risks independently to ensure the solution is fit for purpose.
This is incorrect because even technical risks often require collaboration. Sukra contributes architectural leadership, but technical risks may affect priorities, cost, compliance, usability, and business outcomes, so they should not be handled in isolation.
AgilePM perspective
AgilePM supports team behaviour where:
everyone is alert to risk,
risks are discussed early,
people collaborate across roles,
escalation happens when needed,
and risk thinking is part of everyday delivery.
So the two statements that best describe appropriate team behaviour for effective risk management are:
A, E
