PROJECT MANAGEMENT
BigQuery velocity warehouse and forecast snapshot
Nightly job that loads each team's completed Linear story points into BigQuery, recomputes a rolling velocity model.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionFetch completed points per teamLinear
- ActionAppend rows to velocity history tableBigQuery
- LogicRecompute rolling weighted velocity per team
- OutputWrite forecast snapshot tableBigQuery
What it does
This workflow turns raw delivery history into a queryable velocity model. Every night it pulls each team's completed points from Linear, appends them to a BigQuery history table, and recomputes a rolling weighted velocity per team. It then writes a forecast snapshot table containing predicted next-sprint capacity and a confidence band, ready for BI dashboards and other workflows to consume.
When to use it
Use it when you want one trusted source of truth for velocity across many teams rather than ad hoc per-sprint math. It is the data backbone other forecaster workflows can read from instead of recomputing history every run.
How it works
- 1A nightly schedule triggers the refresh.
- 2The flow fetches each team's completed points from the most recent cycle in Linear.
- 3It appends the rows to the BigQuery velocity history table.
- 4A query recomputes a rolling weighted average and standard deviation per team.
- 5The results are written to a forecast snapshot table with predicted capacity and confidence range.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.