| Backlog | A prioritized list of Stories to be worked on. Teams continuously Estimate → Build → Validate → Re-prioritize Stories based on priority and what they learn. |
| Story | The smallest unit of work that makes up the Backlog. |
| Feature Story | A Story that delivers new user or business value through functionality. |
| Design Story | A Story for defining or validating the user experience or product behavior. |
| Estimate | A relative complexity assessment of a Story, expressed in Story Points. |
| Story Point | A unit of relative complexity, not a measure of time. |
| Pointing | The process by which the team discusses and agrees on Story Points. |
| Iteration | A recurring development cycle planned based on Velocity. |
| Velocity | The average number of Story Points completed by the team in an Iteration. |
| Volatility | A measure of how much the team’s normalized delivery capacity varies across recent Iterations. |
| IPM | A planning meeting where the team reviews and clarifies upcoming Stories and estimates them. |
| Pre-IPM | A refinement process before IPM to prepare Stories so they are ready to be estimated. |
| Bug | A Story for fixing unintended behavior in functionality that has already been implemented. |
| Chore | Necessary work that does not directly create user value. |
| Icebox | A holding area for Stories that are not yet sufficiently defined or prioritized. |
| Priority | The position of a Story in the Backlog, which indicates its relative importance. |
| Acceptance Criteria | The conditions used to verify whether a Story is complete. |
| Accept | The PM confirms that a Story meets its Acceptance Criteria. |
| Reject | A Story is returned for further work because it does not meet its Acceptance Criteria. |
| Release Marker | A product or project milestone within the Backlog. |
| Current | Stories that are currently being worked on. |
| Done | Stories that have been implemented and accepted. |