JIRA Review

​It is very capable, but also very complicated


What is our primary use case?

We use it for backlog management, sprint planning, requirements management, Scrum, conducting Scrums, and all of our agile stuff.

How has it helped my organization?

It handles all of the issues that we need it to do.

What is most valuable?

It is very flexible, so we can do pretty much what we want with it. 

What needs improvement?

I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

It scales up well.

How is customer service and technical support?

We have a team who administrates technical support. They handle this interaction with JIRA. Sometimes it takes a while to get a solution, but they solve everything. 

Which solutions did we use previously?

Before, we used a homegrown solution. 

Almost everybody uses JIRA nowadays because it is the most cost-effective solution.

How was the initial setup?

I was not involved in the initial setup. 

I do know the initial setup was pretty complicated. The user interface could be better organized and easier. 

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

It does not cost that much.

Which other solutions did I evaluate?

We did not really evaluate anything else. All of the other products were way too expensive for our purposes. Also, JIRA is the de facto standard.

What other advice do I have?

It is very capable, but also very complicated.

Most important criteria when selecting a vendor: reliability.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest

Sign Up with Email