We just raised a $30M Series A: Read our story

Jira Align Alternatives and Competitors

Get our free report covering Planview, ServiceNow, Microsoft, and other competitors of Jira Align. Updated: September 2021.
542,029 professionals have used our research since 2012.

Read reviews of Jira Align alternatives and competitors

Kleber A
Chief Operating Officer at a tech company with 11-50 employees
Real User
Top 10
Allows you to create a bridge for maintenance and support, directly to the client

Pros and Cons

  • "We can forecast tasks and the number of hours a task will take and can compare it with how long a task actually takes."
  • "The communication could work better, especially for the development team."

What is our primary use case?

We use it to manage the project. We create the product backlog, and we put our tasks into the DevOps schedule.

How has it helped my organization?

Azure DevOps allow you to create a bridge for maintenance and support, directly to the client. We can forecast tasks and the number of hours a task will take and can compare it with how long a task actually takes. The Timetracker function allows us to put all this together. Before Azure DevOps, we had difficulty predicting how long tasks would take, considering all the parts that must work together.

What is most valuable?

We have a component server, which is basically a tracker. This is very useful for us to itemise the start and end of tasks to evaluate the resources required, based on price. So it's very valuable. It is important to be able to inspect the items required in a project.

What needs improvement?

The communication could work better, especially for the development team. The important thing is that the tracker tools provide adequate communication, as do other tools. It seems to be lacking in DevOps and is an area which could be improved. We also need to improve publishing in production. In the future, we would like Azure DevOps to work with automated tasks regarding publishing. Better integration with existing source code is another area, which would benefit from improvement. The search repository could be more comprehensive, and visualisations could be optimised, further.

For how long have I used the solution?

We have been using Azure DevOps for around two years. We are a Microsoft partner, so we use Azure DevOps as part of that partnership.

What do I think about the stability of the solution?

Stability is excellent. Initially, we had some problems with performance, but nowadays it's okay. Maybe they improved the server.

What do I think about the scalability of the solution?

It's good scalability, but we need to improve the process by understanding it a lot more.

How are customer service and technical support?

We never actually contacted support. The best plan is to read through all the documentation, but getting the right documentation for your specific project is not always easy to find, as there is so much to go through.

How was the initial setup?

It's average, because we need to research what we are trying to achieve, and the platform has rich functionality. This is a good thing, but it can also mean setup is very complicated. However, we usually find that after testing more, we find our way around what we are trying to achieve.

What about the implementation team?

Our deployment took about three months, as we tracked it. Following that period, we needed another month to integrate a new component into the setup. We implemented it ourselves, with one of our team. We have about 10 users using Azure DevOps, but we have 2 people to provide the deployment out of those. These are developers. We have a small team for DevOps, including the manager. We need our staff to be flexible and agile in our team to take on various DevOps tasks.

What's my experience with pricing, setup cost, and licensing?

As a Microsoft Partner, you get a discount on the pricing. Licensing costs are around $80 a month for DevOps, but for Azure, it is about $200 a month.

Which other solutions did I evaluate?

We tried other tools, but Azure DevOps has a richer toolset, and it fits in better with our process. To some extent, as we are a Microsoft partner, we didn't seriously consider other options. However, we did look at Jira and Gitlab as potential alternatives.

What other advice do I have?

I would rate Azure DevOps as an 8 out of 10. I would ensure that DevOps' use is planned, in detail, including the implementation before using the software. I would also ensure you have a thorough knowledge of the main components of the system. This will ultimately save hours of work.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
BP
Director, Solution Strategy & PMO at Verisk Analytics
User
Top 20
Great for viewing impediments and provides visibility and predictability across teams

Pros and Cons

  • "The "Blocking" feature has helped our scrum masters track impediments and share them at the program level to stakeholders with accountability and detail so that they understand and the action items which can be noted easily."
  • "Our overall impression of Leankit has been very positive, however, our experience with the JIRA integration into our Leankit boards was much harder than we anticipated and that could be improved by simplifying it somehow."

What is our primary use case?

With Leankit, our PMO has a single solution and Program Increment Board to integrate teams and projects and align priorities across the entire program - which consists of 22 Scrum teams. 

It allows us to track our PI goals, sprint goals, dependencies, and impediments across all of the teams creating extreme visibility and predictability for product owners, stakeholders and the teams. With integration into JIRA and the team boards, it allows us to have one single source of truth while not overwhelming the teams with the added responsibility of manually updating their epics, stories, and/or tasks. 

How has it helped my organization?

Leankit has made it much easier for us to visualize our progress across our entire portfolio, which consists of 22 Scrum Teams. 

It is now our single source of truth, given the integration with JIRA and near real-time updates. It has made such an impact on the way that our business unit manages programs that we plan to leverage the virtual Kanban boards to enable remote and in-person Big Room Planning sessions. 

It provides visibility and predictability across all of the teams in each PI. It also has been a great roadmapping tool for our product owners.  

What is most valuable?

The "Blocking" feature has helped our scrum masters track impediments and share them at the program level to stakeholders with accountability and detail so that they understand and the action items which can be noted easily. 

We use it for our Scrum of Scrum Impediment Executive Action Team Meetings daily because it allows us to view all of our impediments in one place and shows us what exactly is being blocked, (i.e. Program Increment Goal, Sprint Goal or an Epic). 

The dependency features are also very valuable as there are many to track in a given Program Increment; that also allows us to review them during our Big Room Planning. 

What needs improvement?

Our overall impression of Leankit has been very positive, however, our experience with the JIRA integration into our Leankit boards was much harder than we anticipated and that could be improved by simplifying it somehow. They could use some sort of drag and drop approach if possible. 

