# Planning: estimates, cycles and milestones

Andon plans in two ways. A **cycle** is a team's planning period, one to a few weeks long: you put cards in it, watch
the burn line and carry over what didn't get done. A **milestone** is a dated checkpoint in a project, such as
"Private beta, Dec 1", and its progress comes from the cards on it. **Estimates** size the cards so both can add up
work instead of counting cards.

Putting a card in a cycle or on a milestone doesn't move it. The cycle view and the roadmap show the same board,
filtered.

## Set up estimates and cycles for a team

Planning belongs to a top-level team. Its sub-teams share its scale and its cycles.

1. Open the team's page: pick the team in the sidebar, then **Team page** in the header. Its **Cycles** section has an
   **Edit** link. Or search Settings for **Cycles on their own** and pick the team.
2. Under **Estimates**, pick the scale: points, t-shirt sizes or hours.
3. To have Andon make cycles for you, turn on **Cycles on their own**, then set **Length** (1 to 4 weeks) and
   **Starts on** (a weekday).

With **Cycles on their own** on, Andon makes the cycle that holds today and the next two, and keeps two ahead from
then on. Each cycle closes the day after it ends, and the next one starts. It is off by default.

To add a cycle by hand instead, click **New cycle** in the team page's **Cycles** section, give it a name and its
**Starts** and **Ends** dates, and click **Add cycle**. A cycle is at most 12 weeks long, and a team's cycles never
overlap. A cycle added by hand also starts and closes on its dates.

### Estimate scales

| Scale | Sizes |
| --- | --- |
| Points (the default) | 1, 2, 3, 5, 8 |
| T-shirt sizes | XS, S, M, L, XL (added up as 1 to 5) |
| Hours | 1h, 2h, 4h, 8h, 16h, 24h, 40h |

## Plan a card into a cycle

1. Open the card.
2. In its details, set **Cycle** to one of the team's open cycles.
3. Set **Estimate**, just below it.

The estimate shows small on the card face ("3", "M", "4h") and in the List layout. To plan many cards at once, pick
them and use **Set → Cycle** and **Set → Estimate** on the selection bar ([bulk edit](https://andon-docs.pages.dev/guide/templates-and-bulk-edit.md#change-many-cards-at-once)).
A card that moves to another team tree leaves its cycle. Agents don't estimate cards on their own.

## Follow a cycle

Open the cycle view from the team page, from a card's **Open the cycle** link, or from Stats. The board below is
filtered to the cycle, and a card you add there joins it.

The header shows:

- **Scope**: the cycle's cards, and the sum of their estimates
- **Done**, **In progress** and **Not started**
- the days left
- the **burn line**: what is left each day against a straight line to zero

A card counts as done on the day it last moved into Done. The **Previous cycle** and **Next cycle** arrows step
between the team's cycles, and the **×** at the top right leaves the cycle view.

Totals add up estimates when the cards carry them, and count cards when none do.

## Close a cycle

Andon closes a cycle the day after it ends, and carries its unfinished cards (not in Done, not archived) to the next
cycle. If there is no next cycle, it makes one of the same length.

To close one early or late yourself:

1. Open the cycle view and click **Close…**.
2. Choose where the unfinished cards go:
   - **Carry over** moves them to the next cycle.
   - **Back to Backlog** returns them to the Backlog. Cards in Working or Review stay where they are and only leave the
     cycle.

Only the team's own members and admins can close a cycle by hand. Each carried card's **Cycle** field then says
"Carried over from Cycle *n*", and the closed cycle keeps the list and its numbers.

## Milestones

A milestone belongs to one project. It has a **Name** (once per project), an optional **Target date**, a **State**
(open, done or canceled) and an optional **Note**.

### Add a milestone and put cards on it

1. Open **Roadmap** in the sidebar, under **Progress**.
2. Click **New milestone**, pick the **Project**, and fill in the name and date.
3. Open a card in that project. In its details, set **Milestone** to the new one. You can also make a milestone from
   that field.

Any member who sees the project's team can add and edit milestones. Deleting one is for its maker, the project's lead,
owners and admins. A card that moves to another project leaves its milestone.

### How progress is counted

A milestone's progress comes from its cards' columns: **Done**, **In progress** (Working and Review) and **Not
started** (everything else). When the cards carry estimates, the bar follows the summed points.

## The roadmap

**Roadmap** lists every project's open milestones by month. Each row shows its project, team and date, a progress bar
and "3 of 8 done". An overdue date is amber.

- **View** narrows the roadmap to a saved view. A milestone stays when one of its cards matches the view, or when a
  matching card is in its project.
- **Show done and canceled** brings back the closed milestones.
- Click a row to open the milestone: its cards as a list, with **Edit milestone** and **Delete milestone** (Undo in
  the toast).

On a phone the roadmap is the same list, opened from the menu.

## The timeline layout

The board's third layout (**Board**, **List**, **Timeline** in the filter bar) draws projects as rows and days from
left to right, with a line for today.

- **Milestones** are diamonds at their dates. Drag one sideways to move its date; the toast offers Undo. With a
  diamond focused, ← and → move it a day, and Shift with an arrow a week. Click it (or press Enter) to open its cards.
- **Cards with a due date** are bars from when the card was made to when it's due. Done cards are struck through and
  overdue ones amber. Click a bar to open the card. Cards with no due date aren't drawn; the toolbar counts them.
- **Zoom** is week, month or quarter, remembered on this device. **Today** scrolls back to now.
- **Rows**: with no filter typed, every project in the sidebar's team or project that has a milestone or a dated card.
  With a filter, the projects of the cards it keeps.

The timeline doesn't draw cycles.

## Milestones from Linear and Jira

- **Import.** A Linear issue in a project milestone lands on the matching milestone in its board project. A Jira issue's fix version becomes a milestone in the card's project. If the issue has several, Andon uses the
  first unreleased one, or the first one if all are released. A
  released version reads as done, an archived one as canceled. The tracker stays the source: the milestone's name,
  date and state follow it.
- **Write-back** is off unless you turn it on: in **Settings → Connections**, open Linear or Jira, and under
  **Write-back** turn on **Set the primary issue's project milestone…** (Linear) or **Set the primary issue's fix
  version…** (Jira). Then changing a linked card's milestone sets the issue's project milestone or fix version. Only milestones imported from
  that tracker are sent; one made on the board never touches the issue.

## Where else plans show

- **Filters**: `cycle:current`, `cycle:next`, `cycle:"Cycle 12"`, `cycle:none`, and `estimate:3`, `estimate:>=5`,
  `estimate:none`. The List layout groups by cycle. See [Views](https://andon-docs.pages.dev/guide/views.md).
- **The team page**: the current cycle (done of scope, days left, what was carried in), what the last three closed
  cycles finished, the next cycles and the recently closed ones.
- **[Stats](https://andon-docs.pages.dev/guide/stats.md)**: a row for each team's current cycle and its last three closed ones.
- **The Dashboard**: the current cycle's name and days left in its status line. See
  [Dashboard and phone](https://andon-docs.pages.dev/guide/dashboard-and-phone.md).
- **Autopilot** takes each card's estimate into account when it places cards.
