Requirements management and traceability
Manage requirements from the business need to production: business cases, epics, features and stories, traced to the code and changes that deliver them.
2 min read
Requirements management, end to end
Requirements management captures what the business needs, keeps it current as it changes and proves that what was delivered matches what was asked. The last part — traceability — is what most tools lose once development starts.
From business need to task
| Level | What it captures |
|---|---|
| Business case | Why the investment is worth it, with its own authorizations |
| Epic | A large business capability |
| Feature | A deliverable part of an epic |
| Backlog item or user story | A unit of value with acceptance criteria |
| Task | The work to build it, with hours |
| Deployment | The governed change that takes it to production |
Traceability in both directions
- Forward: from a business case to the deployments that delivered it.
- Backward: from a production change to the requirement and business case behind it.
- Impact: which work is affected when a requirement changes.
- Coverage: which requirements have tests and evidence.
Where new requirements come from
New ideas can enter as project requests, be evaluated and become business cases with their authorization phases before any development starts.
How DevGob helps
DevGob keeps the chain from business case to production unbroken, and includes it in the evidence package of every change.
Read it in the documentationFrequently asked questions
What is a traceability matrix?
A table that links each requirement to the design, code, tests and releases that implement it. In DevGob those links already exist between work items, code and changes, and each change's evidence package includes its requirements.
Can business users take part?
Yes. Business cases have their own requesters and authorizers, separate from the development roles.
Must requirements be fixed before development?
No. In agile work they evolve; what matters is that each change records which version of the need it delivered.
Keep reading
DevOps with governance, on one record
DevGob plans the work and governs every change on its way to production: backlog, sprints, committee authorizations, install evidence and an audit trail.