Originally posted by porkins_sf
What is it about Jira that you loathe? Not gonna lie, I get a little concerned when I hear people on a sw project talk like that. I've worked primarily on safety critical systems my career and tools like Jira & Bugzilla & others are crucial for knowing what's going on. I can understand why non-safety critical products might not need that same level of intense attention to detail but it's always helped things run smoother and especially keep track of problems.
I don't like overly rigid structures either...for example whenever I work with a legacy products using waterfall or spiral methods I do what I can to move away from that. But we've never moved away from using Jira-like tools for tracking features and bugs.
I'm not really bagging on the tool. It's more a shorthand for my own PTSD about the times I've had people who knew how to wield a hammer (JIRA) see everything as a nail - and the hours and hours of arcane debates I've had about "what exactly constitutes an Epic vs a Story vs a Subtask?" and other esoteric conversations that would make a mystic blush.
JIRA (or any number of other systems) are great for tracking the status of tasks, features, bugs, etc. and can be incredibly powerful tools if you do the work to configure it in a way that works with your team's workflow. I'm personally much more of a visual/tactile learner, always want to jump up and diagram stuff on a whiteboard, make mind maps, user story mapping, move sticky notes around, etc.
I remember early on in my career as a Producer on a different title, a Technical Director sat me down and told me the only way I could communicate with the engineering team was to deliver a flat list of user stories strict...
Read more