Add more context to your requirements in complex projects
Use Cases and Deployment Scope
We used Microsoft Azure DevOps to manage the development of digital products. In the transition from design and concept to development, it is very important to define the right requirements. Therefore we used the Microsoft Azure DevOps AddIn Modern Requirements4DevOps to support our Requirements Engineering, and subsequently the usage of these requirements along the development and quality assurance processes. What we in general experienced is that the individual entities (requirements, documents, tasks) are better integrated.
Pros
- Smart Documents
- Building a connection between individual entities (requirements, documents, tasks, tests)
- Requirements Management and Reporting
Cons
- forms could be transferred into in line fields to allow in line maintenance of data
- make window management of diagram builder more flexibility to make more space to build diagrams
- I would wish that the performance is a bit better sometimes, loading times can be quite long in some cases
Most Important Features
- Smart Docs
- Diagram
- Baseline (it is amazing to have the ability to reuse requirements)
Return on Investment
- Better communication --> thus less misunderstandings
- More Transparency about requirements --> adds context and helps to build a common understanding
- Traceability of Requirements --> we used the baseline also to look into the history of requirements to understand how certain requirements have changed
Alternatives Considered
Azure DevOps Server
Other Software Used
Figma, Miro, Azure DevOps Server, MURAL, Stormboard
