Explain what a user story is in Agile and provide an example.

• A. A user story is a detailed technical specification; example: 'As a system, I must...'
• B. A user story is a test case
• C. A user story is a short, user-focused description of a feature; example: 'As a student, I want to export my project to PDF so I can share it easily.'
• D. A user story is a project schedule

Answer: (C)

A user story in Agile is a short, user-focused description of a feature that captures who benefits, what they want, and why it matters. It is lightweight on details to keep the team focused on user value and to spark conversation, with acceptance criteria added later to define when it’s done. For example, “As a student, I want to export my project to PDF so I can share it easily” clearly identifies the user (a student), the desired capability (export to PDF), and the benefit (easy sharing). This format helps prioritize work in the backlog and guides discussion between the user, product owner, and developers without getting bogged down in implementation specifics. It’s not a detailed technical specification, a test case, or a project schedule, which are about how something is built, verified, or timed rather than describing a user’s need and the value delivered.