White Papers

Whitepaper: The Real Cost of Misusing Jira

Wednesday, November 21, 2018

This is part of a series of abridged white papers intended as quick reference sources for busy managers interested in the subject matter and faced with limited time to absorb lengthy research documentation.

It is based on research undertaken by Plandek drawn from anonymised data observed across a range of clients – from small start ups to large corporates with large scale, distributed Agile teams.

Purpose of this Paper

The analysis presented below is focused on the software development process and is based on analysis across a representative range of Jira users in large corporates, SMEs and start-ups.  It is designed to help strike the optimum balance of Jira usage within the software development team, so that Jira does the job that it was designed to do - but does not over-burden the engineering team with bureaucracy.

The paper identifies the most serious (and common) misuses of Jira that prevent the efficient functioning of teams within an Agile environment.

Correcting such Jira misuse will have a big impact on overall project productivity and predictability. [This can be done using Plandek as it tracks Jira use/misuse by project and team and therefore is a key tool in greatly improving Jira (and related process) accuracy within teams.]

Scope of the Analysis

The proprietary analysis is based on Agile principles and experience of working with clients and analysing anonymised data from strongly performing and poorly performing Agile software development projects observed between September 2017 and August 2018.  

The Plandek analytics platform surfaces over 120 metrics at project, team and individual level across the history of a project.  As per Figure 1 overleaf, Plandek collects data from four key sources:  

1. The complete history of tickets residing within workflow management tools like Jira; as well as:
2. Meta-data from code repositories to review how/when code has been committed and by whom
3. Code quality tools
4. Time trackers to show resource time (and cost) spend.  

Plandek is therefore focused specifically on the activity of software development teams and related QA functions. Plandek does not yet analyse data from DevOps activity where completed code is integrated and deployed to a live environment.  

As a result, the scope of this Whitepaper, is the use/misuse of Jira in the software development stage of the process only.  The focus is specifically on how Jira is used – and not a broader critique of processes and interactions (e.g. between stakeholders and engineering) that also heavily affect team and project efficiency.

All the metrics discussed are easily viewable within the Plandek analytics platform. Plandek currently integrates with the Atlassian stack – the analysis is therefore focused around companies using Jira as their principle workflow management tool.

Read the complete whitepaper here

Download white paper
News From Our Blog

Related Posts

White Papers

Whitepaper: Achieving Agile Engineering Excellence Through Continuous Improvement

White Papers

Whitepaper: The Six Key Drivers of Agile Project Productivity and Predictability

White Papers

Whitepaper: The Real Cost of Misusing Jira

View all the latest blog posts