The winning combination for your software development team: JIRA + Agile
Overall Satisfaction with JIRA Software
We use JIRA as a project management and a bug tracking tool for most of the company projects. Whether it is software development, ASIC design or IP development, JIRA fits all flavors. For software development, we use it mainly for its agile scrum and Kanban development support. We realized that switching to Agile with JIRA was a winning combination to increase productivity, together with having more homogeneous teams and same mindset across team members.
Pros
- Easy to use bug tracking features.
- It has a great support for Agile SCRUM and Kanban software development methodologies.
- Promotes collaboration within the team and across teams.
- It is extremely configurable and allows a system admin to address complex project management requirements.
Cons
- There is a steep learning curve for JIRA administrators before the full potential of the tool can be harnessed.
- The licensing system is per number of users. If you buy a small license and the tool is widely adopted, you may have an issue in getting your budget approved in a low cost environment, because the price for higher tiers goes up quickly.
- Support can use some improvement. It happened few times that for critical issues we had to spend a lot of time exchanging emails and explaining to different people where the problem was.
- It really improved our productivity and therefore decreased the time to market of our deliveries by 40%.
- It improved the collaborative work inside the team.
- Helped building the scrum mindset in the team.
- It helped replacing the various bug tracking tools used across the company to just one.
There are two advantages that Bugzilla has over JIRA:
1. Being open source (read free)
2. Having a feature that few of my users desperately need: clone a issue to multiple projects at once
Other than these two things, JIRA is better than Bugzilla in all aspects. It is the best choice for any company that looks at increasing the productivity, collaboration between team members and different teams, and subsequently reducing the time to market for projects or new features.
1. Being open source (read free)
2. Having a feature that few of my users desperately need: clone a issue to multiple projects at once
Other than these two things, JIRA is better than Bugzilla in all aspects. It is the best choice for any company that looks at increasing the productivity, collaboration between team members and different teams, and subsequently reducing the time to market for projects or new features.
Comments
Please log in to join the conversation