PROJECT MANAGEMENT
Track scope-creep trends across sprints in a warehouse
After each sprint closes, calculates the committed-vs-added work for the Asana sprint and appends the metrics to BigQuery so creep trends can be charted across sprints over time.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled run after sprint end date
- ActionFetch Asana sprint tasks with timestamps and pointsAsana
- LogicCompute committed vs added metrics and completion rate
- LogicAssemble normalized per-sprint metrics row
- OutputAppend sprint creep metrics to BigQueryBigQuery
What it does
This workflow builds a longitudinal record of scope creep. At the close of each sprint it reads the Asana sprint section, measures committed work against work added after the sprint kickoff, and writes one summary row per sprint to BigQuery. Over many sprints this becomes the dataset behind a creep-trend chart, letting leadership see whether discipline is improving or eroding.
When to use it
Use it when a single sprint's number isn't enough — you want to know if scope creep is a one-off or a chronic pattern, and you want the data in a warehouse for dashboards.
How it works
- 1A scheduled trigger fires after the sprint's end date.
- 2The flow pulls all tasks from the Asana sprint project with their creation and completion timestamps.
- 3It computes committed task count and points, added-after-kickoff count and points, and the completion rate.
- 4It assembles a single normalized metrics row keyed by sprint name and end date.
- 5It appends that row to a BigQuery table for trend analysis and dashboards.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 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.