Can be extended with the following solutions:
- Epic Hypothesis Statement (EPS) (783b1d3c-edd9-49ae-9952-5cb8eb011a25)
- Lean Business Case (LBC) (1a187fc1-5375-4b6f-b994-ffc74651c666)
- Work Estimated Cost (e37f8490-a78a-4b38-899d-cecf881d8147)
The solution enables a new Requirement object and it's connections to Work Items such as Portfolio Epics, Epics (Capabilities) and Features.
A Requirement entails defining the system's intended characteristics and functionality to meet user needs. It comprehensively depicts how the system should respond to specific commands, outlining its features and meeting user expectations. It can be used as a separate backlog of Requirements, where you track the details and the status of its accomplishment, as well as a list of Requirements of a specific Feature, Capability or Portfolio Epic.
In Epic Hypothesis Statement (EHS) and Lean Business Case (LBC) solutions, it's used as a list of Non-Functional Requirements (NFRs). You can rename it into NFRs using Terms to match the terminology
Within the Requirement view, you will find additional tabs that enable you to establish connections between a Requirement and various work items such as Portfolio Epics, Epics (Capabilities), and Features. It is possible to link the same Requirement to multiple Portfolio Epics, Epics (Capabilities), and Features.
On a Portfolio Epic, Epic (Capability), and Feature view, you will find a list of associated Requirements.