Blanket JIRA rollouts

I’m not 100% sure, but I’m starting to think that the moment a team or organisation introduces the JIRA / Confluence combo as tools to manage non-development teams, it is probably the moment to consider renegotiating a fixed deliverables contract with periodic checkpoints (to limit daily micro-management which JIRA can encourage), or to simply walk away…

The blanket introduction of such tools across all workers probably says more about a process led, controlling culture interested in tasks and time rather than value and output. And I haven’t even mentioned what it may mean to respecting differences between people and their individual values. There are not many times (any?) where I’ve seen the mass rollout of JIRA / Confluence actually improve the output of a team, over and above what they could do without it.  

Perhaps an interview question I might consider in the future may be along the lines of…
Q: “Do you use JIRA for tracking non-development work?” 
A: “Yes, we do”
Q: “How’s that working out for you and your staff?”

Frank Ray

Did you know successful projects depend upon healthy relationships between the people involved? Trust, honesty and openness are required so that problems and issues can be frankly discussed and nipped in the bud. This is how we conduct business at Frank Ray & Associates, a software engineering consultancy I founded. You can also reach me directly at

Leave a Reply