­a tool that visualizes plans, flow and forecasts in Jira from different perspectives

Sometimes it’s hard to see the forest for the trees and sometimes we need to be able to study the leaves to solve a minor matter. The forest, with its trees and their leaves, is our common plan. JIRA contains the plan and allows us to walk around in the forest and look at the trees and also zoom in so we can see all the details of the leaves. That is not enough. We also need to be able to zoom out and see the forest to understand more of the whole.

Scope360° helps us look at the forest or part of the forest from different perspectives.

medium medium medium
Forest Trees Leaves


In addition to the three perspectives described briefly below, Scope360° offers assistance in improving the ability to navigate in JIRA as well as creating the queries needed to view the different perspectives.

Plan Flow Forecast
medium medium medium
The plan is visualized through a number of views
- Dependency board - shows which deliveries each team has planned, including dependencies to other teams
- Plan view - shows the team’s plans iteration for iteration
- Status report - gives a status overview measured in the number of issues in each JIRA epic that has status to do, in progress and done.
Learn more
The flow perspective provides different views of our capacity by visualizing the flow in terms of CFD, Throughput and lead times.
Learn more
Forecast is made by visualizing the outcome of a Monte Carlo simulation. The simulation uses previous throughput to calculate possible outcomes ahead and the result is a forecast based on historical data from the latest iterations.
Learn more



With different dimensions such as purpose, organization and time, the opportunity to answer ad-hoc questions arises. Questions like; When will a group of teams be ready to deliver a specific initiative and what does the progress look like. The core of each dimension is initiative, team and iteration, but can also be project, component, program, ART, solution, portfolio, program increment or something else.

It is the connection between JIRA issues together with these dimensions that identifies a scope that can be visualized in Scope360°.

The dimensions can be implemented in JIRA in different ways and usually some of them already exist. Scope360° does not depend on the dimensions being set in a special way in JIRA. See About Dimensions View for en example of dimensions.


Dependency Board Status Report Plan
large large large
CFD Throughput Forecast
large large large


The product family of Scope360° is evolving. Currently these products are available.

Scope360° Professional Scope360° Enterprise
Scope360° Professional provides Scope360° functionality to users without the need for a enterprise config1.

Scope360° Light
(Flow Companion for Jira)
This funtionality is now provided in Scope360°.
Full functionality of Scope360° including a company wide common config1 that supports all Jira users with an enhanced Jira experience with reports from Plan, Flow and Forecast perspective.

Please visit Chrome Web Store to install Scope360° for Jira.

  1. A config contains the translation from Jira fields to Scope360° Dimensions 2


Please contact us if you have any questions or want to know more about Scope360°


As many great products, Scope360° was created out of frustration and a need for better visualizations and tools, to plan better based on data and create a model to follow constant updates.

Magnus and Tom have worked together in different ways since 2012. The journey of Scope360° started with a Chrome extension written by Magnus to enhance visualization in TFS and that work transformed into Flow Companion for Jira.

Inspired by Magnus, Tom started to make visualizations of dependencies and that resulted in a extension called Program Reports. A few years ago both tools had evolved and matured in a way that it made sense to combine them and Scope360° was born.

Together with Aliby - The pink company - they have gone from eight years of ”basement work” to a commercial product and a company. All energiezed by a partnership with born {digital}.

person person
Magnus Siverbrant Tom Mårdh


This is a index of the documentation in this site grouped by category.


  • Flow
  • Forecast
  • Plan
  • release-note

  • Scope360° Version 2024.07.02 <-- Next
  • Scope360° Version 2024.06.18
  • Scope360° Version 2024.06.17
  • Scope360° Version 2024.06.15
  • Scope360° Version 2024.05.27
  • Scope360° Version 2024.05.18
  • Scope360° Version 2024.04.25
  • Scope360° Version 2024.04.10
  • Scope360° Version 2024.04.07
  • Scope360° Version 2024.04.03
  • Scope360° Version 2024.03.16
  • Scope360° Version 2024.03.07
  • Scope360° Version 2024.02.06
  • Scope360° Version 2024.01.19
  • Scope360° Version 2024.01.16
  • Scope360° Version 2024.01.06
  • Scope360° Version 2023.12.04
  • Scope360° Version 2023.11.16
  • Scope360° Version 2023.10.10
  • Scope360° Version 2023.09.25
  • Scope360° Version 2023.09.03
  • Scope360° Version 2023.05.19
  • Scope360° Version 2023.04.02
  • Scope360° Version 2023.01.31
  • Scope360° Version 2023.01.05
  • Scope360° Version 2022.12.20
  • Scope360° Version 2022.11.28
  • Scope360° Version 2022.11.23
  • Scope360° Version 2022.07.05
  • Scope360° Version 2022.05.22
  • Scope360° Version 2022.04.10
  • Scope360° Version 2022.02.13
  • Scope360° Version 2022.01.21
  • Scope360° Version 2022.01.19
  • Scope360° Version 2021.12.26
  • Scope360° Version 2021.12.18
  • Scope360° Version 2021.11.23
  • Scope360° Version 2021.11.13
  • Scope360° Version 2021.11.07
  • Scope360° Version 2021.10.30
  • Scope360° Version 2021.10.18
  • Scope360° Version 2021.10.02
  • Scope360° Version 2021.09.18
  • Scope360° Version 2021.08.21
  • Plan

  • Information Flow from a Plan Perspective
  • Other

  • Privacy Policy