# sprint

## Hero

### One real problem solved in

Best fit when the problem is real, bounded, and overdue — but still needs judgment to get right.

## When a problem keeps surviving the roadmap

Everyone knows the issue matters. Nobody has owned it. It sits between teams, outside the roadmap, or behind higher-visibility work.

Meanwhile it keeps creating drag: on delivery, on reliability, on adoption, or on the people who have to work around it.

## Bleu Sprint

A Sprint is a bounded engagement where Bleu takes ownership of one concrete problem and gets it to a usable outcome.

- Ownership from discovery through delivery
- Clear scope and decision points
- Working result, documentation, and handoff

## Typical Sprint work

- **Integrations**: Third-party APIs, protocol integrations, internal system handoffs, data flows
- **Legacy surfaces**: Areas nobody wants to touch, but everybody depends on
- **Migrations**: Frontend migrations, stack upgrades, architecture transitions
- **Reliability work**: Performance, stability, observability, production hardening
- **New product work**: A feature or surface the core team cannot absorb without slowing something more critical

## How it works

- **Understand the shape of the problem**: We get enough context to know what we're taking on.
- **Set the plan**: We define the path, the scope, and the decision points.
- **Execute with visibility**: We keep moving, surface the calls that matter, and avoid creating extra load.
- **Deliver in good shape**: The result works, is documented, and can be handed off cleanly.