Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
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.