JIRA is the bees knees.
Updated February 25, 2015
JIRA is the bees knees.
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Atlassian JIRA
At Wonderlic, JIRA is the primary tool used to track requests and projects. JIRA is very popular within the software development cycle (Stakeholders, BA, SD, QA teams) but I've seen it utilized by other teams, like our print & warehouse departments. The whole organization has access to the tool and I believe each team does take advantage of what it offers.
I can think of a couple business problems JIRA helps solve. The most important, in my opinion, would be that JIRA provides stakeholders with a consistent avenue to request work. It clears up any confusion as to who owns such work and defines what stage the work is currently at (e.g. UAT). Another problem we've been able to rectify by using JIRA would be the issue we've had with ticket prioritization. Using boards, we can rank tickets quickly and painlessly.
I can think of a couple business problems JIRA helps solve. The most important, in my opinion, would be that JIRA provides stakeholders with a consistent avenue to request work. It clears up any confusion as to who owns such work and defines what stage the work is currently at (e.g. UAT). Another problem we've been able to rectify by using JIRA would be the issue we've had with ticket prioritization. Using boards, we can rank tickets quickly and painlessly.
Pros
- JIRA does a great job of providing flexibility for the ticket types. It can be used for a large software development project with tons of scope and it can be used for a small print job.
- Ticket management using boards is super effective and makes tracking work very simple.
Cons
- Moving tickets across different stages on a board can be a little cumbersome as tickets can sometimes not update properly and require intervention on the ticket itself.
- I'd like to see more creative widgets for the dashboard. Don't have any specific ideas but more options around metrics would be awesome.
- The software development process is more efficient and effective because of JIRA.
- Requests from stakeholders are better defined.
- Expectations for work are more clearly understood and confusion around when something will be delivered has been eliminated.
JIRA blows Sharepoint out of the water. I've been a heavy user of both and the JIRA implementation we have now has reduced so many headaches within our organization. At one time, we had physical cards to track Sharepoint issues and were forced to stand around a board for 15 minutes, twice a week, fighting for urgency. JIRA has made it easier to enter tickets, prioritize them, watch them through the entire process and sign off upon completion.
Comments
Please log in to join the conversation