Personas can help to:
(choose the best answer)
A. Understand the needs of a set of users.
B. Formulate hypotheses about product value.
C. Understand market potential.
D. Discover key buying triggers.
E. All of the above.

Which of the following statements is true about the Product Vision?
(choose the best answer)
A. It evolves as the Scrum Team learns more about customers and their needs.
B. It is the shared responsibility of the Scrum Team to develop and evolve.
C. It must be completely free from discussions about strategy technology choices.
D. All of the above.
E. None of the above.

If quality assurance work does not occur as part of the development work within a Sprint, which of the following statements are true?
(choose the best three answers)
A. The next Sprint may be interrupted when quality issues are encountered.
B. The project manager cannot effectively update the plan.
C. The indication of progress on the Product Backlog is not transparent.
D. The Product Owner may still decide to release the product.

Which of the following might be considered when ordering Product Backlog items?
(choose all that apply)
A. Value of Product Backlog items.
B. Cost of implementation.
C. Dependencies between Product Backlog items.
D. Dependencies to other products.
E. Cost of delay.

What is the role of the Product Owner in crafting the Sprint Goal?
(choose the best answer)
A. The Product Owner must work with stakeholders to set each Sprint’s Goal.
B. The Product Owner has no role in it. This is the Developers responsibility.
C. The Product Owner defines the scope for a Sprint and therefore also the Sprint Goal.
D. The Product Owner collaborates as a member of the Scrum Team to define a Sprint Goal.

You started measuring product feature usage in your last release. You are surprised to learn that a sizable percentage of the features you thought were very important are never or rarely used.
Which of the following actions could you take to further evaluate this unexpected result?
(choose all that apply)
A. Spend more time talking to Users to identify the impact they seek.
B. Disable the features that have never been used and listen for feedback.
C. Run experiments to increase your understanding of what customers find valuable.
D. Examine whether the rarely used features solve the intended problem.