5 ms·
JIRA is for people who like to do more planning of work than actual real work. See also: meeting moths. It’s commonly used by technical managers who have no sk
by iamleppert 7y ago
JIRA is for people who like to do more planning of work than actual real work. See also: meeting moths.
It’s commonly used by technical managers who have no skills to contribute but need to justify themselves as important so they will spend countless hours setting up complex workflows, tweaking forms and starring at pointless “burndown” charts describing work they have absolutely no clue about.
JIRA also generates an enormous amount of automated email which is further exploited by these folks to advertise to others in the company that they are doing work.
When you interview some place, pay attention if they have a culture ruled by JIRA. If they do, and you like to get real work done, do not work there. It may be possible some use JIRA as a tool but the risk is far too high to take.
- Macuyiko 7y agoI wish I could upvote you twice. Exactly describes my experience and it is soul sucking. It gets so bad that the work-planners actually succeed in creating faux importance and are valued more (and value themselves more) than the actual workers.
- JasonBlack555 7y agoI upvoted on your behalf !
- time0ut 7y agoJIRA can be used in a way that is beneficial to the team. It is ok as a simple shared task list. Of course, a shared spreadsheet is actually better and infinitely less expensive. Unfortunately JIRA is monstrously complex and dead weight hides in that complexity as you've noticed. My company is so far gone. We use JIRA as the system of record for change audits. This is a function it is particularly poorly suited to. I don't even want to list the other things we use it for. They are too numerous an depressing. But rest assured, if you can somehow map a process to JIRA, it's there.
- jaclaz 7y ago>Of course, a shared spreadsheet is actually better and infinitely less expensive. I need to bookmark this, and - with your permission - cite you when (often) I am proposed obscenely complex software to solve trivial issues.