Advanced Reporting and Custom Dashboards

01Advanced BI

• Dashboards embedded in Orangescrum

  Full business intelligence dashboards render inside the product, not in a separate tab somebody has to be told about.

• No second login

  A short lived token is issued for you behind the scenes, so nobody manages a second set of credentials.

• Your data and nobody else's

  In Cloud a company filter is written into every token before the dashboard runs, and in Self-Hosted the BI instance is your own.

• Reads live project data

  There is no nightly export to wait for, so the dashboard shows what is true now.

• Pick which dashboards appear

  Choose which dashboards are attached to your account, and add or remove several at a time.

• Dashboards get their own menu

  Attached dashboards appear as menu entries, split between analytics and reports so people find the right one.

• Connect your own instance

  In the Self-Hosted edition you point Orangescrum at your own BI server and it stays under your control.

• The current context is passed through

  The project or company you are looking at is handed to the dashboard, so it opens already scoped.

02Dashboards

• A widget set you assemble

  Build the screen your audience needs from more than twenty widgets rather than accepting one fixed layout.

• Widgets respect permissions

  A widget only appears for people whose role is allowed to see the numbers behind it.

• Hide a widget for everybody

  In the Self-Hosted edition an owner can switch a widget off across the whole organisation.

• Cards, charts, and lists together

  Counts, donuts, bar charts, tables, and activity feeds all sit on the same screen.

03Delivery

• A velocity chart

  How much the team actually completes per sprint, so planning is based on evidence.

• Sprint burndown

  Work remaining against time remaining, so a sprint that will not land is visible before the last day.

• A completed sprint report

  What was committed, what shipped, and what carried over, with a PDF you can send on.

• Average age of open work

  How long the things still open have been open, which is usually the number nobody wants to look at.

• Resolution time

  How long work takes from being raised to being resolved, over the period you choose.

• Created against resolved

  Whether the team is keeping up with incoming work or falling behind it.

• Recently created work and time since it moved

  Two reports that show what has just arrived and what has been sitting untouched.

• A task cycle report

  How long work spends moving through your statuses, so you can find the stage that is slow.

• A probabilistic forecast

  In the Self-Hosted edition, a forecast built from your own delivery history rather than an optimistic guess.

04Plan against reality

• Planned versus actual

  Compare estimated effort and dates with what really happened, and choose the columns you want to see.

• Why a due date moved

  Every date change carries a reason from a list you control, and the report shows them by project and person.

• Progress by weight, points, or hours

  In the Self-Hosted edition, decide whether progress counts tasks, weightings, story points, or estimated hours.

05Capacity

• Resource utilisation

  Where each person's logged hours actually went, split billable and non billable, down to the task.

• Resource allocation by role and project

  Estimated against spent hours, week by week, drilled from role to project to person.

• Team utilisation

  Utilisation by role, role group, project, and person, viewed by month or by week.

• Pending work per person

  What is still open against each person, exportable for a one to one.

• Capacity against allocation

  In the Cloud edition, a dedicated resource tracking view compares available capacity with what has been committed.

06Money

• Profitability per project

  Revenue against cost per project, filtered by client, manager, project type, status, and date.

• Hours spent, four ways

  The same time data as a burndown, a pie, a grid, and a line, because different people read different shapes.

• Timesheet reporting

  Approved hours by person and project, with a chart view alongside the table.

• Budget and cost on the dashboard

  Budget against actual, cost by resource, and a red amber green cost view, all from logged hours and your rates.

07Export

• CSV from the table reports

  Due date changes, resource utilisation, team utilisation, pending tasks, and profitability all export.

• A spreadsheet file, not just CSV

  Resource utilisation writes a real spreadsheet file for people who want formatting to survive.

• A sprint report as a PDF

  The completed sprint report renders to PDF, which is what usually ends up in a board pack.

• Save a chart as an image

  Any chart can be taken out as a picture or a PDF, straight from the chart itself.

• Scheduled email reports

  Weekly usage, a task status digest, daily due reminders, a daily update report, management reports, and team utilisation, on a schedule you set.

08Access

• A permission for each report

  Every report has its own view permission, so the profitability report is not open to the whole company.

• One project or all of them

  Reports run for a single project or across the portfolio, which is how PMO and leadership actually ask the question.