A project's customer is furious. When the customer arrived at the project site, they discovered that one of their requirements was not met.
What should the project manager do?
A project's customer is furious. When the customer arrived at the project site, they discovered that one of their requirements was not met.
What should the project manager do?
When a project's customer identifies an unmet requirement, the project manager should refer to the requirements traceability matrix and analyze the requirement. This matrix is a crucial tool during the project lifecycle as it helps track the status and origin of each requirement. By examining the traceability matrix, the project manager can verify if the requirement was documented, understand its source, and determine why it was not met. This provides a factual basis for addressing the issue, ensuring a structured approach to resolving the customer's concern.
Requirement not met means it was already defined in planning during Define Requirement Process before Create Scope Statement Process. A requirment traceability matrix should be consulted to have more information on this requirment and how it is linked to other artifacts of the project.
C. Consult the scope management plan with the customer to understand the gap. Starting with the Scope Management Plan is important for clarifying whether the requirement in question was initially included in the project scope or explicitly identified as out of scope. It helps set the context and boundaries of the project, which can be crucial in addressing the customer's concern. After consulting the Scope Management Plan, the project manager may then consider referring to the Requirements Traceability Matrix and performing an analysis to further investigate the specific requirement and its status. However, starting with the Scope Management Plan is a logical and essential first step in understanding the situation and managing customer expectations.
Agreed.
I cans see the logic of your argument, in a planning phase we make a plan and then RACI matrix for the requirement, but I this phase where the product development missed a requirement, I would go backwards, and check first the lower level document, the traceability matrix to see if the requirement was there and in case who was responsible, accountable etc..etc.., and if not escalate to an higher level information the Scope Management Plan, to see if it was part, or not, of the scope. this is my thought.
you are mixing scope management plan with scope statement here. In scope / out of scope is defined in scope statement, not scope management plan. Also people marking Requirement traceability matrix as the solution, are forgetting that it just maps any particular requirement raised during requirement gathering phase, to its source / requester (who asked for what). most apt option amongst given, seems to be option A.
B. Refer to the requirements traceability matrix and analyze the requirement
voted A
Voted A
Answer B : The requirements traceability matrix (RTM) is a tool that helps track the status of project requirements throughout the project lifecycle. By referring to the RTM, the project manager can verify if the requirement was documented, approved, and if it was planned to be delivered.
The project manager should B. Refer to the requirements traceability matrix and analyze the requirement. This matrix helps track the relationship between project requirements and their sources, ensuring that all requirements are addressed. By analyzing the requirement in question, the project manager can identify the gap and determine the appropriate course of action to address it. It’s essential to communicate transparently with the customer and work towards a resolution.
First identify the specific oversight using the RTM and then review the scope management processes to understand the gap.
When the customer arrived at the project site, they discovered that one of their requirements was not met. This means requirements were already defined. Discuss and agree with the customer to implement a missing requirement is the immediate action that can be taken.
B. Refer to the requirements traceability matrix and analyze the requirement
B: The requirement traceability matrix is a table that is created to link the requirements back to their origin. The traceability basically tracks where the requirement suggestion came from, which stakeholder gave the requirement, and why it was added to the actual project. It will help to keep track of the requirements as the project is carried out.
I think you are misunderstand. Requirement traceability matrix link requirement from their origin to "deliverables". It shows that the deliverables satisfy which requirements and ensures that requirements are delivered at the end of the project. Not "origin" as you are explaining.
answer is C
Requirement Traceability Matrix helps check the fulfillment of requirement
C is answer
B is exactly suite as per stakeholder management process
I query it does not meet the requirement but not missing. Acceptable criteria is coming from scope management plan why not C
B. Requirement traceability matrix is the first document a PM should consult when a requirement is not met.