Exam PMI-ACP topic 1 question 142 discussion

C. Conducted an end-of-phase demonstration Explanation: Customer Feedback: An end-of-phase demonstration allows the customer to see the product in action and provide immediate feedback, ensuring that the product meets their expectations and requirements. Validation: This demonstration serves as a validation step to confirm that the product aligns with the customer's needs and any deficiencies can be identified and addressed before the final release. Transparency: It promotes transparency and keeps the customer informed about the progress and state of the product, reducing the likelihood of surprises or dissatisfaction upon release. Iterative Improvement: Conducting demonstrations at the end of each phase allows for iterative improvements based on customer feedback, leading to a more refined and satisfactory final product.

A. Project sponsor approval: While seeking approval is important, it doesn't necessarily validate whether the product meets the customer's needs. Relying solely on this might overlook issues with the actual functionalities. C. End-of-phase demonstration: Demonstrations can showcase the product's features, but they might not reveal underlying inconsistencies with the customer's expectations. A thorough review of requirements goes beyond functionality and delves into the intended purpose and value for the customer. D. Retrospective for validation: Retrospectives are valuable for evaluating processes and learning from past experiences. However, they typically occur after releasing the product and wouldn't prevent the initial customer dissatisfaction in this scenario.

There is a need to demo the end of the phase to the customer

C = correct. B = wrong. What if the project is huge? It is a waste of time to take e review of ALL requirements. The demo is a better option (C).

Vote B

Changing my answer to C.

I am voting for B.

i vote C

I choose C

C - Demo is necessary to get customer feedback. If demo was performed before release, customer would have identified deficiencies.

Option C sounds more like waterfall approach, Option B for me is the best answer.

Working software is one of the best way to engage the customer. Then C.

C looks like the best answer. Customer collaboration is better then comperhensive documentation despite its are 2 different values :) And this was not Scrum definetly :)

I go with C

I put it in B again. many review is more correct.

My answer is C. Retrospective is not to validate project deliverables