undefined | Better HN

0 pointsdimitrios13y ago0 comments

Why is it always on the Dev team to completely uplift whatever is working for them, and never that the PM/PO/DPO/Scrumwhatever has to do the heavy lifting themselves? Is it because they would actually have to do work instead of just attending meetings, slacking other people for updates, and sending out progress reports? (Sorry to all you good PMs out there, I am talking about the median case)

If you are a PM and you come on a team that isn't using JIRA, and you want JIRA with all it's fancy bells and whistles, that's fine. Set up a board yourself, write all the tickets, capture all the work that's happening based on the dev's tool they are currently using, and update all the knobs and buttons to your heart's content.

My guess is the infatuation with JIRA would quickly diminish if this was so.

0 comments

atom_arranger3y ago

One of the best PMs I have had used to be a dev. The company we were working with used a terrible Jira like piece of software I don't remember the name of, but he had the devs just use Trello. He would go through and update the other thing for stakeholders. Worked great

ratww3y ago

Definitely.

JIRA is the case of a product made for buyers/deciders rather than for final users, like the dreaded enterprise ERP.

Atlassian's Product Managers believe their product is mostly used by other product managers, but they're dead wrong. Not that it matters, anyway. Atlassian could probably fire all PMs tomorrow and it would be the same, as long as the software ticks all the necessary boxes it will still sell the same. Just hire more marketing, sales and evangelists.