Skip to content
sprintrr logo
sprintrr
Sign in

Core Concepts

The four building blocks — workspaces, projects, milestones, and tasks — and how they relate.

Everything in sprintrr is built from four concepts. Understanding how they relate makes the rest of the product predictable.

Workspaces

Every project lives in exactly one of two kinds of workspace:

  • Personal — projects you own privately. These are the projects where team_id is unset.
  • Team — a shared workspace. Projects belong to the team; members can see and work on them according to their role. Teams have pooled AI credits.

You switch workspace from the sidebar. The same account can have a personal workspace and belong to one or more teams.

Projects

A project is the top-level container for a body of work. It carries a name and description, an optional tech stack and success metrics, sprint counts, and a flag indicating whether it was AI-generated. A project holds milestones and tasks.

Projects can be grouped into folders (up to two levels deep) for sidebar organization, and can be archived as a soft-state alternative to delete — archived projects hide from the main list but stay restorable. See Projects for the full field reference.

Milestones

A milestone is a checkpoint within a project (e.g. "Beta launch"). Tasks can be assigned to a milestone via their milestone_id. A milestone's progress percentage is calculated automatically from the status of its associated tasks — you don't set it by hand. Milestone status is one of Not Started, In Progress, Completed, or Blocked.

See Milestones.

Tasks

A task is the unit of execution. Key attributes:

  • Status — Not Started → In Progress → Completed (or Blocked).
  • Priority — Low, Medium, High.
  • Category — Development, Design, Testing, and more.
  • Estimates & actuals — estimated hours vs. actual hours.
  • Time tracking — automatic: a timer accrues while a task is In Progress.
  • Assignment — one or more team members.
  • Due date and optional milestone grouping.

See Tasks for the complete model, including how time tracking accrues.

How they relate

Workspace (Personal | Team)
└── Project
    ├── Milestone ──(progress % computed from its tasks)
    └── Task ──(optionally grouped under one Milestone)
  • A task always belongs to a project; it optionally belongs to one milestone.
  • Milestone progress is derived, never manually entered.
  • Moving a task's status drives time tracking, milestone progress, and analytics — all automatically.
  • Every create/update/delete on these entities is recorded in the Activity feed, attributed to who (or what) made the change.
PreviousQuickstartNextProjects