Shivanjali BhutkarBringing Technology and Business togetherNa, Ca, United States
Has anyone used JIRA for agile PM? Please provide the pros and cons you have experienced with this tool. thanks! Saving Changes...
Sort By:
Clemens BauerCEO| Think3 Consulting GmbHGraz, Austria
We use JIRA for product development in an agile way. There is project and it contains stories, epics and tasks. This is used for documentation and for an overall overview for management. But for the teams the progress is tracked on a wall with post-it. Saving Changes...
AJU K SEBASTIANAju K Sebastian, PMP| IBS Software ServicesPeroorkada Po, Trivandrum, Kerala, India
JIRA is an excellent and easy tool for an agile PM. It has both Kanban, SCRUM boards for operational or product development. In SCRUM, it has various sections like Backlog, Active Sprints, Releases, Reports, Issues, Components, and add-ons.
You can create a board for the team and can move items (issues, tasks, sub-tasks) using a basic flow (to do, in-progress, done). Or, you can even create your own workflow. Saving Changes...
As Clemens mentioned, I am also using JIRA for product development with Agile methodology. We can create/end sprints, schedule stories in sprints from backlog, change status of stories as the sprint progresses. We can also create sub-tasks for the stories and assign to individuals to track dependencies and progress.
Dashboard tools and charts can help in displaying sprint health/status at any given time.
The only disadvantage I can see is we cannot add efforts for sub-tasks of stories. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Sure, it works. And many use it for their stories, backlogs, sprints, and Kanban boards. I'm sure you knew that already though as it is one of the most popular tools atm. What specifically are you looking to learn with regards to your needs?
At face value, the pros is that it centrally exposes relevant project information - assuming it is utilized and maintained properly (as with all tools). The con is that it can be a bit kludgy, and had originally come out as an issue tracking tool - so everything is an 'issue'.
Seems to be one of the main 'go to' tools when companies transition to Agile. Saving Changes...
The one flaw with any of these tools Is that you can't compel team members to use them in a consistent manner so training and social pressure are key to avoid GIGO.
Kiron Saving Changes...
Shivanjali BhutkarBringing Technology and Business togetherNa, Ca, United States
All,thanks for your input! Saving Changes...
Eric IsomOwner| learn.pmguaranteed.comUt, United States
It’s a fine tool for Agile. However, it is easy to over-complicate it. Keep it simple. Use a single template for all item types, such as bugs and stories and tasks so that you have the flexibility to change from one type to another easily. Also, change the default workflow to allow you to go from any state to any other state, otherwise it becomes a limitation and can cause data quality issues with resolution dates and states. Saving Changes...
Michael PerdunnPrincipal| MKP SolutionsOmaha, Ne, United States
I'm a big fan of the Atlassian products. They do a great job providing a wide range of easy-to-learn tools. But they can scale up to more complex environments. I would agree with Eric and say it is easy to over-complicate things. I had a lot of success when I kept things simple and let adoption grow organically. Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
We use JIRA for Agile. The problem is that not all team members are using this is a consistent manner, so I concur with Kiron on this. Saving Changes...
