JIRA - The Best ALM Tool in the Market.
Updated October 15, 2019
JIRA - The Best ALM Tool in the Market.
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with JIRA Software
JIRA is used in my organization for Application Lifecycle Maintenance (ALM) activities. It is used in collaboration with Confluence/Wiki for capturing detailed:
1. User stories in form of project backlog
2. Acceptance criteria
3. Creating bugs
4. Analysis ticket
5. Maintaining story workflows (from ready for dev to closed)
6. Logging work hours spent on each individual ticket/story
It is also very helpful in creating a very simplistic boundary line between the on going sprint and the backlog (all my projects have been executed in Agile mode). In addition to it, as my projects have always had more than one sprint going on simultaneously and the stories part of those sprints related to each other, it acts as a very elegant tool for representing such views where the information is easy to comprehend for any developer or tester.
1. User stories in form of project backlog
2. Acceptance criteria
3. Creating bugs
4. Analysis ticket
5. Maintaining story workflows (from ready for dev to closed)
6. Logging work hours spent on each individual ticket/story
It is also very helpful in creating a very simplistic boundary line between the on going sprint and the backlog (all my projects have been executed in Agile mode). In addition to it, as my projects have always had more than one sprint going on simultaneously and the stories part of those sprints related to each other, it acts as a very elegant tool for representing such views where the information is easy to comprehend for any developer or tester.
- Single view for all the user stories (active sprint/backlog)
- Ability to generate reports of various types for each of the active / closed sprints for e.g. burndown chart, sprint velocity etc.
- Ability to track release tickets - we can create tickets which are supposed to go for production from various sprints in one single page and manage it from there.
- Integration of communication tools like Hipchat and Slack makes it very easy for tracking & responding to notifications.
- Mobile app of JIRA is not so holistic in nature and one has to navigate a lot to do various things which are very easy to do in web application.
- Faster turnaround time for closure of tickets - Developers could communicate through various chat platforms, share their analysis in form of attachments in JIRA
- Hosting on cloud made it easier to work from remote location leading to cost efficiency
- As a JIRA Admin, it is very easy to maintain and manager various user accounts
Previously I have used TFS and Rally. JIRA is very simple to use and has lots of features compared to these two and other tools available in the market. The ability to integrate other tools is much easier in JIRA. It is also robust, scalable and has a good number of add-ons to try and play around with JIRA to make an impactful tool for project management.