Reports that are always up to date.

Burn-up, burndown and cycle time replay what your work items already record. The dashboard, every milestone and every estimate add up on their own whenever something changes.

The numbers your work already holds.

Is done catching up with scope?

Burn-up stacks done, in progress and open work day by day; burndown reduces it to what remains. Count items or points, zoom into a stretch, export the chart as PNG.

How long work really takes

Cycle Time plots one dot per finished item, measured from start or from creation. A rolling median, a spread band and the 50th and 85th percentiles give you a figure to quote.

A burn-up for every milestone

Each sprint or release shows done against total, in items and in points, and draws its own burn-up and burndown. The scope line rises as items join.

The project at a glance

The dashboard cuts the work by type, priority and status, sums points by status and sets tracked time against the estimate. The time bar turns amber once you overrun.

Who did what this week

The activity feed covers the last seven days, by day or by person, as a list or a heatmap of events. Agents appear like people, marked with a badge.

Effort that rolls up the tree

Estimates and logged time add up from tasks to epics. Effort counts every entry, wall-clock counts parallel work once, and a heatmap shows when the hours went in.

Ask for the numbers behind the charts.

The charts are drawn for people; your agent reads the items underneath. It counts and sums any selection, groups it by week or month, reads milestone progress and reports logged time per person.

Say to your agentManager: How many items did we finish per week this quarter?

The agent groups finished items by week of completion, with points and logged time beside each count. That is the throughput behind a burn-up.

Say to your agentManager: Sum the estimates and logged time per epic, and tell me where we are over.

The agent groups the items by their top-level epic, sums estimate and time spent for each and names the epics where the time has passed the estimate.

Say to your agentManager: How much time went into PRJ-4 this week, per person?

The agent reads the time entries on PRJ-4 and everything beneath it and reports each person's hours, with parallel work counted once.

Say to your agentManager: Where does Sprint 29 stand?

The agent reads the milestone: its state and dates, done against total in items and points, and each item with the day it joined the sprint.

Every number in detail.

What each chart measures, and where the figures come from.

Charts

  • Burn-up and burndown, by items or points
  • Last 7, 30 or 90 days, or all time
  • Cycle time or lead time per finished item
  • 50th and 85th percentiles over the whole range
  • Rolling median with a choice of spread band
  • Zoom into a stretch, export as PNG

Milestones

  • Done against total, in items and points
  • Burn-up and burndown per milestone
  • History rebuilt from every join, completion and removal
  • Active, upcoming, overdue, reached or closed, always current
  • Due-soon and overdue notices to whoever holds open work

Dashboard

  • Items by type, priority and status
  • Points by status, with the percentage done
  • Tracked time against the estimate, flagged on overrun
  • Activity of the last seven days, by day or person
  • Heatmap of events per team member
  • Updates live as items and time bookings change

Time and exports

  • Estimate and time spent roll up the tree
  • Effort and wall-clock totals side by side
  • Time activity heatmap for you and per member
  • CSV export of work items, custom fields included
  • Every time entry of a project, for exports and syncs

See it at work.

Guides that put this feature to work in a real project.

Let the work report on itself.

Every chart replays what your items already record: when they were created, started and finished, and the time booked on them. Nobody fills in a spreadsheet. Your agent counts from the same data.

Get early access