Sprint Lock
Once a sprint starts, its lane locks.
Plan freely, press Start sprint, and the sprint lane is fenced. New work, urgent client asks included, waits in To Do for the next sprint. Every refusal explains itself, so nothing silently bounces.
14-day free trial with every feature. No card.
How it works
- 1
Plan
Drag cards into the next sprint, or map them to sprints further ahead.
- 2
Lock
Start the sprint. The lane is fenced with solid markings and drops are refused before you let go.
- 3
Ship
Cards move through In Progress and In Review. New asks queue in To Do.
- 4
Report
End the sprint: finished work, carried cards and every scope change, in one report.
What you get
- Plan several sprints ahead and map cards to each
- Scope override with a reason, logged in the sprint report
- Send back and reopen need a note
- Blockers stop a card starting until they are done
A transition matrix, not a convention
While a sprint is locked, the server decides every move: creating in To Do always works, creating into the sprint, In Review or Done is refused with a clear reason. The board shows the refusal before you drop.
Scope changes leave a trail
If your workspace allows it, an admin can override with a reason. The override is logged and shows up in the sprint report as scope added after start.
The sprint road
A running sprint is drawn as a road with a “today” marker and the done fill, so you can see at a glance whether you’re ahead or behind.
Sprint Lock: questions
Is Sprint Lock the same as Scrum?
No. Sprint Lock keeps the Kanban flow of columns but fences the running sprint. Scrum in Laneway has a backlog, planning and burndown. You choose per project.
What happens to urgent work during a locked sprint?
It goes into To Do and waits for the next sprint, or an admin overrides the lock with a reason that is logged.
Start your first sprint today. Lock it tomorrow.
14 days free · no card · cancel any timeSee pricing