2 ms·
Well, JIRA isn't terrible. It does its job reasonably well, but it really shows that it's a project management tool that developers happen to be forced to use,
by bitwize 5y ago
Well, JIRA isn't terrible. It does its job reasonably well, but it really shows that it's a project management tool that developers happen to be forced to use, and it's the standard "agile" tool. Its use is a red flag that maybe the org hasn't put much thought into encouraging developers to work efficiently and cultivating Csikszentmihalyian "flow". A typical corporate JIRA workflow is an example of what I call switch-cutting: making the production of metrics that will be used by management to crack the whip later, the responsibility of the line workers (akin to the old-timey practice of making a child cut the switch with which they will be beaten). But Scrum itself has this problem as well, and JIRA is just a tool to that end.
Like I said, there are far worse things that could be forced on a developer team -- like VersionOne, switching away from which to JIRA will seem as a breath of fresh air.