The requirements to create these integrations are very complex and time-consuming both on our end and the Planview/Tasktop end. Once the integration is set up, the user experience is great, however, the setup itself is difficult. 

For how long have I used the solution?

I've used the solution for a little over a year.

What do I think about the stability of the solution?

The solution appears to be handling our setup perfectly. We rarely have issues.

What do I think about the scalability of the solution?

The solution appears to be handling our 22 Scrum Teams, the JIRA integration, and our use across the program. 

How are customer service and technical support?

So far, we have had a very good experience with customer service and tech support. 

Which solution did I use previously and why did I switch?

We tried to use JIRA Portfolio, however, it did not meet our needs. Therefore we started looking for alternative solutions. 

How was the initial setup?

The initial setup was fine, however, as I mentioned before, the JIRA integration was a bit complex and time-consuming. 

What about the implementation team?

We implemented through our own EPM Tools Group as well as with a Tasktop representative. 

What was our ROI?

This has yet to be determined. 

What's my experience with pricing, setup cost, and licensing?

We shared our experience with other PMOs within our company and it led to an Enterprise Agreement. The price was right and the setup was fairly easy. 

Which other solutions did I evaluate?

We also looked at JIRA Align. 

What other advice do I have?

We're very happy with our decision to use LeanKit for our Portfolio/Program management and we're glad we could spread the word around our company to lead to deeper integration. We look forward to some cool new features.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Anthony Gregg
Technical Engineer (Retail Group) at a retailer with 10,001+ employees
MSP
Top 5Leaderboard
A stable solution that is useful for cases and incidents tracking and help desk and knowledge management

Pros and Cons

  • "We use it for a lot of things, and it is really good for our use cases. We use it for our help desk and knowledge management, which is really good. When it comes to modules, it has an incident module, which is really good for us in terms of tracking our cases and incidents. Its change management module is really good, and it also has customization capabilities."
  • "Its performance is really bad. When you're on the hosted cloud, it gives you the time it takes for a transaction to happen, and it takes anything from 20 seconds to a minute, which is a really long time. Something that is really annoying in this solution is that when you click on the Back button to go back, you don't go back to the previous screen. You go back all the way to the homepage. It is really annoying and painful. Its UI is also pretty dated. It is very customizable, but the customization seems to be clunky. We have a separate team that owns the ServiceNow implementation. They control how it is customized. Its customizations are pretty extensive, and it takes us a while to get them done, which is painful. That could be because of our internal team, as opposed to the product itself. When it comes to DevOps, there are better solutions such as Atlassian and Azure DevOps. ServiceNow DevOps is an ITIL product that is trying to be something else. DevOps is not its prime purpose, even though it is capable of doing that. Trying to be too many things by one platform is not a good idea. They should focus on the ITIL space and not get into all other spaces."

What is our primary use case?

We use it for ITIL. It is our everyday tool for ITIL.

How has it helped my organization?

It is a very capable and significant product that we utilize within the company, and it has absolutely improved the way our organization functions. 

What is most valuable?

We use it for a lot of things, and it is really good for our use cases. We use it for our help desk and knowledge management, which is really good.

When it comes to modules, it has an incident module, which is really good for us in terms of tracking our cases and incidents. Its change management module is really good, and it also has customization capabilities. 

What needs improvement?

Its performance is really bad. When you're on the hosted cloud, it gives you the time it takes for a transaction to happen, and it takes anything from 20 seconds to a minute, which is a really long time.

Something that is really annoying in this solution is that when you click on the Back button to go back, you don't go back to the previous screen. You go back all the way to the homepage. It is really annoying and painful. Its UI is also pretty dated.

It is very customizable, but the customization seems to be clunky. We have a separate team that owns the ServiceNow implementation. They control how it is customized. Its customizations are pretty extensive, and it takes us a while to get them done, which is painful. That could be because of our internal team, as opposed to the product itself.

When it comes to DevOps, there are better solutions such as Atlassian and Azure DevOps. ServiceNow DevOps is an ITIL product that is trying to be something else. DevOps is not its prime purpose, even though it is capable of doing that. Trying to be too many things by one platform is not a good idea. They should focus on the ITIL space and not get into all other spaces.

For how long have I used the solution?

I have been using this solution for eight to ten years.

What do I think about the stability of the solution?

Its stability is really good.

What do I think about the scalability of the solution?

I believe it is very scalable because it is in the cloud. It is a very widely used application. Our whole IT organization uses it. We have probably a hundred thousand users.

How are customer service and technical support?

We have our own internal tech support, so it is hard to know in terms of ServiceNow. Our internal tech support is pretty good on it.

Which solution did I use previously and why did I switch?

The previous solution that we were using was Remedy. We switched because Remedy was even worse. It was dated in every way possible. It didn't perform, and it wasn't functional. Its UI was hard to use, and its capabilities were very limited.

What other advice do I have?

I am in the DevOps world, so from a DevOps perspective, I know all the tools out there. Personally, when it comes to DevOps, there are better solutions such as Atlassian and Azure DevOps, and I wouldn't use this solution for DevOps. 

I would rate ServiceNow DevOps an eight out of ten as an ITIL tool. It has a lot of good things about it for its prime purpose, but there is definitely room to improve. As a DevOps tool, I would rate it lower because it is currently missing a lot of capabilities from that perspective.  

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Get our free report covering Planview, ServiceNow, Microsoft, and other competitors of Jira Align. Updated: September 2021.
542,029 professionals have used our research since 2012.