The correct answers are C and D .
AgilePM treats risk management as a continuous, embedded, and collaborative activity , not as a one-time exercise done only at the beginning of the project. Risks are identified, discussed, reviewed, and responded to throughout the lifecycle using iterative planning, stakeholder engagement, feedback loops, and frequent inspection points.
Why C is correct
"AgilePM embeds risk management in processes, proactively addressing risks at multiple levels." This is a core AgilePM concept. Risk is not handled separately from delivery. Instead, it is built into the way the project works through:
* iterative planning,
* prioritization,
* collaboration between business and technical roles,
* incremental delivery,
* frequent reviews,
* and ongoing reassessment of assumptions and dependencies.
AgilePM recognizes that risks may emerge from both:
* the external environment such as regulation, price changes, or market shifts, and
* the project approach such as weak communication, poor alignment, or misunderstood priorities.
Because of this, risk management must happen at multiple levels across the project, not only in formal risk logs.
Why D is correct
"AgilePM leverages Sprint Reviews and feedback loops to surface and mitigate risks." This also strongly aligns with AgilePM. Reviews, demonstrations, and feedback events are important mechanisms for exposing:
* misalignment with business goals,
* technical integration problems,
* missing requirements,
* stakeholder concerns,
* and benefit realization issues.
AgilePM relies on iterative feedback because it helps the team identify risks early enough to respond before they become major failures. A Sprint Review, for example, may reveal that a feature is not fit for purpose, that dependencies were missed, or that stakeholder expectations were misunderstood. That is exactly how AgilePM uses feedback to reduce risk progressively.
Why the other options are not the best answers
A). AgilePM allows Mira Bachar to adjust Backlog priorities with advice from Sukra Aroon and Hira to address risks.
This is plausible in practice , because reprioritization can indeed be used to respond to risk. However, it is more of a specific situational example than a broad statement of AgilePM's overall risk approach. Since the question asks for the two statements that describe the approach itself, C and D are stronger and more directly aligned.
B). AgilePM removes all risks before execution, prioritizing avoidance over mitigation.
This is incorrect. AgilePM does not assume all risks can be removed before work begins. In fact, AgilePM accepts uncertainty as normal and focuses on:
* early visibility,
* continuous adaptation,
* mitigation,
* and learning through iteration.
Trying to eliminate all risk upfront would be unrealistic and contrary to agile thinking.
E). AgilePM assigns risk management solely to the Project Manager, Hira.
This is incorrect. In AgilePM, risk management is a shared responsibility . The Project Manager plays an important coordinating role, but risks are also surfaced and addressed by:
* business roles,
* technical roles,
* delivery teams,
* and stakeholders.
For example:
* Mira may reprioritize work to reduce value risk,
* Sukra may identify architectural or feasibility risks,
* Brinda may highlight business alignment risks,
* Hira may coordinate mitigation and escalation.
AgilePM perspective
AgilePM manages risk by making the project:
* visible,
* collaborative,
* iterative,
* feedback-driven,
* and adaptable.
Rather than depending only on formal reporting or one person's control, AgilePM spreads risk awareness across the project and uses regular events and evolving plans to keep risk under active management.
Therefore, the best two answers are:
C, D

In the context of Agile Project Management, when developing the Delivery Plan during the Feasibility phase, the two statements that best align with Agile principles are:
A: The Project Manager should include any known constraints associated with planning permission.
E: The Architecture Angels' Marketing Director should be involved in the development of the Delivery Plan.
Here's the rationale:
*A: Recognizing and accounting for known constraints such as planning permission is a key aspect of Agile. It allows for better adaptability and planning around these constraints. Including them early in the Delivery Plan helps ensure that they are considered throughout the project.
*E: Agile emphasizes cross-functional collaboration and stakeholder engagement. The Marketing Director would provide valuable insights into customer needs and market conditions, which are crucial for a successful delivery plan.

Explanation:
* C. Independent Testing
* A. Collaborative Testing
* B. Repeatable Testing
* D. Prioritised Testing
Short Comprehensive Explanation:
* Independent Testing is appropriate when someone from a different department (Finance) with no involvement in the development process conducts the testing to ensure an objective view.
* Collaborative Testing involves various stakeholders, in this case, the Sales Manager and the solution tester, working together to review and test a prototype, promoting early feedback and shared understanding.
* Repeatable Testing is used for security testing where predefined test scripts (provided by the bank) are applied to ensure the system meets specific security standards and can be repeated as needed.
* Prioritised Testing is essential when the project's stability and core functionality, such as the website's capacity to handle new features, must be confirmed before other tests are conducted to ensure the most critical aspects are addressed first.
* Again, Prioritised Testing is used to ensure that the essential requirements (Must Haves and Should Haves) are tested and validated before moving on to less critical ones (Could Haves), aligning with prioritization in Agile methodologies.
References:The Agile Project Management (AgilePM) framework and principles, as detailed in the AgilePM Practitioner documents and learning resources, guide the application of these testing concepts within an Agile project environment. These resources emphasize the importance of iterative development, stakeholder collaboration, and prioritization of work to ensure project success and alignment with business needs. Specific references to testing approaches and their application within Agile projects can be found in the official AgilePM handbook and practitioner-level training materials available through APMG International and affiliated training providers.