For the team lead

How a Quantum Sprint runs

A Quantum Sprint is one planning interval in three sprints and a closing review. Teams that work agile will recognise the shape: a planning event at the start, sprints with a fixed weekly rhythm, and a review and retrospective at the end.

TeamSprint 0Sprints 1 and 2Total with the closing review
Experienced1 week6 weeks8 weeks
New to quantum2 weeks7 weeks10 weeks

Sprint 0 · Foundation

2 weeks, or 1 for an experienced team

The Quantum Capability Kickstart, for a team new to quantum (week 1). Five hands-on half-days take the team from single qubits to running and reading quantum algorithms in Qiskit and PennyLane, on working code. Every participant keeps the notebooks and the written handouts. An experienced team skips this week.

Planning (one week, two days of joint sessions): the tools (the platform, the workbook for each case, how to read a report); the backlog (which cases, and which questions each case should answer); tasks, and who takes which; team capacity over the coming weeks; data (what is ready, what needs a substitute).

Sprint 1 · Exploration

3 weeks

Every case in the backlog is run once on the platform and measured against its referee. At the end of the sprint the team knows where each case stands: which method was used, how close it came, and what it cost in circuit size.

Halftime

1 day

A full day with the team between the two sprints. Review: the results so far against the backlog, what to drop, what to add. Retrospective: how the work went, and what to change for the second sprint.

Sprint 2 · Deepening

3 weeks (4 for a team new to quantum)

The team works on what Sprint 1 showed. Depending on the case: other settings, another method, a run with realistic noise, a run on a real quantum device. For portfolio optimization and classification, each run names the settings worth changing, with what a published study measured about them.

Review and way forward

the final week, 2 to 3 days of joint sessions

With the team: review of all cases against the backlog, and a retrospective on the Quantum Sprint as a whole. Preparation: the written result for management. With management: the results, and a joint look at the options from here.

The weekly half-day

Through both sprints the team and qubit-lab.ch meet for a joint half-day every week:

  • backlog review: what was run, what it showed, what comes next
  • a short retrospective
  • coaching on the open questions of the week

A second session a week can be added.

What the team works with

The platform

Ready-to-use prototypes (the RQP platform) for portfolio optimization, index replication, credit and collateral allocation, feature selection, classification (credit scoring, fraud detection) and derivatives pricing. Data goes in as a workbook.

The referee

Every result is checked against a certified exact solver where one exists, and against the strongest tuned classical baseline where it does not, including the verdict “No advantage demonstrated”. Certified means that an exact method has proven the best possible answer, so the comparison is not a matter of opinion.

Simulator and device

Fast, low-cost simulators for everyday work; real quantum hardware where a use case calls for it. Device runs use IBM hardware through a free account each team member opens with IBM, under your firm’s own policies; it currently comes with ten minutes of processor time per person and month. Device runs are processed by IBM, outside Switzerland. We recommend sending a device run from the platform, with that account; the team can also run the exported code against IBM itself. For scale: the five device runs of our published noise study took 44 seconds of processor time together.

The code

Every run exports reproducible notebooks (Qiskit, PennyLane, Cirq, CUDA-Q, Classiq, OpenQASM).

Explore the RQP platform →See the published evidence →

What it takes and what it costs

Scope, team effort, the written result for management and the price are on the services page.