Yeah, it depends on how big your teams are. There are some perf issues on the on premise solution, but when you're dealing with dozens of teams, each about 5-6 engineers all following scrum or kanban, you really need something like Atlassian.
While this is typically how it's been done in my experience I really don't agree. My take on JIRA is that it can literally do anything project-management wise but everything it does is cumbersome and slow.
I wish there were more alternatives that had SOME similar feature sets (certainly not all of the features; most of the JIRA ones can be interchanged with its other features) and was significantly faster to use.
We just updated Jira at my job, it feels pretty snappy. It has always felt reasonably smooth to me, but I have also only been using it for about 2 months.
The most things in JIRA I need to click probably at least 5 or 6 things to do something. So I didn't necessarily mean it's slow as in clicking on something takes forever to load (though I've seen that happen on self and Atlassian hosted versions of JIRA) but that it just simply takes way too many clicks to do anything in JIRA (except maybe creating an issue since that's always at the very top). In my opinion at least.
I'm using Slack + Gitlab + Pivotal. Overcoming resistance depends on the source. Managers like that they don't need to chase engineers for updates. Engineers like that everything is integrated, so if they 'git push' while referencing the Pivotal story ID, the story will be updated/finished/delivered.
Email in profile, feel free to get in touch if you want more detail.
