Azure DevOps vs. Azure DevOps Server vs. IBM Rational ClearQuest

Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.

Incentivized

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

If you are familiar with IBM Rational Suite products, RequisitePro will add up due to the synergy between other components. Beyond that, if your business is not structured to an adequate development methodology or lacks the degree of maturity or necessary resources, probably RequisitePro does not add much value. If you work with developers in the requirements analysis, they probably prefer to use an SVN repository.

Incentivized

• Utilize Git as a repository to share work between multiple users
• Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
• Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
• Track status of each task
• Integrate with Git to utilize branches, merging, approvals, history, etc.

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

• Capability to query bugs on multiple criteria and export it to csv for triages.
• Simple and intuitive user experience and clearly planned defect life cycle
• There are other features like assigning the defect to pull request, clearly explaining defect by attaching screenshots, detailed description etc
• If you are using other IBM tools for requirements documentation, this tool integrates very well

Incentivized

• I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
• The wiki is not the prettiest thing to look at, so it could have refinements there.
• It could improve the search slightly better.

• 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

• Performance can be an issue. Make certain the server is sized properly
• There is a large difference in capability of the Thick Client Version compared with the web based version. Make certain each job function has proper access to be able to do what is required of them.
• Learning curve is not too steep, but would suggest having someone with experience setup the repository. Highly suggest getting a contractor to assist to get the repository up and running.

Incentivized

I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.

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

Most likely as it's one of the powerful tools in the organization. We needed this tool to track all the process related documentation and also to capture signatures.

Incentivized

It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).

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

Please keep in mind that this all has to do with you you customize the user interface. It becomes very easy to house all of your requirements, but it may and can make life difficult for you if you do not think ahead of how you want the app to work and house your data

Incentivized

When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.

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

IBM has good support and knowledge base. With the wealth of information on their site and the support desk, we were able to quickly resolve issues. It is smart to build up a COE and a group that manages the software otherwise it is quick to be able to lose the knowledge as team members are assigned different duties

Incentivized

Was not part of the process.

Incentivized

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

Incentivized

It was pretty simple.

Incentivized

Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.

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

IBM clearquest would the BEST option if you are looking for managing change requests, managing project workflows, generating reports on status of requests. The reason being: cost, cost and cost. It almost handles everything that you would need for your project including bug tracking unless you want something really fancy (like HP QC) with a higher cost that supports a wide variety of needs which you might need to evaluate based on your project needs. For example, if you would be really making use of all those additional features provided by HP Quality Center. To be honest it depends on your project size, the skills of team members and of course budget!

Incentivized

• We have saved a ton of time not calculating metrics by hand.
• We no longer spend time writing out cards during planning, it goes straight to the board.
• We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.

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

• IBM Rational ClearQuest has provided a workflow that works without unique software methodology. As a result we deliver complete software products to our clients in a 6 to 8 week development time frame.
• As a result of our highly customized implementation, we have 8 resources supporting IBM Rational ClearQuest. Three of the resources are full time configuration management staff that administer and support the tool set and the other 5 are from the testing group that handle ClearQuest user support issues in addition to their testing duties.

Incentivized