Requirements Management Plan

Correct Answer: Review the project's change control process

The correct answer is 'Review the project's change control process'. The scenario suggests that there is a pattern of changes affecting project schedule. The project manager should act on this by reviewing how changes are controlled within the project, which includes how changes are requested, assessed and implemented. This may reveal issues with the change control process itself that may also be contributing to the schedule impact. 'Request additional resources for the project' might be a premature action as it does not directly address the pattern of changes that are impacting the schedule. 'Raise the issue to the project sponsor' could be a step if the review of the change control process does not provide any insights or solutions. Lastly, 'Adopt a new project management methodology' is a drastic action to take based purely on the information given in the question. It does not directly address the observed pattern of requirement changes.

Correct Answer: Requirements Attributes

Requirements traceability is a critical aspect of requirements management. It involves tracking the relationships and dependencies between requirements, as well as their origins and evolution throughout the project lifecycle. Traceability helps ensure that all requirements are properly addressed, tested, and verified. The key component that should be included in the Requirements Management Plan to maintain requirements traceability is Requirements Attributes. Attributes such as a unique identifier, source, priority, and status can be assigned to each requirement. These attributes enable the project team to track and manage requirements effectively, ensuring that they can be traced back to their origins and linked to other relevant project elements. Requirement Decomposition involves breaking down high-level requirements into more detailed, lower-level requirements. While this is an important aspect of requirements management, it does not directly address traceability. Requirement Prioritization involves assigning importance or urgency to requirements based on stakeholder needs and project objectives. Although prioritization helps in decision-making and resource allocation, it does not specifically focus on maintaining traceability. Requirement Validation is the process of ensuring that the documented requirements meet the stakeholders' needs and expectations. While validation is crucial for ensuring the quality and accuracy of requirements, it does not directly contribute to traceability.

Correct Answer: Review the Requirements Management Plan

The best action for the project manager to undertake first is to ‘Review the Requirements Management Plan’. This is because the Requirements Management Plan contains the procedures for how new requirements will be analysed, tracked, and managed. Thus, it should serve as a guide to tackle the new requirements. Going straight to 'Incorporate the new requirements immediately' can potentially disrupt ongoing tasks and may not account for all project impacts. Simply 'Rejecting the new requirements' without thorough analysis may lead to loss of client trust and missed project opportunities. 'Sending an email to the stakeholders' is not an inaccurate answer; however, this should only happen after a thorough analysis of the new requirements is done, which starts with reviewing the Requirements Management Plan.