4 ms·

Indeed Jira scales a lot (although being slow) and is well customisable and flexible. Its plugin system is also great (although a better documentation of how to

Indeed Jira scales a lot (although being slow) and is well customisable and flexible. Its plugin system is also great (although a better documentation of how to develop/maintain one, and of their APIs would grealy help). But in the meantime, it requires increasing discipline and regular revampings of internal processes across dev, product, market teams, and that's a lot of energy to burn to make it "work" across an org. Even more when you have people that are for very strict and precise adherence to processes. Whereas a less flexible, good enough system could help funnel the same energy towards something more productive than just internal compliance for the sake of it.

threeseed 4y ago
Which is why Jira continues to sell so well. You simply can't force one way of working on larger companies even if that way is undisputedly the right way. Because a lot of people will need to sign off on which tool to purchase and each of them are special geniuses with their own special genius way of working.
- Juliate 4y ago
  Well, time will tell. I'm not opposing a single Jira methodology to a myriad of other ones (tools or processes). I'm saying that Jira, without being constantly challenged for what it is[1] creates its own growing and tiring bureaucracy because companies (even large ones) cannot agree on a right way to work (but will add piles over piles of bureaucracy). [1] exactly like what Agile methodologies, or some certifications are; where now it feels like almost no one remembers/knows how to organize teams _without_ resorting to anything that Agile-thinking has tainted. It somehow relates to the fact that, in some companies, more energy and money is burnt over how to organize the work rather than doing the work itself. And it definitely shows.
- raverbashing 4y ago
  For real, I don't think it's all about "each special snowflake's way of working" but there are legitimate needs that change Each team can have a different workflow with Jira Jira works for non-software-development tasks as well I've seen it used on companies having 4/5 levels of stories deep (think Initiatives/Epic/Stories/Subtasks/etc. Different companies split this different ways. The plugins sound inconsequential but they are very useful (almost a must) in several occasions.

threeseed 4y ago

Which is why Jira continues to sell so well. You simply can't force one way of working on larger companies even if that way is undisputedly the right way. Because a lot of people will need to sign off on which tool to purchase and each of them are special geniuses with their own special genius way of working.

Juliate 4y ago
Well, time will tell. I'm not opposing a single Jira methodology to a myriad of other ones (tools or processes). I'm saying that Jira, without being constantly challenged for what it is[1] creates its own growing and tiring bureaucracy because companies (even large ones) cannot agree on a right way to work (but will add piles over piles of bureaucracy). [1] exactly like what Agile methodologies, or some certifications are; where now it feels like almost no one remembers/knows how to organize teams _without_ resorting to anything that Agile-thinking has tainted. It somehow relates to the fact that, in some companies, more energy and money is burnt over how to organize the work rather than doing the work itself. And it definitely shows.
raverbashing 4y ago
For real, I don't think it's all about "each special snowflake's way of working" but there are legitimate needs that change Each team can have a different workflow with Jira Jira works for non-software-development tasks as well I've seen it used on companies having 4/5 levels of stories deep (think Initiatives/Epic/Stories/Subtasks/etc. Different companies split this different ways. The plugins sound inconsequential but they are very useful (almost a must) in several occasions.