MatchanuMatchanu
Docs

Features

Scrum & Roadmap

Organize large projects into structured pieces of work. You don't have to use all of this — pick what's useful.

Not familiar with scrum?

No worries. This page explains everything from scratch. You can use just Epics without Sprints, or neither — it's all optional on top of Tasks.

The big picture

Here's how the pieces fit together — from biggest to smallest:

🗺️

Epic

A large chunk of work — like a major feature or milestone. Could take weeks or months.

📍

Phase

A stage within an epic — like Discovery, Development, Testing, Release.

🏃

Sprint

A short burst of work, usually 1–2 weeks, with a specific goal.

✅

Task

The individual unit of work that gets done. Tasks live on the kanban board.

Epics

An epic is a big goal. It's too large to fit on one task, so you break it into phases and tasks. Think of it like a chapter of your project.

Example epics for a SaaS product:

  • User Authentication & Onboarding
  • Billing & Subscriptions
  • Core Product Feature: Dashboard
  • Mobile Responsive Redesign
  1. 1Go to your project's Roadmap tab
  2. 2Click Add epic
  3. 3Give it a title and description
  4. 4Optionally pick a color to make it easy to spot on the roadmap

Phases

Phases break an epic into stages. They're like checkpoints — each one represents a distinct part of the work.

Typical phases for a feature epic:

DiscoveryDesignDevelopmentTestingRelease
  1. 1Open an epic
  2. 2Click Add phase
  3. 3Name the phase — keep it to one word if possible
  4. 4Tasks can then be assigned to a phase when you create them
💡Phases are optional. If your epic is simple enough, skip them and just use tasks directly.

Sprints

A sprint is a fixed period of time — usually 1 or 2 weeks — where your team focuses on a specific set of tasks. At the start you pick what goes in, at the end you review what was done.

Sprints help you stay focused. Instead of working on 30 things at once, you commit to finishing 5–10 things this week.

  1. 1Go to Sprints tab and click New sprint
  2. 2Set a name (e.g. Sprint 1), start date, and end date
  3. 3Write a sprint goal — one sentence on what you want to achieve
  4. 4Add tasks to the sprint from your backlog
  5. 5When the sprint ends, mark it completed and start the next one

Sprint status

planningBeing set up — tasks are being added
activeCurrently running — team is working on it
completedFinished — can be reviewed for learnings
💡Solo developer? Sprints still work great. Use a 1-week sprint to stay focused and avoid scope creep — commit to a list on Monday, ship by Friday.

Capacity & story points

When creating a sprint, you can set a capacity — the total story points your team can handle in that sprint. Then as you add tasks with story points, you'll see how full the sprint is.

This helps you avoid overcommitting. If your capacity is 20 points and you've already added 18 points worth of tasks, adding a 5-point task would put you over — a signal to push it to the next sprint.