Microsoft Azure DevOps Competitors and Alternatives

Get our free report covering Atlassian, Microsoft, GitLab, and other competitors of Microsoft Azure DevOps. Updated: July 2021.
521,189 professionals have used our research since 2012.

Read reviews of Microsoft Azure DevOps competitors and alternatives

RobertCampbell
Product Manager at a insurance company with 10,001+ employees
Real User
Top 20
Great for collaboration, very stable, and extracting data is straightforward

What is our primary use case?

We are using the product for general task management, largely. From a software development community perspective, obviously, we use the task management piece - the foundation to what leads into the development and the CI/CD pipelines and et cetera. Outside of that, it varies widely. At its very core, it's task management, however, then it's used by various functional areas within the company. For example, we have contracting and procurement that utilize it. And we have marketing that uses it and security, IT security, audit, compliance. Various functional areas across the company use Jira. We… more »

Pros and Cons

  • "You no longer need to email people. You can mention them right in Jira and have conversations there."
  • "In Jira, say on the team, no matter the methodology, it doesn't matter what I'm practicing, if I am using the tool for a while and I've compiled some sort of history. If I want to change my workflow, say my team is today using to-do in progress done, and tomorrow, I decide I want to use to-do in review and done, and I apply that new workflow, I have just now effectively lost all of my histories in terms of reporting."

What other advice do I have?

We're just customers and end-users. I upgraded the application back in December, so we're on 8.13 right now. While we're currently on-premises, one of the things that were on my to-do this year was to consider moving to the cloud, which is something that we are very interested in doing. Currently, we're using the Jira Data Center. Our company has barely scratched the surface of the power of Jira in my personal opinion as they've just largely tried to do a bunch of customization. There was no governance set when I first joined the organization. People were just allowed to create whatever they…
AL
Implementation Consultant at a healthcare company with 201-500 employees
Consultant
Top 20
Useful for seeing if we are on target for work, but it is not intuitive and should have easier and user-friendly reporting without having to use the Excel add-in

What is our primary use case?

It is used to track any enhancements or new integrations. We have integrations from mainframe systems to RESTful services. We also have a few SOAP integrations. Essentially, we use the feature level of Rally to document what the interface is and then the engineers make the user stories within the feature to represent the tasks that they need to do to complete the interface, which includes everything from making the design document to the activities that they do in IIB, such as deploying the code to production. Our version has probably been updated within the last three months.

Pros and Cons

  • "We use the roadmap features, and we're getting better at using dates to use the roadmap so that we can see if we're on target for work."
  • "What I don't like about it is that it is really hard to find old work to reference information and use the reporting section of the application in terms of trying to analyze trends. If I am trying to find out which interfaces took this long and I want to compare and measure improvement from one quarter to another quarter, the reporting mechanism within Rally is very troublesome. They have an Excel plugin that you're supposed to use, but you literally have to pull the raw data out before you can do the analysis. You can't do it within Rally, and if you can, it is a secret, and I don't know how to do it. It should have better, easier, and user-friendly reporting without having to use the Excel add-in. It is very clunky. There is a lot of data in there, but it is not organized in such a way that makes it intuitive. You really have to kind of look for where do you put your documentation or dates. Some customization is available, but it is not plug-and-play like Jira. When I switched from TFS to Jira, I just went and started using Jira, whereas with Rally, you kind of have to really get in and figure out what you need to do before you set stuff up, or you're going to get yourself stuck. You can just start using Jira and be successful."

What other advice do I have?

I would advise others to make sure that they have full training in terms of the connection between features, user stories, and epics. They should also fully understand how to configure it in terms of providing visibility across teams that have to work with each other. I would rate Rally Software a six out of ten.
Muhammad  Ishfaq
Application Developer at Saudi Credit Information Co. J.S.C.
Real User
Top 20
An easy initial setup with good stability and very good scalability

What is our primary use case?

We are using the core repository for the complete development life cycle.

Pros and Cons

  • "The initial setup is fairly easy."
  • "There should be management of the project built-in."

What other advice do I have?

Overall the solution is good. It's scalable and stable and has been working well for us. Of course, the phased release could be smoother, and it's something they need to improve upon. I'd recommend this solution, even though we do plan to move to Microsoft Azure DevOps. I'd rate the solution eight out of ten.
Get our free report covering Atlassian, Microsoft, GitLab, and other competitors of Microsoft Azure DevOps. Updated: July 2021.
521,189 professionals have used our research since 2012.