Usage of JIRA by our geographically distributed Agile software development team
November 26, 2018
Usage of JIRA by our geographically distributed Agile software development team
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with JIRA Software
JIRA is used by the entire BizMerlin team for design and development of the product roadmap. Product managers add items to the backlog as well as various sprints. Test Preparation, QA, code review, development, everything is controlled through JIRA. Scrum masters do their daily stand-ups and record notes, as well as ensure the issues are being updated correctly via comments and status transitions.
- When you want a configurable workflow for different issue types
- Showing the entire sprint progress at a glance in the burndown (or burnup) chart
- Ensuring every team member (even a new one) knows the steps that an issue has to take before closure
- Workflows and schemas are sometimes really difficult to understand. You learn it one time and it works fine for 6-7 months. When you need to modify it, it seems you need to learn it ALL OVER again.
- Left hand navigation panels sometimes need to be collapsed and expanded multiple times.
- A lot of accountability.
- Every developer can see their progress and how they did. No one needs to be told.
- Excellent communication - don't email etc, just add a comment in JIRA.
I have used other tools like Trello, FogBugz, Bugzilla, Backlog, etc.
Overall JIRA comes across as a clear winner. Perhaps the only close competitor is Bugzilla since it is open source and has a lot of other features that have been built for it, even if by many different teams.
Overall, JIRA is robust, configurable and scalable.
Overall JIRA comes across as a clear winner. Perhaps the only close competitor is Bugzilla since it is open source and has a lot of other features that have been built for it, even if by many different teams.
Overall, JIRA is robust, configurable and scalable.