A customer and product delivery team meet to discuss product’s attributes, goals, expectations, ,hypothesis, and high level needs. What is a benefit of this meeting? a. The team will learn how its
Saida AdilkhanovaSAP Delivery Lead| Capgemini UKSouthampton, Eng, United Kingdom
a. The team will learn how its contribution will create product value b. It will enable team acceptance of client priorities c. It will enable the team to see the entire project in one glance d. It will enable the team to ask any questions to the customer upfront
I think it is high-level planing (visioning) and the right answer is probably A. Saving Changes...
I'm not a fan of this question as it will draw lots of responses for A & D and possibly even C. When you have such initial meetings, all three of these areas are usually covered. The only poor choice is B as the team shouldn't be accepting the client's priorities but rather understanding them.
I would agree that the best answer is A, and that it is a poorly worded question.
What is being discussed is the product architecture, which includes not only the basics of how the product functions, but also things like the business case that makes it viable, and the qualities that the customer needs to perform as intended.
I would say that C is incorrect because there is no "one glance" view of any project. There are multiple perspectives. D is still valid because asking questions is part of the reason for a discussion rather than having the customer email you a pamphlet, but the question doesn't say this meeting occurs at the beginning, and "any question" is overly broad. Saving Changes...
