18 ms·
> Ruined in the very first line by suggesting that JIRA is somehow a project management tool. This level of pedantry is unwarranted, especially given that JIMR
by mbesto 9y ago
> Ruined in the very first line by suggesting that JIRA is somehow a project management tool.
This level of pedantry is unwarranted, especially given that JIMRA was only mentioned in the comments. An issue tracker is a project management tool.
> imagine trying to use JIRA to project manage the the construction of a new vehicle,
Which is precisely why people don't use JIRA to manage construction. I don't see how this adds any value to whether JIRA helps manage software development projects.
> Just try and use JIRA to determine a critical path, or to track the impact on one project when a deliverable expected from another project slips, or to alert when the threshold of a slipped due date is exceeded.
I thought the idea of Agile is that you focus on the mechanics of delivery and not the expectations of delivery? This comment sounds so "enterprise IT" that I don't even know where to start with dissecting it.
You seem to have a gripe with JIRA specifically and I can't pinpoint why one would get so worked up about it.
- dragonwriter 9y ago> An issue tracker is a project management tool. Issue tracking is a very small subset of project management. It's true that an issue tracker is a “project management tool” in the sense that it is a tool for some aspect of a project. It's not a “project management tool” in the more comprehensive sense that that term is often, but not always used.
- UK-AL 9y agoPlus the fact JIRA has extensions such as JIRA Agile, and Portfolio which is really means its becoming a project management tool. Just not prince2/waterfall/pmo style project management, which I avoid at all costs.