Glossary

Agile And Software
Project Glossary

Plain-English answers to the terms teams use every day, from epics and user stories to acceptance criteria, PRDs and sprints. Each one starts with the short answer.

Terms

Start With The Question
You Were Asking

Epic vs storyWhat Is the Difference Between an Epic, a Story and a Task?An epic is a large body of work that usually spans several sprints and is split into user stories.Read the answer
User storyWhat Is a User Story in Agile?A user story is a short, plain-language description of something a user needs, written from their point of view.Read the answer
Acceptance criteriaWhat Are Acceptance Criteria?Acceptance criteria are the specific, testable conditions a user story or feature must meet for the product owner to accept it.Read the answer
Acceptance criteria vs DoDWhat Is the Difference Between Acceptance Criteria and the Definition of Done?Acceptance criteria are the conditions one specific story must meet to do what the user needs.Read the answer
PRDWhat Is a PRD (Product Requirements Document)?A PRD, or product requirements document, describes what a product or feature should do, who it is for and why it matters, without dictating how engineers build it.Read the answer
Story pointsWhat Are Story Points in Agile?Story points are a relative unit agile teams use to estimate how big a backlog item is, combining effort, complexity and uncertainty into one number.Read the answer
Story points to hoursHow Many Hours Is a Story Point?There is no fixed number of hours in a story point.Read the answer
SprintWhat Is a Sprint in Agile?A sprint is a fixed-length timebox of one month or less in which a Scrum Team works toward one Sprint Goal and creates a usable Increment.Read the answer

Agile And Software Project Glossary

Start With The Question You Were Asking

Agile And Software
Project Glossary

Start With The Question
You Were Asking