3 ms·

My team does a lightweight agile process, we don't hate it. If we used a better tool, we'd love it. We have Jira, and I don't have the energy to change it, nor

My team does a lightweight agile process, we don't hate it. If we used a better tool, we'd love it. We have Jira, and I don't have the energy to change it, nor do I want the responsibility to decide or suggest what other tool that should be. I've always used Jira, I have no suggestions ready. I'm sure it's easy to pick a simple tracker, like GitHub Issues, but I would not know if it'd suffice all our needs and if it would scale, and again, I don't have the immediate energy to invest time into that. But meanwhile Jira is slowly eating away at me. I think the general concepts are acceptable. It's just all the rough edges, all the stupid little design decisions, and its slowness that I hate (passionately).

emllnd 3y ago
- Monday.com - Airtable - A giant board on Miro.com with a bunch of notes in frames Of course the scaling needs are different whether it’s for just a single team or if the data needs to be aggregated into some KPI. In my experience it’s better to keep KPI publishing separate from task tracking, though
lmm 3y ago
> I'm sure it's easy to pick a simple tracker, like GitHub Issues, but I would not know if it'd suffice all our needs and if it would scale The irony here is that those simple trackers scale a lot better. Jira's complexity is part of why it scales poorly - it's really bad when you have 500 people trying to use it.