Modules

A sprint groups work by when. A module groups it by what part of the product.

“Checkout”, “Onboarding”, “Mobile app”, “Billing” — the areas your team already names in conversation. A task can sit in a sprint and a module at the same time, because those are two different questions.

What a module carries

Field	What it is for
Name	The area — “Checkout”
Description	What is in scope, and what is not
Lead	One person accountable for it
Color	So it is recognizable on a board grouped by module
Status	Where the module itself stands, not its tasks
Start date	When work on it begins
Target date	When it should be done

Note that a module has its own status and dates, separate from the tasks in it. A module can be In progress while most of its tasks are still in Backlog — that is useful information, not a contradiction.

Turn it on

Modules are a per-project feature. In project settings, enable Modules and the tab appears; leave it off and the property never clutters a task.

This is deliberate. A three-person project does not need workstreams, and a fifty-person project cannot function without them.

Use them

Once a module exists, set it on a task like any other property — hover a card and press M, or use the task panel.

From there:

• Group the board by module to see each area as a column. See Board display.
• Filter by module to work on one area at a time.
• Sub-group by module to get one swimlane per area.
• Open the module itself for its own list of tasks and its progress.

Module or sprint or label?

They overlap enough to confuse, so:

You want to say	Use
“This ships in the next two weeks”	Sprint
“This is part of Checkout”	Module
“This is a bug”	Type
“This came from a customer”	Label
“This belongs to a different team’s board”	Mirror
“This is a company outcome spanning projects”	Initiative

The test: if the grouping would still make sense in a year, it is probably a module. If it expires, it is probably a sprint or a label.

Modules vs initiatives

They sound similar and sit at opposite ends.

• A module is inside one project. Smaller than a project.
• An initiative is above several projects. Bigger than a project.

If your “module” keeps needing tasks from another project, you wanted an initiative. See Run an initiative.

Archiving

Finished with an area? Archive the module. Its tasks keep their history and stay exactly where they are — archiving the container never touches the contents.

Next

• Plan a sprint — the when axis.
• Board display and swimlanes — group by module.
• Dashboards — a widget that breaks work down by module.