I’ve worked with some pretty rotten software, but management software is easily the most user unfriendly, so my vote goes to HPSM.
I’ve worked with some pretty rotten software, but management software is easily the most user unfriendly, so my vote goes to HPSM.
Jira is literally a shiny keychain which keeps PMs distracted and busy enough so that they don’t start calling people into a million meetings because they have nothing better to do. It is otherwise completely useless and borderline nonsensical, and any perceived productivity gains from its usage can be attributed directly to keeping superfluous managers away from engineers.
Funny I find jira to be very useful for a nice centralized location of where we keep issues that weve come across and will, at some point, handle, but are not going to get to now.
Other than our team lead, I don’t think any of our managers even look at it.
But how else can I force all my self-organising agile teams to follow exactly the same process?
Depends on your issues. If its something esoteric and/or too high level to be useful, yea it sucks. If its issues that are easily reproducible but you can’t address it immediately, adding it to the backlog and having that context in jira really helps. That’s all predicated on the story reporter providing steps to reproduce and good context. But there are some things I would consider it adds which are less than useful, like story points, where its almost bait how it starts a conversations with PMs who don’t know how to ask the right questions over why is it too high or low…
And gives middle managers another way to misinterpret sh1t they don’t understand.
Just wait until your product team gets suckered in by JIRA Align.