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.
Discuss and agree with the customer to implement the missing requirement
B.
Refer to the requirements traceability matrix and analyze the requirement
C.
Consult the scope management plan with the customer to understand the gap
D.
Analyze the benefits management plan and implement the needed change
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.
The scope management plan collects requirements from whom the project is going to deliver value to, (the customer) if its not a high level requirement, then C will be the answer. If its a high level requirement, then it will be B........it just said a requirement is missing, and he or she is mad, so I would have to pick C
requirements traceability matrix will link the requirement and where it came from and will influence scope. If the customer required a certain requirement, it will be there, and it can be studied.
Requirement not met means it should be in requirement traceability matrix as defined requirement so need to revisit the document again.Answer should be B
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.
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: 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.
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.
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.
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
achacyrille
Highly Voted 1 year, 8 months agocrypto_dreams_medellin
Most Recent 2 weeks agocrypto_dreams_medellin
2 weeks agocrypto_dreams_medellin
2 weeks agoZubair1
3 weeks, 1 day agoPragati06
2 months agosweety433
5 months, 2 weeks agoakashushi007
6 months, 1 week agohoomz
9 months, 1 week agokraze29
10 months, 1 week agoBuviD
10 months, 3 weeks agoDeeski
11 months, 1 week agohonidt
9 months agoGabMonterey
11 months, 3 weeks agoTuanit
1 year, 1 month agoPranav2204
1 year, 2 months agosambeth
1 year, 2 months agoSreeSu
7 months agoRoberto_B
1 year, 1 month agoPrashantpra99
1 year, 2 months agoAsakthi
1 year, 3 months ago