Analyze team focus and time allocation with the Investment Distribution view

Are you spending enough time on the most important priorities? Do you keep a healthy balance between roadmap work, maintenance, and unplanned ad hoc tasks?

The purpose of prioritization is to identify which problems and their solutions have the potential to successfully drive the most important outcomes. Whatever the planning or prioritization process behind this, for development teams this ultimately manifests in the form of some unit of work (Epics & Stories, Projects, Initiatives etc.). Simply put, teams should spend enough time on the highly prioritized activities in order to realize the positive outcome in a timely manner.

However, there are some common obstacles teams (and organizations) face when trying to make this seemingly simple thing a reality. There are always multiple priorities to juggle, with planned roadmap work, discovery work (often invisible), unplanned work and interruptions, as well as bugs and other types of maintenance work. How a team manages their focus between this mix of work can be a great indication of the health of the team.

The best teams understand where their time is going and are able to balance between the most impactful work and housekeeping. This ensures they can reach the high-impact business objectives and solve the right problems in the short term, without compromising the capability to do so in the long term.

The Investment Distribution view introduces transparency to different categories of work. It help teams understand how much of their time they are allocating to their biggest priorities. It also provides a feedback loop for teams that enables them to stick to their target work allocation (eg. “we want to spend 20% of our time on fixing bugs”), or course-correct when they see an alarming trend (eg. "we've spent 30% less on roadmap work than in previous quarter").


Common problems with focus on high priorities

When organizations mature and grow there tends to be an ever-increasing number of problems and issues competing for the attention of individual teams. This can result in teams spreading their focus too thin, and not being able to spend enough time on their most important priority.

It's not difficult to imagine what the difference is between a team that's spending 20% of their time towards a goal, versus one that spends 40%: the time to deliver a solution most likely at least doubles. This isn't good news for the team or the organization – but there's a huge opportunity on the flip side: teams who can improve roadmap focus can drastically improve their impact.

Follow up on high-priority work

⚠️ Note: Getting the full benefits of Investment Distribution depends on reliably linking Pull Requests with Issues. This is something you should discuss and agree to do as a team.

It can be easy to get lost in the sea of problems and day-to-day work, especially without a proper way to measure what kind of work a team is spending their days and weeks on. The Investment Distribution view brings transparency to this data, and especially the trend over time.

The view can be used to track the amount of time spent on the important categories of work. For instance, if the most important outcomes are the result of finishing certain Jira Epics, following the investment in them (week over week, month over month) can be eye-opening:

  • Look out for decreasing trends in the most important work. This increases your odds of catching a problem early and correcting course before it becomes a real problem.
  • Are you spending less than 50% of your time on high priorities? Low numbers in the absolute time spent on the most important category might mean your team has too many items to focus on, or that it's not clear how to progress further with the important projects.
  • Is a majority of your time going to bug fixing and maintenance work? An increasing trend in the amount of bug fixing and maintenance work can indicate a problem with the team health. This might require an action such as investing into infrastructure, or addressing some of the technical debt the team has accrued.
  • Are you spending an increasing amount of time with ad hoc tasks? When organizations and systems grow, complexity grows with them. It's sometimes easy to get overwhelmed by the amount of goals, opportunities and the difficulty of getting complex problems solved. This can cause teams and individuals to fall back to simple, reactive tasks which are easy to complete, but time spent on them might not maximize the impact of the team. 
  • Do you have a lot of unlinked work? Drawing good conclusions without transparency to a major share of the work can be difficult. Creating routines to link issues and pull requests, and categorizing ad hoc work pays off and enables the team to make well-informed decisions to improve their performance.

In the real world, there are rarely any silver-bullet solutions for the potential problems indicated by the Investment Distribution. They should be used as discussion starters to improve the focus and speed of delivery as a team.

Configuring investment categories

You can also customize how you categorize issues to ensure the grouping is relevant to your organization.

Understanding Investment Distribution data

Investment distribution shows activity on pull requests and child issues grouped by investment category.

The work is measured in terms of issues completed and pull requests merged. We do this in order to account for both invisible work that might not be connected to pull requests (eg. some DevOps work, or work spent on compliance or security) as well as the deployment of new code.

More specifically, the way we collect and group data for the investment distribution report is:
  1. Look up all members of the selected team
  2. Look up all work items (PR merges and issue completions) done by those people
  3. Determine the investment category for each work item (depending on the rules you've set up, and any manual assignments you've made for individual PR's)
  4. Group the work items based on their investment category (these categories are mutually exclusive and collectively exhaustive)
  5. Within each group, group again based on the highest level issue the work belongs to which has the same investment category. That is, if multiple tasks belong to the same story, group the ones with the same investment category as the story under it. Those with a different investment category will stand on their own, possibly with their child issues also grouped under them if they have a matching investment categories.

Why am I seeing issues that belong to another team?

If members of the selected team have done work towards issues belonging to other teams, those issues will show up. Think this is not a bug, but a feature: the team is investing its time somewhere, and the report shows you where that investment goes, even if it's not for the things you might've expected.