CAPMEasy

CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Question 44 of 67 in Demonstrate an understanding of business analysis (BA) roles and responsibilities

Pick an answer below — you'll get the explanation instantly, no signup.

What is a 'user story' in the context of business analysis on agile projects?

Show answer & explanation

Correct answer: A short, simple description of a feature from the perspective of the person who desires it: 'As a [user], I want [goal] so that [reason]'

Explanation

User stories are the primary requirements artifact in agile BA work. The format 'As a [type of user], I want [feature] so that [benefit]' keeps requirements user-focused, brief, and connected to business value.

**Why not A:** A narrative biography of each user is a user profile or persona, not a user story. User stories are short, structured descriptions of desired functionality in the format "As a [user], I want [goal] so that [reason]" — they are concise and action-oriented, not biographical narratives.

**Why not C:** A formal requirements specification approved by management describes a traditional requirements document (BRD or SRS), not a user story. User stories are intentionally lightweight, informal artifacts designed for agile collaboration, not formal management-approved specifications.

**Why not D:** A test script describing how users should test the system is a test case or UAT script, not a user story. User stories describe what users want and why, serving as the basis for development. Test scripts describe how to verify the implementation works correctly.

Key Concept

This question covers Demonstrate an understanding of business analysis (BA) roles and responsibilities under Demonstrate an understanding of business analysis (BA) roles and responsibilities (Business Analysis Frameworks).

All 1,500+ CAPM questions are free