Categories: Requirements

This guide describes the most fundamental parts of component capabilities. It also includes a flowchart of component capabilities updates and a list of attributes sometimes mistaken for component capabilities.

This guide describes how to handle epics in streams. It includes examples of epic descriptions and information about the epic definition, grooming, and change management.

This guide describes how to handle features in streams. It includes examples of feature descriptions and information about the feature definition, grooming, and change management.

This guide describes how to handle system requirements and system epics. It includes descriptions and information about the system requirement / system epic definition, workflow, grooming, and change management.

Product capabilities describe what the product “can do” for anyone who wants to understand its capabilities. They represent the product's property and are updated throughout its lifecycle through multiple releases.

The requirements process describes how the market opportunities and system requirements are received from Portfolio and Product Management and transformed into epics, features, and stories.

This guide describes how system requirements in Decision Focus are broken down into system epics, epics and features in Azure DevOps (ADO).

A system requirement review intends to improve the quality of the requirements. It applies both to system requirements and technology requirements.

This guide describes the different states of Azure DevOps (ADO) work items. Consistent work item state transitions are essential to enable consistent follow up on status.