User Story Skills

Question 1

Acceptance criteria

Answer 1

a set of statements, each with a clear pass/fail result, added to a user story.

Question 2

Sign-offs

Answer 2

when user stories are “signed-off,” they become a contractual obligation between the requester and provider. Sign-offs are controversial.

Question 3

Version controlled repository

Answer 3

user stories can be kept in a version controlled repository to manage scope. This helps with versioning of documents.

Question 4

User Story

Answer 4

An explanation of a feature that helps translate technical requirements into easy-to-understand ideas. A user story describes the functionality that a business system should provide so that it can be developed. It is often called a ticket or work item. The format is “As a…. I want to… So that I can…”

Question 5

Use case

Answer 5

A use case identifies, defines, and organizes the system requirements from the perspective of a user.

Question 6

INVEST checklist

Answer 6

independent, negotiable, valuable, estimable, small, testable.

Question 7

Definition of Done (DOD)

Answer 7

set of guidelines that dictates everything a team is required to do before they can call the work truly done.