re: Is Jira an antipattern? VIEW POST

VIEW PARENT COMMENT VIEW FULL DISCUSSION
 

In truth, this is not an issue of tools but of communication and roles and team management.

#bestofdev :)

My current PM is very upfront about working at the Epic level. Like, she at the end of the day doesn't know what the nitty gritty of what we're implementing is, she is mostly in meetings with our UX guy or making sure overall features are being prioritized right.

On the one hand, cool, someone with a vision for the actual app. Normally I feel like since I'm working at an end to end level, I'm the only one who ever sees that. On the other, though, we're not really able to mix epics her way. It might make more sense for dependencies to work on a few api layer things at once to be prepared for the UI stuff once the wireframes are done, instead of scrambling before a release date to do everything all at once to Ship It.

Now that I'm on this rant, I'm a smidge disappointed the author didn't address how date driven Jira is. Every sprint has a day countdown. Every issue has dots for how many days they've been in a swimlane. Every release has a date. Dates are everywhere as the target rather than points or epics or something. Shouldn't we be more focused on the actual stuff of the app?

 

Every sprint has a day countdown. Every issue has dots for how many days they've been in a swimlane. Every release has a date. Dates are everywhere as the target rather than points or epics or something

Basically like one of those social networks full of metrics causing anxiety to the users :-D

On the one hand, I love metrics. I like Jira as a tool for obtaining metrics.

On the other hand, for gods sakes, don't compare teams using those metrics. Keep them internal and use them for retrospective discussions, not dick waving in front of management.

That basically summarizes my awful 15-page paper on Agile metrics from my grad program that I alluded to in my comment to @ben xD

code of conduct - report abuse