Pipeline Tracking
As your team works through the stages — PM specifying requirements, designers creating mockups, engineers planning, developers building — you need a way to see where everything stands. Pipeline tracking gives you real-time visibility into delivery readiness.
The Pipeline View
Requirements flow through five stages, and the pipeline tracks their progress across each:
| Stage | What It Answers |
|---|---|
| PRD | Are requirements defined and confirmed? |
| Design | Are UI/UX designs complete? |
| Engineering | Has development been planned? |
| Dev | Has implementation been completed? |
| QA | Has testing been completed? |
For each stage, you can see:
- In-Scope — total requirements relevant to this stage
- Available — requirements ready to be worked on
- Completed — requirements that have passed this stage
- Progress % — percentage complete
How Each Stage Is Calculated
| Stage | In-Scope | Available | Completed |
|---|---|---|---|
| PRD | All requirements | Draft requirements | Confirmed or out of scope |
| Design | Confirmed (excluding "not needed" for design) | Design status "not started" | Design status "completed" |
| Engineering | All confirmed | Design done, dev status "not started" | Dev status "planned" or later |
| Dev | All confirmed | Dev status "planned" | Dev status "developed" or "tested" |
| QA | All confirmed | Dev status "developed" | Dev status "tested" |
Sankey Visualization
The pipeline includes a Sankey diagram that visualizes how requirements flow from one stage to the next. At a glance, you can:
- See the distribution of requirements across PRD, Design, and Development statuses
- Spot bottlenecks where work is piling up
- Identify stages that need attention
Stage Completion at a Glance
In addition to the granular pipeline metrics, each project tracks high-level stage completion:
| Stage | Complete When |
|---|---|
| PRD | Problem, users, solution, and success criteria are documented |
| Product Spec | All requirements are confirmed or out of scope |
| UI/UX | All designs are "completed" or "not needed" |
| Engineering | All requirements are "planned" or later |
| Development | All requirements have been developed |
| QA | All requirements have been tested |
This dual tracking gives stakeholders a quick top-down overview while the development team gets a detailed bottom-up view.
These metrics — combined with Documents, Artefacts & Bugs and Workstreams & Requirements — give your team complete visibility into the project.