Understanding User Stories and Requirements

User Stories are not equivalent to product requirements or specifications. Instead, they are broken down into small scopes that add or change functionality. Essentially, user stories serve as work instructions for a specific period.

Stories as Artifacts

• Planning-relevant backlog items
• Managed and documented in a Backlog Management Tool
• Business-focused
• Reference requirements and rules
• Include acceptance criteria/tests

Work Packages as Artifacts

• Planning-relevant backlog items
• Managed and documented in a Backlog Management Tool
• Architectural- or technical-focused

Requirements and Business Rules

• Specifications of the final product
• Versioned and change-tracked in a Requirements Management Tool
• Traced by other artifacts
• Implemented and fulfilled through stories