Workstreams
What it is
Section titled “What it is”Workstreams break a program into parallel tracks of delivery. Each workstream groups related requirements, tasks, and sprints under a named stream with a short code, RAG status, and sprint cadence.
Why it matters
Section titled “Why it matters”Large engagements need structure beyond a flat backlog. Workstreams let teams organize by functional area (e.g., “Catalog,” “Checkout,” “Order Management”) and track health independently, so blockers in one stream do not obscure progress in another.
Key concepts
Section titled “Key concepts”- Short code: A brief identifier (e.g.,
CAT,CHK) displayed on cards and filters across the platform - RAG status:
on_track,at_risk,blocked— a traffic-light health indicator you can cycle through - Sprint cadence: How many sprints are planned for the workstream
- Requirement count: Aggregated from requirements linked to the workstream
- Task progress: Computed from task statuses within the workstream
How to use it
Section titled “How to use it”- Navigate to [Program] > Workstreams.
- View the card grid showing each workstream with its short code, RAG status, and requirement/task counts.
- Click a workstream card to open the detail page with linked requirements, tasks, and sprint information.
- Toggle the RAG status directly from the workstream card by clicking the status badge.
- Create new workstreams from the workstreams page header.
Data model
Section titled “Data model”This feature uses the following tables:
workstreams— Name, shortCode, status, sprintCadence, linked to a programrequirements— Each requirement has an optionalworkstreamIdtasks— Tasks can be scoped to a workstream