A kingdom for a decent tool review

Backlog tools are seldom the first-order problem in an organization. And even the best ones can’t solve the first-order problems for you. However, bad tools do get directly in the way of your transformation efforts. That’s why it’s useful to tell one from the other.



– God bless me, but the backlog, is very like a list! (adapted from John Godfrey Saxe)

Having been involved in the development of a backlog tool (that’s Agilefant, nowadays known also as Nektion) since 2004, I’ve been a long time dismayed by the quality of the tool reviews out there.

I know, it’s individuals and interactions over processes and tools but bear with me here. Tools are seldom the first-order problem and even the best tools can’t save you. However, bad tools do get directly in the way of your transformation efforts. That’s why it’s useful to tell one from the other.

Unfortunately, most tool reviews seem to be camouflaged marketinghuge tables or lists consisting of extremely shallow observations of the tools’ capabilities and/or copy-paste from the vendor’s sites. I honestly don’t know why these are done in the first place! Perhaps virtual name-dropping gets you traffic?

Gartner’s magic quadrant reports seem to come the closest, but they, too, suffer from staying at a superficial level.

Another confounding factor is that as SAFe and the like spread further, the vendors’ marketing folk pick up that this is something their product should be able to do as well. And they go and change their website to say that surely their product supports SAFe whether or not that actually is evenclosely the case in reality. Of course similar things tend to happen to everything which has demand – like it has for AgileScrumLean or Kanban.

If there was a clear upside to doing good tool reviews, surely someone would have done so already. And kept at it, because whenever I have found something that might be useful, it’s cut short after some two posts.

So, while producing useful tool reviews will probably prove to be a futile effort in ways I don’t yet foresee, I’m willing to take my chances and try it.

But before going into the actual reviews, in this post I’ll lay some necessary groundwork.


In my experience, the “goodness” of a tool really comes down to three things:

  1. The conceptual strength of the tool
  2. How easy it is to get started
  3. To what degree you can tailor and adapt the tool as you learn more of what you need

I’ll try to elaborate a bit on what I mean by these below.


At the heart of the challenge is the concept of ‘product backlog’ and being able to support how it’s supposed to work. While that might sound simple – “just list the most important items” – taking a closer look at what has been said about it will reveal a vast landscape of needs.

Exploring that further would be a subject of another post itself, but you can get a taste of what I mean by skimming through chapter 2 of “Towards Agile Product and Portfolio Management”.


The ease of getting started is in direct contradiction to the conceptual strength of the tool. This makes things challenging.

I’ve seen cases where people want to start by getting a board-like view for the company’s high-level initiatives (a ‘portfolio kanban’, if you will). But equally crucial is the need to support a single team in its daily work.

While Trello might, with individual boards, cater to both of these needs, its conceptual strength stops short when people start wanting to combine these views into a coherent whole.

From the portfolio perspective this can expand into wanting swim-lanes for ‘strategic themes’, roll-upped progress metrics based on the epics’ breakdown and so on.

Likewise, on the level of the individual team, being able to tie the team-level work items to the big audacious hairy goals of the company is something that may help guide the decisions. As expert work such as programming is essentially problem-solving, and there are many ways to solve problems, an understanding of the big picture helps the team align their solutions to the company goals.

Either way, you have to start somewhere, and if the conceptual strength gets in the way of just jotting things down as you would on post-it notes or a paper notebook, it will cripple the drive.


To be able to combine both the easiness of getting started and the conceptual strength, you need to be able to adapt and grow the tool as you need to, creating new concepts and relationships and renaming the old ones.

This makes it possible for the tooling to grow with you. Otherwise, you have to force your way of working to the model enforced by the tool. This could be a “big hairy proven framework” which incarnates the latest version of the Unified Software Development Processes or Capability Maturity Models of late 1990s – or something else which doesn’t quite fit your reality.

No matter how enlightened, if a big model is forced on the organization too soon, the result will be co-optation: your system projects will be cast as ‘release trains’, your component teams as ‘feature teams’, and your non-customer facing business units as ‘value streams’. In such a scenario, the tooling wille become a strait jacket. In such a case, if you are going through with your transformation, not only will you have to change the organization, but also dismantle the tooling.

