Azure DevOps Server vs. Modern Requirements4DevOps

Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.

Incentivized

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.

Incentivized

• Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
• Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
• Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.

Incentivized

• Smart Documents
• Building a connection between individual entities (requirements, documents, tasks, tests)
• Requirements Management and Reporting

Incentivized

• Can add more build templates for specific technology requirements
• Can have more features in dashboards which can help dev teams stream line their tasks and priorities
• Can have raise alarm feature in case of any sort of failure in devops pipeline execution

Incentivized

• 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

Incentivized

Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.

Incentivized

For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.

Incentivized

I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus

Incentivized

Do research beforehand and, if possible, do a trial run before implementing into production environment.

Incentivized

In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!

Incentivized

Modern Requirements4DevOps is an AddIn for Azure DevOps Server (Microsoft Azure DevOps) and extends the native features of Azure DevOps in the area of Requirements Engineering, Requirements Management and Reporting. Azure DevOps already contains tons of valuable features. However, for bigger and more complex projects Modern Requirements4DevOps extends Azure DevOps by further features. Thus we used both products alongside.

Incentivized

• It has streamlined the pipeline and project management for our agile effort.
• It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
• The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.

Incentivized

• 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

Incentivized