Add more context to your requirements in complex projects
Rating: 8 out of 10
IncentivizedUse 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
Likelihood to Recommend
We tried the Modern Requirements4DevOps AddIn to see if it brings a added value to our development. I have to say that I would distinguish between types of projects in which it is beneficial and in which it is probably "over engineering". Certainly, bigger development projects with higher complexity are more suitable than small and not really complex projects.
However, for the bigger projects Modern Requirements4DevOps definitely helps to deal with the complexity as it adds way more contextualisation to the various entities. It really helps to understand which requirements led to which action in a diagram or task during development. It helps to control the complexity and inform all team members along the project.
However, for the bigger projects Modern Requirements4DevOps definitely helps to deal with the complexity as it adds way more contextualisation to the various entities. It really helps to understand which requirements led to which action in a diagram or task during development. It helps to control the complexity and inform all team members along the project.
Vetted Review
2 years of experience