4 ms·

I may be in the minority, but at my last job I had some pretty great project managers that had us using Jira in a way that was simple and helpful. I think part

I may be in the minority, but at my last job I had some pretty great project managers that had us using Jira in a way that was simple and helpful. I think part of that was they had experience and political capital. So they chose to use only about 10% of the functionality, and allowed almost no one to augment their minimal workflow.

to11mtm 6y ago
At the first 'Real IT' job I had we started off as Waterfall using Jira. We eventually did transition to agile, and while it was painful, having an Agile coach on contract worked out GREAT. Their job was to teach us agile in 6 months and be out. Once we had switched, our Jira workflow was simple. I think it was the same scenario you outline above though; they had enough experience with Jira in waterfall that they knew what to use and what not to use. Which for us was Epics/Stories/Tasks/Tickets/Bugs, Attaching things, linking together (i.e. being able to track that a story was assigned to a ticket submitted by a user/customer was great for communicating with the business about priorities.) But that was about it.