How We Use Linear

Client Project (Linear Project = the client)
└── Milestone (a product/build for this client)
    └── Issue (one unit of work)
        ├── Sub-issue (smaller step)
        └── Sub-issue (smaller step)

Project = Client

Each client lives as a Linear Project. When you want “where are we for Client X”, you start at that Project. We focus on Active projects for day to day tracking.

Milestone = Product build inside the client

Milestones are not just dates or phases for us. A Milestone is a specific product or build we are delivering for the client. This could be an app, a workflow, an agent, a dashboard, a major feature set.

Every build starts from a Scoping process that is led by the AI Strategist (more details on How We Scope A New Build in Chapter 1).

Issue = Unit of work

An Issue is a single piece of work required to build or improve the milestone.

It could be a feature, a bug fix or an improvent.

When creating an issue, the AI Strategist should:

1. Pick a template (either the main template for a feature/improvement or the bug template if we need a fix)
2. Assign it to a dev (who will own and work on the issue)
3. Define the priority (see chapter 3 for what each priority means)
4. Add details on what the issue is meant to accomplish (description, desired output, inputs needed and acceptance criteria).

Once a dev gets assigned an issue, they should review it, ask for clarification to the strategist if the task isn’t clear and then estimate how many points the work will take.

Issues can’t be moved to “In Progress” until the issue has been estimated.

Issues can’t be moved to “In Review” or “Done” until they have been tested and reviewed by the AI Strategist and/or the client (more on this in chapter 4).

Sub-issue = Smaller unit under an issue

A Sub-issue is a slice of work that belongs under a parent issue. Use it when the parent issue is too big or has parallel steps that could be better tracked and described in separate, smaller issues.