This is essentially my opinion of it. I look at both Trello and JIRA as useful, depending on my use case. With a cross-discipline team focused on delivering a f

This is essentially my opinion of it. I look at both Trello and JIRA as useful, depending on my use case. With a cross-discipline team focused on delivering a few things (basically epics/features/whatever) at once, I love JIRA. Working on my own, I'd use Trello. It has a similar feeling to the hatred for Excel we all have as we start to use it. So. Many. Features. When you have a team member who is a power user, it can be frustrating since they will want to lead the implementation. Then you run into a bottleneck when they are the only ones that can run/fix that report. Maybe not a great comparison beyond that. I like John's take on it that you should start with a simple, physical board. If I start with a new team that will be my preferred path. I joined a team on Asana and we simply used the list type for a project with acceptance criteria. Not a physical board but it was super basic. Over the next 3 months we started to add colored tags for epics, important links to the description during the sprint, & links in the description to related stories. When it became JIRA 6 months in, we moved to JIRA. If we would have started with JIRA there would have been a riot. But now that we know the features we need, we don't find it bamboozling. It still can be for features we're figuring out we need (I spent 3-4 hours on a simple plugin last month), but the attitude is definitely not the "JIRA sucks" mentality that I hear a lot about.