A state-of-the-art product was delivered at the end of a project life cycle. However, the customer claims the product was not designed to specifications.
What should the project manager have done to avoid this issue?
A state-of-the-art product was delivered at the end of a project life cycle. However, the customer claims the product was not designed to specifications.
What should the project manager have done to avoid this issue?
To avoid the issue where the product was not designed to specifications, the project manager should have ensured that the customer's requirements were captured accurately to meet the customer's standards. Properly documenting and understanding the customer's needs and specifications is crucial to delivering a product that meets their expectations. This involves thorough requirements gathering, validation, and ongoing communication to ensure that the final product aligns with what the customer specified.
Its mentioned that product is delivered at the end of project life cycle, which means predictive isnt it? So "C" will be best answer.
Its a predictive scenario. The Scope Management with its respective processes of Collect Requirements Process and Validate Scope Process would have handled this.
Selected B. C suggests that requirements were captured once and it is not sufficient in my opinion.
I will take B. There was no mention of the methodology and also no mention that any requirements were missed during gathering. Sprint reviews (demo) would have prevented this situation
customer claims the product was not designed to specifications - This clearly indicates that the customer was not involved in the iteration reviews. So, it should be B
C. The customer's requirements should have been captured in order to meet the customer's standards.
my answer is C
I will go for B This is end of project life cycle. So clearly customer didn't talk on specification during iteration reviews. Secondly, the requirement was clear unless it is stated otherwise in question
I will go with C- The customer would have noted the wrong design specification during the iteration review and pointed out the issue before the product is released. Option D is wrong since it assumes the requirement was wrongly designed
it is predictive project (key here is the deliverables come after end of tge project)
Picked C
C. The customer's requirements should have been captured in order to meet the customer's standards
C. The customer's requirements should have been captured in order to meet the customer's standards
voted c
C. Project manager got specifications from the customer. He has to deliver what the customer wants, period
C is correct. No need to meet supplier standards. The retro meeting is with team not with the customer.
Delivery at the end of a project lifecycle and not at the end of an iteration means predictive. If it was Agile, the issue would've been addressed at one of the Iteration review sessions.