Working with Workstreams
Introduction
Workstreams group a plan's milestones, so that a plan with many milestones stays readable. This page describes what a workstream holds, how it shows on the Timeline and how it affects who can change what.
What a workstream is
A workstream is a named group of milestones. On the Timeline each workstream has its own lane, so you can see which milestones belong together and who is responsible for each area of the plan.
Workstreams suit several ways of organising work:
- Areas of work: Marketing, Development or Operations.
- Specific objectives: "Product launch" or "Customer onboarding".
- Sub-teams: one workstream for each team.
A plan can have as many workstreams as it needs. Too many make a plan hard to scan, and too few lose the benefit of grouping.
What a workstream holds
- Name: describe the workstream or goal.
- Owner: the person responsible for the workstream.
- Status: a small pie chart beside the name, showing how many of its milestones are in each status.
Creating a workstream
On the Timeline, select ADD A WORKSTREAM, then type a name.
Moving milestones between workstreams
On the Timeline, drag a milestone up or down into another lane. You can also move an entire workstream out into a plan of its own: expand it and select [MOVE TO PLAN].
Workstreams and permissions
A workstream's owner can change the milestones and actions in it, even if they have only View access to the plan as a whole. This lets you delegate an area of a plan without giving everyone full access. See Project Roles and Permissions.
Example
A product launch plan might use these workstreams:
- Development: technical milestones and feature work.
- Marketing: campaign planning, content and promotion.
- Sales: sales enablement, training and pipeline preparation.
- Operations: infrastructure, support processes and documentation.