Dear reader - help me improve the categories / capabilities, or point out any errors I may have made - jarno@agilefant.comAgilefantAn issue tracker dressed up in agile clothingMediocre scrum management for small-scale settingsA heavyweight agile ALM systemNimble task management for small projects with little-to-none reporting needsAn open source tool for small teams and very small projects, with exciting promotional writing and a tad of eccentricity
#CategoryCapabilityOpen SourceCloudnotesJira Softwaremore infoScrumwiseVersionOneTrelloTeamworkPMTeamworkPM notesMore notes
0UXReal-time editing (edits done go 'live' to all users without a refresh)NoYesPartialReal-time editing is present inside a Scrum or a Kanban board, but elsewhere you have to refresh manually. Also, if you move an item from the project backlog into a sprint board, it doesn't appear without a refresh. Note: in practice this is a bit erratic; sometimes the updates go through, sometimes not.YesNoYesYesPartialSome changes went live, others did not. Didn't discover if there was a logic behind the seemingly 'random' behavior
0UXFast to use (loading times, etc.)PartialYesThe speed of the OS version depends on the amount of data. My Work and Story tree views get slower as there is more data. The Cloud version is a single-page app, and in most of the views loading is instantaneousNoOnDemand seems quite slow even if you only have a little data. When you navigate between pages it can take up to 10 seconds to load. Things which are done on a single page are OKPartialNoYesYesYesNo significant loading times, at least if the system has very little data.
0UXFast new item creationPartialYesIn Cloud, we "copied" Trello's by default always leaving the add field open if you want to create many items at the same timePartialJira has in many places the Create + create new (just like Trello, for example, but) Creating new issues is limited in many ways. For example, one cannot create a new item directly into an ongoing sprint, but it must first be put to the backlog in a project, and then moved to the sprintNoNoYesI liked the bulk adding dialogs. They could also be used to import tasks and stories from e.g. excel
0UXDrag & drop prioritization within a backlogYesYesYesYesYesYesYesif a task list is thought of as a backlogYes
0UXDrag & drop from one backlog to anotherNoYesIn Cloud, you can drag & drop one or more items into the backlog listing of the left hand menuPartialDrag & drop works well within a sprint (scrum board) or a kanban board. According to the user guide you can also drag n drop stuff from one version to another. No drag & dropping from one project to another, thoughNoNoNoNoMoving tasks and task lists using a move commandYesDrag & drop from the project backlog to the sprints, between sprints, and back to the project.
0UXHow difficult is it to pick up & learn the tool?EasyEasyHardHarder than e.g. Scrumwise or Agilefant, but Not as hard as VersionOne, though. This is exemplified in the fact that I had to dig up the answers from the manual, as they were hard to find in Jira itself. Jira's homeground is to serve as an issue tracker, and it does a good job serving as a team scrum or kanban board. The lack of hierarchy means that it does not scale too well beyond the single team context (though this can be tried - there are add-ons that may alleviate the two-level hierarchy problem)ModerateHardVery easyEasyQuite easy! Not as easy as Trello, thoughEasyThey say "Figuring out the tool is ridiculously easy", and based on that I expected it to be very easy - like Trello. However, that wasn't the case and Taiga wasn't immediately intuitive to me. After some clicking around I understood how most things work. There is no user guide either.
0UXIn-place editing (as little as possible unnecessary context switches / pop-ups / windows opening)YesYesNoIn most places (well, all places I found, except when renaming objets), a pop-up seems to be needed to edit issue attributesNoNoYesYesPartialThere coiuld be more in-place editing of story and task attributes, now dialogs are used quite a bit
0UXEasy editing of properties of multiple work itemsNoYesNoAt least I couldn't find how to do it in the project backlog or sprint board views. Probably can be done with JQL...?
0UXMobile appNoYesFor Android. But it's written with Cordova, so doing an iOS release would be easy, we just haven't done that yet.PartialYou can login to a mobile-friendlier browser interface. It is quite limited in functionality, as you can only see issues assigned to you, and comment on them. There were 10+ 3rd party-created apps, both free and paid-for, available in the Play store - I didn't take a closer look at them, but it seems that with them, some of the limitations of the by-Atlassian -created mobile interface could be overcomeNoNoYesYesThere is a mobile app, didn't check it thoughNo
1Electronic tool basicsSearching for work itemsYesYesYesCan search for issues...PartialYesYesYesYesCan search for stories, issues, tasks and wiki pages
1Electronic tool basicsSearching for work item containers (backlogs)YesYesNo...but can't search for projects, boards, sprints, etc. ...PartialYesYesYesNo
1Electronic tool basicsSearching for peopleYesYesNo...or usersPartialYesYesYesNo
1Electronic tool basicsStory / task commentingYesYesYesIssues can be commentedYesYesYesNoSupports project-wide messaging; can probably be used to get rid of internal email - within a projectNo
1Electronic tool basicsStory / task statesYesYesYesConfigurable states for issuesYesYesYesPartialTasks either done or not doneYes
1Electronic tool basicsA log of all changes in the systemPartialPartialAgilefant keeps track of all changes made to the database. Currently these can't be viewed via the user interface. On the roadmap to the Cloud versionYesCan add filtered activity streams on dashboard viewsYesYesYesYesThe 'overview' tabYes
1Electronic tool basicsSharing views as read-onlyPartialPartialIterations can be shared as read-onlyYesPowerful - or should I say complicated - user permissions. Would be interesting to know how much of all of that is needed in the real world.PartialYesYesNoOtherwise, reasonably granular and easy-to-use user rightsYes
1Electronic tool basicsFlexible time tracking / logging of spent effort (for tasks, stories, backlogs - use the granularity needed)YesYesNoCan log spent effort only for issues and issue sub-tasks; not for epics, projects, versions, etc.PartialPartialNoPartialCan log time to tasks and sub-tasks only. Otherwise I like the interfaceNoNo time tracking, but they say an integratin to Toggl exists. Another suggested workaround is to use custom fields.
1Electronic tool basicsKeeping track of time spent since last logging of spent effortNoYesNo
1Electronic tool basicsAPINoYesThe entire user interface of the Cloud version operates through the APIYesYesYesYesYesREST
1Electronic tool basicsExport of all data to ExcelPartialYesIn open source, only iterations, or items which have spent effort logged to them can be exported to excel????YesI pressed 'export', and Taiga said that t will send me an email when the export is ready.. Some 5min later, I received an email with a link to a json dump
2Team-level agileSprintsYesYesYes"Sprint board"YesYesNoNoProjects and milestones. Could you workaround with milestones or task lists?Yes
2Team-level agileRollup of sprint degree of completion in pointsYesYesYesAccording to the manual; didn't check "in person"PartialYesNoNoNo story points; tasks have man-hour estimates and completion in percents (0-100%)Yes
2Team-level agileRollup of sprint degree of completion as effort leftYesYesYesAccording to the manual; didn't check "in person"PartialYesNoPartialCan do rollup of man-hours in tasks and task listsNoPoints are the only unit, and are determined for stories only. Tasks do not have a numerical estimate of any kind
2Team-level agileRollup of sprint velocity in pointsYesYesYesThe velocity chartYesYesNoNoNo story points, to mark a story as done, you have to close all tasks related to it
2Team-level agileRollup of sprint spent effort in man-hoursYesYesPartialCan't specify by sprint, but other "filters" possibleYesYesNoPartial...if you devise a suitable workaround for not having the concep of sprints; e.g. tying task list to a milestone
2Team-level agilePulling stories from multiple different backlogs into a sprintYesYesYesPulling stories from several projects into a sprint is possibleNoPartialNoNoNo concept of backlogs; you could workaround by e.g. having different projects as product, release and sprint level backlogs? Or, use task lists for the levels - that would be quite unwieldy, thoughNo
2Team-level agileSetting more than one person responsible for a story or taskYesYesNoTasks and stories can have only a single assigneeYesYesYesYesNoA single user can be assigned to a story or a task
2Team-level agileBoard view for child storiesNoYesYesScrum and Kanban boards existYesYesYesNoYes
2Team-level agileCustomizable story/task statesNoNoComing in 2015YesCan configure states and allowed changes from one state to anotherNoYesYesNo
2Team-level agileStories separated from tasksYesYesYesYesYesPartialPartialTasks and subtasks; if you consider Tasks = stories, and sub-tasks as tasks, then partialYes
2Team-level agileMan-hour estimates for tasksYesYesYesYesYesNoYesNo
2Team-level agilePoint estimates for storiesYesYesYesYesYesNoNoYes
2Team-level agileSprint burndownYesYesYesYesYesNoNoNoSince tasks don't have estimates, there's no sprint burndown
2Team-level agilePersonal view to collect and organize all of the stories and tasks of a single person across his projectsYesYesYes"My open issues"NoNoNoYesYes
3Project/release level agileProject/release degree of completion in points as function of time (burn-up)YesYesYesThis is called the Version progress reportNoYesNoNoin man-hours
3Project/release level agileProject/release degree of completion as effort leftYesYesYesThis is called the Version workload reportNoYesNoYesin man-hours
3Project/release level agileRollup of project/release velocity in pointsNoYesPartialCan't estimate epics, only issues; so total scope is not visible unless everything has been split into issuesNoYesNoNoYes
Project/release level agileEstimated release date based on past velocityNoYesPartialsee above????No
3Project/release level agileMulti-team project/release developmentYesYesPartialEnabling "Parallel iterations" is currently available as a Labs feature, no date for releaseNoYesNoPartialno concept of teams (or sprints), but you can have as many people work on a project as you like. Could you work around this by creating a task list for each team / iteration?
3Project/release level agilePrioritization of (leaf) stories in rank-ordered listsYesYesYesYesYesYesNoNo story hierarchy; the conceptual model resembles that of Trello's quite closely (Boards = Projects, Task lists = lists, Tasks = Cards, Sub-tasks = checklists)Yes
4Agile product managementCustom burn-ups / burndowns for a set of stories (= roll-up of completion for a higher level story as function of time)NoYesPartialThis is called the Epic progress report. Marked as PARTIAL because epics cannot be nested without add-ons NoNoNoNo
4Agile product managementCustom dashboards composed of key stories, iterations, projects/releases and peopleYesYesYes62 different gadgets that can be pinned to dashboardsNoYesNoNoDid not find custom reports or dashboard customizationNo
4Agile product managementBranch copying (= copying a story and all its child stories with a single operation)NoYesNoNo proper support for story hierachy, see belowNo
4Agile product managementInfinite work item (for example story) hierarchy to enable just-in-time elaboration, estimation and prioritizationYesYesNoIn projects with Scrum boards only (no using epics in Kanban boards). Only two levels: epics and stories (and subtasks); can't be viewed as a tree without addons (see the 'Structure' addon - which I found a bit confusing). Jira Portfolio adds another level on top of epicsNoYesNoNo
4Agile product managementInfinite backlog (= work item container) hierarchythree levelsthree levelsComing in 2015PartialProjects can contain sprints, and that's it. Compared to Agilefant, projects in Jira correspond to Products, Versions correspond to Agilefant's projects, and Sprints to IterationsNoYesNoNoJust projects, which are separate from each other (though people can work for multiple projects and you can move tasks and task lists from one project to another)NoTwo levels: projects and sprints.
4Agile product managementA single work item can reside in multiple work item containers (= backlogs, boards) at the same timeNoNoComing in 2015NoNoNoNoNoNo
4Agile product managementPulling stories from multiple different products into a project/releaseNoNoComing in 2015NoAccording to the documentation: "Versions are points-in-time for a project. "; so, can't contain issues from multiple projects (which correspond to the 'product' as referred to in the criterionNoYesNoNoCould one work around this by creating a project for each of the products, and then one project, and you move the tasks / task lists there... but then you lose the original context. are "separate" from each other, so a team multiple on
4Agile product managementStrategic / business themes with many-to-many relationships to storiesNoYesNoNothing beyond epics; probably a work-around exists be configured via custom attributes and object dependenciesNoYesNoNo
4Agile product managementMulti-project/release product development (many projects working in parallel to advance something)YesYesNoNote, that many of the 'No's in Agile product management can most likely be worked around with configurable issue types. See the link to right for details.NoYesNoNo
4Agile product managementBoard view for parent storiesNoYesNosee aboveNoYesNoNoNo
4Agile product managementStory business valueYesYesYesNoYesNoNoNo
4Agile product managementStory labelingYesYesYesNoYesYesNoYes
4Agile product managementFiltering of views based on story attributesNoYesYesPartialCan filter based on story status and labels
5Kanban supportWork-in-progress limits for storiesNoNoYesNoYesNoNoYes
5Kanban supportWork-in-progress limits for tasksNoNoYesNoYesNoNoNo
5Kanban supportWork-in-progress limits for peopleNoNoNoNoNoNoNoNo
5Kanban supportWork-in-progress limits for backlogsNoNoNoNoYesNoNoNo
5Kanban supportPeople load trackingYesNoPartialUser workload report shows remaining hours for a person per projectNoYesNoYes
6Bells & WhistlesExplicit defect trackingNoNoYesNoYesNoNoYesIssues can be entered, catogirized and morphed into user stories
6Bells & WhistlesPrinting stories and tasksNoNoNoUsed to be in Greenhopper; now available in Jira Classic only, which is not actively developed; available as an add-in to Download version of Jira ("Agile Cards"), which costs ~10$/userNoYesNoNo
6Bells & WhistlesStory templatesPartialPartialYou can create a set of template stories to a backlog and create copies of these as the basis for new storiesYesIssue templatesNoYesYesYes
6Bells & WhistlesCustomizable fields for objects (stories, tasks, people, backlogs, ...)NoNoPartialCustom fields can be added for issues, but not for other objectsNoPartialNoNo fields for user stories
6Bells & WhistlesExcplicit story acceptance criteriaNoYesPartialCan be added as a custom field; also available as an add-onNoYesNoNo
6Bells & WhistlesCustomizable workflow between statesNoNoYesNoYesYesNoNo
6Bells & WhistlesAttachmentsNoYesYesAttachments to issues and sub-tasks; max size 10MB per attachments in SaaS versionNoYesYesYesYes
6Bells & WhistlesFile sharing integrationNoNoYesSeveral exist as paid-for plugin; e.g. zapier, etc.NoNoNoYes
6Bells & WhistlesStory dependenciesNoYesPartialCan be done by linking issues; however, if linking issues is used also for something else, e.g. creating an infinite story hierarchy, can become confusing. Perhaps, using custom fields could helpNoYesNoYes
6Bells & WhistlesTeam / organization chat in-appNoNoYesAtlassian HipChat is free for OnDemand Jira AgileNoNoNoNoPartialHipChat integration
9Open Source?YesNoRuns on MySQL and TomcatNoNoNoNoNoYes
10Fairness of reviewReached out to a representative of the tool for comments on assessmentYesYesNoYesNoNoNoNot yet
10Fairness of reviewGot comments on assessment from a representative of the toolYesYesNoNoNot yet
10Fairness of reviewReviewed and incorporated the comments into the reviewYesYesNoNoNot yet