The Honesty Box · Live from our own Jira board

Most of a project is defining the work. The build is a few focused hours.

The first question in every tender is the same: what are your typical timelines. Here is the live answer, straight from our board: what we build, how long it takes on the calendar, and how many of those hours are actual work.

HB
Delivery, by type of workLoading the latest numbers
Loading
Delivered Items
Kinds of work Types
SourceJiraOur own board

Median calendar days, by type Elapsed, not effort

Why we publish it

Every buyer in this market has been burned by a vendor timeline.

When we split a timeline into our build time and the time spent waiting on your inputs, you get a plan you can hold us to. A big share of any project is scoping, and that is the part you control.

Timeline theatre

  • One number in the tender, and no way to check it
  • Waiting time hidden inside build time
  • Delays explained after the fact

The Honesty Box

  • Live numbers from our own Jira board
  • Calendar time and logged hours, side by side
  • Scoping shown as the part you control

By type of work · From our own Jira board

Days of calendar. Hours of work.

For each kind of request: how many we have delivered, the median elapsed calendar time, and the median hours we actually logged. The gap between them is mostly waiting, not building.

Loading the latest numbers

Each bar is scaled to the longest in its own measure: calendar days against calendar days, logged hours against logged hours.

Elapsed timeComes from Jira status history.
Logged hoursCome from developer worklogs.
MediansSo one long project does not hide the typical one.

Your project

Tell us roughly what you need. We will tell you which of these it looks like.

And what we would need from you to land at the fast end.

You

Tomorrow, your case

Bring us a case that went wrong.

We will run it through Zenoo while you watch: the evidence, the decision, and the record your MLRO would want to defend.

30 minutes. Your data. No slides.