The project manager should take two actions to address the feedback from the security department about regulations that the project must comply with. The first action is to ask the team members to analyze the impact of including this regulation on the project scope, schedule, cost, quality, and risk. This will help the project manager to understand the implications and trade-offs of incorporating the regulation, and to plan accordingly. The second action is to ask the product owner to include the requirements in the product backlog, and prioritize them based on their value and urgency. This will ensure that the regulation is properly documented and communicated to the team and stakeholders, and that it is aligned with the project vision and goals. The project manager should also collaborate with the product owner and the team to determine the best way to deliver the regulation in the upcoming iterations, and to monitor and control its implementation and verification.
Option B is not a good choice, because it is not the project manager’s responsibility to ask the stakeholders about the priority of the regulation. The project manager should defer to the product owner, who is the primary person responsible for managing the product backlog and prioritizing the requirements. The project manager should support the product owner in engaging the stakeholders and obtaining their feedback and approval, but not make the decision on their behalf.
Option D is not a good choice, because it is not a proactive or timely action. The project manager should not wait until the feedback is received to ask the security department for details about the regulations. The project manager should have identified and engaged the security department as a key stakeholder early in the project, and obtained their input and expectations regarding the regulations. The project manager should also have established a regular and effective communication channel with the security department, and ensured that they are involved and informed throughout the project lifecycle.
Option E is not a good choice, because it is not a realistic or feasible action. The project manager should not ask the team members to include the requirements in the next iteration, without considering the impact, priority, and complexity of the regulation. The project manager should respect the team’s autonomy and capacity, and avoid imposing unrealistic or arbitrary deadlines. The project manager should also follow the agile principles and practices, and allow the team to self-organize and plan their work based on the product backlog and the iteration goals.
1: Project Management Professional (PMP)® Certification 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition
