undefined | Better HN

0 pointsjordanbeiber4y ago0 comments

But jira is only a tool right? Blaming Atlassian for a poorly led organization seems slightly misguided.

At some project size, measured either by software complexity/interoperability or user base, you will need a tool to manage issues and tasks.

What you're talking about is an organization where developers are not empowered - but even empowered developers need an issue tracker or a board of some description.

A "management by jira" culture will not be remediated by tooling.

0 comments

galangalalgol4y ago

A good tool cannot guarantee good results, but a bad tool can shape its user's behavior in bad ways. The same individual without that tool might have behaved differently. I have seen this in what I call design-by-ticket where all the why and how for a design decision, including design by committee meeting notes, get put in jira tickets.

jordanbeiberOP4y ago

Totally agree with your first two sentences.

However, the final part has nothing to do with jira IMO. You would have the same behavior in these organizations regardless of tool.

The dysfunction you describe goes way beyond a single or set of tools.

galangalalgol4y ago

It is hard to say for sure, but this organization used configuration controlled documents for design documentation before atlassian came along. When they made the switch (and hired oodles of graduates) suddenly about half of them ignore confluence or latex for design, because "jira has markdown". Oh hurray, we have a bad typesetting language mixed in with our bug tracker, lets shove our entire design in there! It is possible this is the influence of the graduates we hired, but it felt like everyone got there together while playing with the new toy.

2 more replies

j / k navigate · click thread line to collapse

0 pointsjordanbeiber4y ago0 comments

But jira is only a tool right? Blaming Atlassian for a poorly led organization seems slightly misguided.

At some project size, measured either by software complexity/interoperability or user base, you will need a tool to manage issues and tasks.

What you're talking about is an organization where developers are not empowered - but even empowered developers need an issue tracker or a board of some description.

A "management by jira" culture will not be remediated by tooling.

0 comments

galangalalgol4y ago

jordanbeiberOP4y ago

Totally agree with your first two sentences.

However, the final part has nothing to do with jira IMO. You would have the same behavior in these organizations regardless of tool.

The dysfunction you describe goes way beyond a single or set of tools.

galangalalgol4y ago

2 more replies

j / k navigate · click thread line to collapse