> the organization-wide problem Jira is trying to solve
Yeah that problem is that in many places management sucks and can't trust their developers to get shit done, so you have to put metrics on it to bring down anxiety brought about by incompetence.
There are large open source projects that don't use jira; the extreme complexity of managing a distributed team with all sorts of interests -geneally even more complex than what a company has to deal with- is empirically doable without jira.
When an organization pivots to using jira it is a sign that their managers are no longer capable of respecting the programmers that work for them. If an organization starts out using jira, that means they never were.
To be charitable I'm sure there are a few corner cases where a manager came up through the ranks and "only knew jira" but that really means they don't understand open source IC, especially in the era of GitHub and gitlab issues.
(Btw GitHub issues is absolutely the thing that is slowly replacing jira)
Yeah that problem is that in many places management sucks and can't trust their developers to get shit done, so you have to put metrics on it to bring down anxiety brought about by incompetence.
There are large open source projects that don't use jira; the extreme complexity of managing a distributed team with all sorts of interests -geneally even more complex than what a company has to deal with- is empirically doable without jira.
When an organization pivots to using jira it is a sign that their managers are no longer capable of respecting the programmers that work for them. If an organization starts out using jira, that means they never were.
To be charitable I'm sure there are a few corner cases where a manager came up through the ranks and "only knew jira" but that really means they don't understand open source IC, especially in the era of GitHub and gitlab issues.
(Btw GitHub issues is absolutely the thing that is slowly replacing jira)