bpummni°
Roadmap

A clear, focused delivery plan, revised as required.

Direction is set annually and reviewed continuously, which is why it has been set eight times. This page is updated whenever a date passes, usually by removing it.

Delivery status

Where we are, measured honestly for once.

Days past the first announced ship date
—
Original target: Q3 2020.
Years of slip, cumulative
—
Across eight published dates and one unpublished one.
Current projected general availability
—
Recedes at roughly 1.4 days per elapsed day.
History

Everything that has happened, and when it was going to.

  • Q2 2019Announced"United. Connected. All-in-one." The tagline shipped first and remains our most stable release.Delivered
  • Q4 2019Discovery completeEleven clinics interviewed. Findings summarised in a deck. The deck is the requirements document.Delivered
  • Q3 2020First general availability dateMissed. The platform decision was reopened after a conference.Missed
  • Q1 2021Rebuild begins on the strategic frameworkChosen for its long-term community support and strong ecosystem.Complete
  • Q4 2021Second general availability dateMissed. The strategic framework was deprecated by its maintainers in October.Missed
  • Q2 2022"Ummni has landed"Landed in beta, at one clinic, for eleven days. The clinic has asked not to be named, and then not to be contacted.Partially
  • Q4 2022Migration from event-bus-alpha to event-bus-betaTwo quarters allocated. Still in progress. Both buses now described as strategic.In progress
  • Q2 2023Third general availability dateMissed. Reporting was re-scoped as a micro-frontend, to reduce complexity.Missed
  • Q3 2023Complexity reduction working group establishedNow has three subgroups and a steering committee.Ongoing
  • 2024Brand refreshSame product. Rounder logo. New gradient. Delivered on time and under budget, and cited in every subsequent business case.Delivered
  • Q1 2025Fourth general availability dateQuietly removed from the website rather than missed. Technically our best result to date.Withdrawn
  • Q3 2025Single sign-on across the four productsDescoped to protect the release date. The release date then moved.Descoped
  • 2026Dates replaced with "soon"An estimate that has not slipped once, and structurally cannot.On track
  • Q3 2027Current target: general availabilityConfidence: low. Dependent on merging the two monoliths, an initiative currently blocked on naming.Under review
  • TBCRestore from backupBackups have run nightly since 2021. Restoring one remains an unscheduled item.Unscheduled
  • TBCDecommission the legacy claim gatewayDeprecated in 2021. Load-bearing since 2021.Unscheduled
How we plan

Our estimation process, described plainly.

Step 01

Set a date

A date is chosen at the annual planning session, based on when it would be convenient for the date to be.

Step 02

Protect the date

As the date approaches, scope is removed to protect it. The removed scope becomes the next release, which needs its own date.

Step 03

Move the date

The date moves. The reason is recorded as an architectural decision, which is filed, which counts as progress.

Next

Ready to talk about what this will cost?

So are we. A pricing decision is expected in the quarter after the one we are currently in.

See pricing