5 REASONSNOT TO

CHOOSE JIRADON'T WORRY,WE PREPARED 5 REASONSWHY TO CHOOSE JIRAAS WELL

*

*

Let's talk again about

JIRA is an issue tracker developed byAtlassian in 2002. It started as a bugtracker and over the years began tocover different management areas –including agile project management.

In a similar presentation we covered 5reasons why to choose JIRA for your

agile project. Now we'll show youanother point of view...

Here are our top five pickswhy you should stay away

from JIRA!

Hard tosetup…JIRA is a complicatedpiece of software thatstarted as a bug tracker.All of its flexibility has aprice – JIRA is reallydifficult be properlyconfigured if it doesn’tsuit you out of the box.

#1

…difficult touse

JIRA’s UI is not exactlyuser friendly, which is an

outcome of being afeature-heavy one-size-

fits-all solution. JIRArequires time to learn and

use effectively – moretime than it should.

#2

Missingfeatures...JIRA Agile was firstreleased six years ago,but to this day limitationsare visible. Somefeatures that should be apart of the core productare available only as paidadd-ons.

#3

…that take agesto be developed

It’s quite ironic if you thinkabout it – JIRA a productdeveloped for managing

agile projects is way farfrom being agile itself. Let

that sink in for a sec ;)

#4

Too manyfeaturesJIRA is simply toooverwhelming for someteams, having lots offeatures that are notrequired. If that’s the case,consider using Jixee,Gitlab, Github issuetracker, or Blossom.

#5

You can read more about JIRA on our blog

5 reasons NOT to choose Atlassian JIRAfor agile projects

Thanks for watching