An important but fairly simple as well as often overlooked part of tailoring is being able to rename the concepts in the tool.

While choice of names will matter in the long-run (think of for example, ‘projects’ vs #noprojects), in a transformation you want to be able to pick your fights.

Will you, from the get-go, have to convince your C-level managers to talk of Epics, Sagas, Novels and Steam Trains or simply Business Value Proposals and Projects like they’ve used to?


At the time of writing this, I’m considering to take the following tools under a closer scrutiny; in alphabetical order, these are:

  • Agilecraft – the self-claimed leader which to date has not lent itself for easy sign-up and tire-kicking
  • Agilefant – the open source version from 2014 – as a baseline
  • Favro – the offspring of Hansoft from Sweden
  • Google Sheets – not because spreadsheets are that good but because they just might be better than anything else
  • Leankit– I’ve heard good things about this, though nowadays it has been acquired by the more traditional vendor Planview
  • CA Agile Central (formerly known as Rally) – first IPO, then going to CA to die?
  • Taiga – the other open source tool worth mentioning
  • Targetprocess – long-standing original thinking from Belarus
  • VersionOne – besides Rally, the other U.S. based ‘enterprise agile’ vendor; nowadays acquired by CollabNet, which already many years ago swalloved an early player, ScrumWorks

Of the obvious possible choices, I’m skipping JIRA, at least for now. This is because of my customer engagements. I am anyhow in the process of writing a separate thread of posts covering it.

I’m also skipping big software houses’ such as HP’s, IBM’s and Microsoft’s offerings, even though nowadays they, too, claim to support “agile”. I may be wrong in doing so, but for some reasons I can’t quite verbalize, I don’t feel it’s relevant to address them. And you can read how they by some strange mechanism get put up as leaders anyway from any Gartner or Forrester report.

So that’s it for the groundwork, and stay tuned for the first review. I will be backlinking the results to this post, and following Nitor on Twitter you’ll hear about it among the first.

If you have suggestions for tools which I should take a closer look at, or want to affect the order in which I go through the candidates, get in touch!

Culture follows structure


– Culture is the product of the system; change the system and behavior changes
(John Seddon)

As a community, advocates of agile often seem preoccupied with the notions of culture and mindset. Even when people who have been involved in successful transformations actually talk about structural changes, they tend to refer to it as “changing the culture” – for example in these presentations by Mirette Kangas and Fred George.

This emphasis on culture paints the picture where “if you just change hearts & minds and train everyone, self-organization happens and things fall into place”.

My journeys in enterprises have taken me to places where seemingly everyone was trained in “agile” but as the key structures remained unchanged, the impediments persisted.

In one organization, “Done” did not mean that something was deployed and running in production. Done merely meant that the feature had been handed off to the Q&A and release organization. And as there was no easy way to measure the time in the Q&A and release phase, they measured the time spent in the development phase and called it the ‘lead time’. As we pointed this out and went on to explore this further, we discovered that for features that had been developed in 1-2 months, the total lead time could be as long as 18 months.

Another common example of a structural problem comes from contractual issues. In one organization, the people were excited about the new ways of working, and most had been trained as well. But upon asking if they could mix the current, component based teams to form cross-functional feature teams, the answer was a disheartened sigh.

After a bit of prodding, it was revealed that because of the outsourcing contracts in place, this was considered impossible. Moreover, the outsourcing had resulted in a considerable amount of offshoring. This had led into people on different sites specializing further into certain kinds of tasks. Because everybody had to have something to work on, prioritizing according to highest customer value was not possible.

And as the people who were responsible for the contracts did not feel the pain, nothing was done about these issues when the contracts were eventually renewed.

You cant’ change structure bottom-up

Organizations tend to grow so that when problems occur, specialists are hired to take care of them. Over time this results in organizing such specialists into their own resource pools. Then work gets done by handing it over from one pool to another. Such structures are in direct contrast with the notion of cross-functional feature teams and organizing around delivering value to the customers.

In my experience, the drive to adopt agile often arrives at organizations at the level of development managers and team leads. However, the prevailing structures can only be changed by C-level executives, and hiring a “VP of agile” will not be enough.

Take it from the thought leaders

It doesn’t help that currently the most popular framework for scaling agile, SAFe, is not that explicit (at least compared to the total amount of material in the framework) of the need to change the structures. Examining the structures lurks under the notion of “applying systems thinking”.

To me SAFe has seemed almost surprisingly agnostic about the matter as it allows “development value streams” and says that “there is no one right answer”. The fine print does warn though that with development value streams you will end up with a lot of dependencies.

I had the chance of discussing this with folks from Scaled Agile Inc. They consider it a conscious choice: it’s better to get a foot in the door and then proceed to help the client from there instead of getting completely turned down as a result of proposing radical changes up front.

While that may be true, there are thought leaders who criticize SAFe from SAFe from the point of view that because of the sheer amount of material, it can easily turn into scaffolding for the legacy organization to hide behind.

Also some thought leaders have taken the notion of changing the structure as a central part of their teaching. In fact, they consider the preoccupation with culture as failure demand caused by the inability to change structures.

They articulate this so well that I’ll step aside here and provide a few pointers so you can delve deeper into the matter.

The ones I’ve raised here work quite well even if you only listen to the audio, so you can explore them while for example commuting. These speakers have also lot of other presentations available on Youtube which further deepens the point. Here’ I’ve tried to pick those presentations that most directly cover the point I’m trying to convey and put them into an order they are most easily approachable. Enjoy!

Four presentations worth checking out


Author Presentation Quote
Mike Cottmeyer (2017)
Is culture really the issue? (Youtube, podcast) “Most organizations are deeply flawed from the perspective of delivering value. Teaching them to want something is not enough. At some point you have to do the work of removing the impediments. And if the impediment is 2M lines of legacy mainframe code in a key business system, you just fix by the next sprint”
Craig Larman (2016)
More with LeSS: a decade of descaling with LeSS @ Agile Munich meetup (Youtube) “I can quickly spot a young naive change person when they say you have to change culture; you can’t change culture”
Jason Little (2017)
Rethinking agile transformation (Youtube) @ Agile Montreal “Co-optation is the most common mode I see. A VP of agile is hired, the structures persist, we do things as we always did them, and the agile is put in front of everything.”
Dan North (2017)
How to break the rules @ Goto 2017 (Youtube) “In companies we have a huge number of rules to cope with the limitations of the old way of working. In a transformation we not only have to dismantle them but also come up with the new and mostly very different kinds of rules to manage the new limitations”


The simplest way to run SAFe with JIRA

Ship in a Bottle Seute Deern 1

“Going agile with JIRA often looks like learning to sail with a ship you’ve built yourself – in a bottle” – Dr. Agilefant, 2016

Somewhere in your large, complex organization there are people who think you should strive for a more agile way of working. Some of those people may think that the Scaled Agile Framework (SAFe™) could be a good blueprint to follow.

While there are alternatives, let’s suppose you want or have to use your existing JIRA to support also the new way of working.

Mismatch of models

SAFe is less complicated than it may seem at a first glance. The difficulties stem from JIRA’s conceptual model, which does not match what is suggested by SAFe. On top of that your organizational design and/or constraints posed by your suppliers or customers probably do not match the set-up suggested by SAFe either, but that is the subject of another post.

JIRA natively has a three level requirements abstraction model (Epics, Stories and Sub-Tasks), but the terms are not configurable. Sure, you could define new issue types with the proper naming, but the terms in the UI will remain the same. This means that at least some mental mapping is required from the users. And of course, a three-level work item breakdown does not scale to a four-level SAFe.

In addition, JIRA’s single level non-nested work containers (Projects) means that at least some workarounds will be needed to express SAFe’s levels of planning.

Typical pitfalls

JIRA originated as an in-house bug tracker. It’s first commercial release was in 2002, and while plenty of features have since been added, little has been taken out. While this makes JIRA highly configurable, it is easy to go overboard in terms of the workarounds.

A common pitfall we’ve seen is that prevailing impediments to agile such as a function or system based organization are replicated into JIRA as some key concept – typically as Projects. This further cements the existing structures – which in most cases should be dismantled and rebuilt around customer value delivery.

Another common challenge stems from attempting to overcome the limits of JIRA with plug-ins. While this is possible – to a degree – it leads to a more complicated set-up. And even with a willing, SAFe-trained organization and detailed instructions, the supposed way to use JIRA can prove too complex to grasp.

The result is a constant demand for training to grasp the complicated JIRA-with-plugins set-up. People also simply go around the complicatedness and make up their own special ways of using the tools, which makes progress roll-ups difficult and improving the ways of working via measurements impossible.

Resorting to ‘shadow accounting with MS Excel’ is also fairly common solution even in cases where JIRA is seemingly being used.

The simplest way

In matching SAFe and JIRA, you have to make some compromises. You should strive to avoid design decisions that directly get in the way of the transformation. You don’t want to simultaneously deal with both the resistance to the new way of working and the complicatedness of the desired JIRA usage model.

Having observed JIRA usage in a number of organizations striving toward large-scale agile we have devised a blueprint for how to implement ‘three-level’ SAFe (known as ‘Portfolio SAFe’ in the 4.5.1 version) using JIRA.

We’ve deliberately aimed at the simplest possible model doable with plain vanilla JIRA. While it is by no means perfect, it presents a sane starting point. The mapping of the key concepts is described in the table below.


SAFe concept JIRA concept Notes
Portfolio Project JIRA’s projects have no beginning or end, and they are the highest level wrapper of content
Epic Epic Workflow: funnel, review, analysis, backlog, implementing, done
Feature Custom defined issuetype ‘Feature’ Use JIRA’s native ‘epic link’ to connect Features to Epics. Workflow: funnel, analysis, backlog, implementing, done
Story Story Use the child-parent issue link to connect to Features; workflow funnel, backlog, sprint, done
(Bug) Bug Use the child-parent issue link to connect to Features; workflow funnel, backlog, fixing, done
Strategic theme Label Manually add at least to Epics; and then to the depth deemed relevant
Key system being worked on Component Add components to the depth of the work breakdown you have sibling work items which concern different components
Team, Train, Solution, Portfolio A single JIRA user for each party Multiple people use the same login. Everyone should have access rights to ‘everything’ except admin functionality
Portfolio kanban Kanban board One for each portfolio
Program kanban Kanban board One for each train; program increments are not explicitly modeled; Features in the status ‘implementing’ are considered to be in the current program increment
Team board Scrum or kanban board One for each team, according to their preference
PI Objective Online shared spreadsheet Not because it’s are good but because it’s better than what you’ll hack to JIRA – especially from the business owners you’ll want to get engaged.

Also, spreadsheet works better than JIRA for the most important metric suggested by SAFe – program predictability based on PI Objectives’ achieved business values

Evaluating the design choices

The choices made above come with good, bad and an ugly side. The Good is what we see as the upside of the choices, and The Bad as the downsides which we see that can be overcome. The Ugly refers to those downsides which are inherent to plain vanilla JIRA and can’t easily be worked around.

The Good

  • Very little mental mapping required; JIRA concepts are not forced to represent other things than their name implies
  • User per party and no access restrictions support the notion of shared responsibility and promotes the importance of frequent communication
  • Can be moved to in an existing JIRA set-up; changes are restricted to a single project and new ‘party’ users
  • Possible with plain vanilla JIRA
  • Not necessary to use JIRA’s rather convoluted sprint functionality
  • Virtually non-existent licensing cost (only a handful of user seats required)
  • Frees the parties to organize as they wish as a team (do more detailed coordination on a physical board, work as a mob, and so on)
  • Changing the legacy organization structure based around systems is a key challenge in most organizations; including this reality via modeling systems explicitly as Components can be leveraged to spot and eliminate dependencies as well as problems with the current organizational design

The Bad

  • Unconventional design choices (compared to how JIRA is in my experience commonly used) may cause resistance in moving to the model
    • No user per a living person
      • However, the model does not fundamentally change if the team-user is replaced with a person-user; you can still model the teams and trains as groups and use these in queries
    • No detailed user access control; everything is shared;
  • To leverage strategic themes in querying lower level items, you’ll need to add them by hand all the way to the story level
  • JIRAs label editor (or rather, the lack of one) makes the usage of Strategic themes error-prone
  • One might argue that having ‘Bug’ as its own issue type is against the grain of ‘the simplest thing that might work’; however, our experience is that sooner or later you’ll want to be able to discern between fixing and enhancing based on work item type; this also frees using labels for other purposes

The Ugly

  • Plain vanilla JQL is not powerful enough to support many queries which can be seen as interesting to running a SAFe-like process; in a future blog post will show what exactly I mean by this
    • However, the most important metric of SAFe has to do with PI Objectives and those we suggest should not be in JIRA at all
    • Also, the plugins required to ease the needed queries and detailed filtering work around the most critical issues are relatively inexpensive; we will take a more detailed look of this in a future post
  • Hard typing of requirements and no support for N-level work item splitting and; why you would want to avoid the former and have the latter is the subject of another (rather long) post by itself; but it has to do with the heart of agile requirements management – iterative refinement and keeping the batch sizes manageable
  • Program boards with dependency visualization can’t be done with plain vanilla JIRA; I predict sooner or later someone will do a free plugin compatible with Cloud JIRA

Running the model

We are running a model very similar to the one described in a couple of customer cases. In the future we will be writing about for example how PI and sprint plannings work in this model, and also present a set of example queries to questions commonly asked by the key SAFe-org stakeholders (such as ‘show me all the work related to this epic’ or ‘show all the work related to this strategic theme).

To be among the first to get the link, follow @dragilefant on Twitter or LinkedIn or @NitorCreations 

To be among the first to get the link, follow Nitor on Twitter or me on LinkedIn.
And should you be running something similar – or even try this model out – we’d very much like to hear of your experiences.

Top ten lean and agile presentations on YouTube

As the year begins, it’s time to reflect on what we’ve learned during the past 20 years of the things we today call lean and agile. I’ve compiled a top list of lean and agile presentations which to me have been especially intriguing and inspiring. The presentations are not in any particular order.

Nowadays most of us have a lot more ear-time than reading time. So just plug in your wireless headphone and dig in, whether you’re commuting, doing the dishes or something else where your brainwaves could use a little simulation. If you happen to drive a motorized vehicle while listening to these, be sure also to look at the road ahead instead of the slides…

Best of 2018 to everyone!

Fred George @ Goto 2015: The secret assumption of agile

“In the 70’s we could code together with the customer. As the industry, the companies and the projects got bigger, we told the customers to go away, as the coding now took a little longer time”


Jeff Patton: User story mapping

“Do you think they’re using Jira for planning at Atlassian?”

Jeff Patton Digs into the concept of user stories, how to use (and not to use them)


Chet Hendrickson and Ron Jeffries: The nature of software development

“SAFe certainly is scaled, and it most certainly is a framework”


Bob Martin: The future of programming

In 1938 Turing described the modern computer. Three years later, he found himself cracking signals with an ancient machine. Kind of makes me think of the bug tracker I’m driving the folks to use in order to manage the building of their next generation whatever.


Allen Holub: #noestimates

How many man-hours was a story point, again?


James Coplien: How Agile and OO have lost their way together

“The Japanese fooled Americans into looking for root causes in complex adaptive systems”


Woody Zuill: Mob programming – a whole team approach

“With mob programming, most of what destroys productivity just faded away in our case”


Joshua Kerievsky: Modern agile

Modern – or perhaps agile how it was all along, as compiled for the contemporary audience.


Bas Vodde: The Story of LeSS

How to solve dependencies and why in practice it can be hard to tailor a big framework method down to your organization


Craig Larman: Practices for Scaling Lean and Agile Development

The competitive contract game, component teams and the prerequisite for scaling agile