Scrum without the overhead.

Why teams switch

• No workflow schemes

  An item has a status and a phase. You define the phases once per project, in the order they are worked, and that is the whole configuration.

• No admin console

  Eight capability bundles, granted by role and readable on one screen. A team role covers that team’s work, and a single per-person override is the only exception.

• Nothing to set up before the first sprint

  Sprints start on a Monday by default. Create a team, put it on a project, write the Sprint Goal, and plan.

One sprint, start to finish

1. 1

   Plan

   Drag groomed items into the sprint. Capacity, blockers and oversize warnings show as you go; only a genuine invariant stops you.

   

2. 2

   Daily Scrum

   The board follows the active sprint. Moving a card is the status change, and the session records it.

   

3. 3

   Review

   The Increment is a query over what is Done, not a list somebody maintains. Feedback becomes a backlog item in one click.

   

4. 4

   Retrospective

   Four columns, everyone writing at once, no shared row to fight over. An action item becomes a backlog item in one click.

   

The sprint closes with a record of what moved where. Nobody typed it.

Real Scrum, in its own words

Not a kanban board with sprints bolted on. The product uses the Scrum Guide's vocabulary and means it.

Product Goal

on the project

Sprint Goal

required before a sprint can start

Definition of Done

a gate, not a checkbox

Increment

what is Done, as a query

Scrum Events

planning, Daily Scrum, review, retrospective

Pricing

An organization over a cap keeps everything it has and is refused only growth.

Compare plans