According to the PMBOK Guide, risk management is an iterative process that should be performed throughout the project life cycle1. Agile projects also follow this principle, as they use frequent iterations to deliver value and respond to changes2. Therefore, the project manager should follow the risk management process while ensuring that risks are identified, analyzed, and managed during each iteration. This will help the project manager to monitor and control the project risks effectively and proactively. The other options are incorrect because:
A. There is no such thing as an agile risk manifesto. The Agile Manifesto is a set of values and principles that guide agile software development, but it does not specifically address risk management3.
B. Asking the product owner to act as a risk manager is not a good practice, as it may create role confusion and conflict of interest. The product owner is responsible for defining and prioritizing the product requirements, not for managing the project risks4. The project manager should collaborate with the product owner and other stakeholders to identify and manage the project risks, but not delegate this responsibility to them.
C. Implementing the role of an agile risk manager is not necessary, as the project manager already has the responsibility and authority to manage the project risks. Creating a separate role for risk management may create duplication of work and communication barriers. The project manager should leverage the skills and knowledge of the project team and other stakeholders to perform risk management activities, but not create a new role for this purpose. References:
1: PMBOK Guide, 6th edition, Chapter 11, Section 11.1, page 397
2: PMBOK Guide, 6th edition, Chapter 3, Section 3.8, page 52
3: Agile Manifesto
4: PMBOK Guide, 6th edition, Chapter 9, Section 9.3.2.2, page 286
: PMBOK Guide, 6th edition, Chapter 9, Section 9.1.2.1, page 273
