DEV Community

Discussion on: Is Jira an antipattern?

Collapse
 
itsasine profile image
ItsASine (Kayla)

Understanding the "why" is the job of being a developer and any tool that discourages this should be put in the rubbish bin.

I think this is also a sticking point for areas that have high dev talent. I'm in Pittsburgh, so there are places looking for Carnegie Mellon Software Engineering graduates. They want the best students from the best schools, taught to engineer and architect a piece of software, just to put them in the little boxes mindset... Code monkey a little button and move on to the next button. That seems silly and a waste of that talent.

Jira does have a reference to the Epic on every story view, which I guess is to keep in mind how things fit into the larger picture, though I would prefer a better visualization of that. And a trust that the decisions made when implementing one issue aren't tossed aside by the people managing the Jira flow. "Why can't you just add a few more user roles? We're supposed to be agile." "Uh, the original requirement was we would have 2 roles. Not these mismatched middle roles. The entire thing needs gutted now." "You should have planned for this better." "wat, you never mentioned more roles. Ever."