ISD - topic 2 - User Story

What is a user story?

• A detailed technical document

• A small unit of work told from the user's perspective

• A system description

Who can write a user story?

• Only the Product Owner (PO)

• Only the Business Analyst (BA)

• Anyone on the team

When should a user story be written?

• Only during the initial phase of the project

• When a requirement is raised (anytime)

• Only after the project is completed

In which type of projects are user stories typically used?

• Traditional projects

• Agile projects

• Waterfall projects

What is the standard format of a user story?

• WHO - WHAT - WHY

• WHAT - HOW - WHY

• WHO - HOW - WHAT

How do user stories differ from use cases?

• User stories have a larger scope than use cases

• Use cases have a larger scope than user stories

• They are the same

Who typically writes acceptance criteria?

• Only Developers

• Only the Product Owner

• Business Analyst and the project team

When should acceptance criteria be written?

• Before the user story is added to the sprint backlog

• After the user story is completed

• Only during the testing phase

What are the 3Cs of a user story?

• Card, Conversation, Confirmation

• Card, Communication, Confirmation

• Card, Collaboration, Confirmation

What is a user persona?

• A technical description of the system

• A fictional representation of the user

• A summary of project requirements