CBAP Question 64

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose C1

  As a [user role], I want to [achieve a goal/objective], so that [I can get a specific benefit/value]. USER STORIES ALWAYS RELATED TO VALUE AND SOLUTION

• Chose D1

  10.48.2 Description User stories capture the needs of a specific stakeholder and enable teams to define features of value to a stakeholder using short, simple documentation. They can serve as a basis for identifying needs and allow for the prioritizing, estimating, and planning of solutions. A user story is typically a sentence or two that describes who has the need addressed by the story, the goal the user is trying to accomplish, and any additional information that may be critical to understanding the scope of the story. With a focus on stakeholder value, user stories invite exploration of the requirements by promoting additional conversations with stakeholders and grouping functional requirements for delivery.

• Chose C1

  The correct answer is C. Stakeholders' objectives are described to identify the requirements that the solution will need to support. The user stories approach focuses on capturing stakeholders' objectives and goals to define the requirements for the solution. It emphasizes understanding what stakeholders aim to achieve and ensures that the solution aligns with their needs. This method is widely used in Agile frameworks, where user stories are written from the perspective of the end user to describe desired outcomes rather than technical details.