What is ScrumPulse?
Understand the product, the teams it serves, and the boundary between the automation engine and dashboard.
ScrumPulse helps delivery teams inspect Jira or Taiga boards, identify recurring scrum problems, and review proposed corrective actions. It combines scheduled board analysis with a web control plane for setup, approvals, run history, metrics, and billing.
Who ScrumPulse is for#
ScrumPulse is designed for people responsible for healthy delivery workflows:
- Scrum masters monitoring blockers, stale work, and sprint readiness.
- Delivery and project leads who need a repeatable view of board health.
- Product managers preparing and reviewing backlog work.
- Organization members who review automation before it affects a live board.
- Engineers who operate the Python agent or self-host the dashboard and API.
What it helps with#
The automation engine can detect or summarize issues such as unassigned work, missing estimates, stale in-progress items, due-date risk, WIP limit violations, blockers, sprint trajectory, Definition-of-Done gaps, and refinement readiness. Optional cycles add risk scoring, replanning, pull-request linking, and sentiment analysis.
The dashboard provides these customer-facing areas:
| Area | What you can do |
|---|---|
| Overview | See connected projects, recent runs, proposed actions, and pending approvals. |
| Runs | Inspect run history, cycle summaries, action logs, and CSV or PDF exports. |
| Approvals | Approve or reject proposed actions before controlled execution. |
| Trends | Compare activity over time and across projects. |
| Import Backlog | Parse CSV or Markdown and create supported backlog items. |
| New Backlog | Build epics, stories, and tasks in a guided form. |
| Backlog Review | Approve, reject, or defer generated backlog proposals. |
| Settings | Connect a board and set the execution profile, action cap, and confirmation threshold. |
| Schedule | Save a schedule, board scope, and cycle selection. |
| Billing | View the current plan and open Stripe-hosted checkout or billing management. |
One product, two operating planes#
ScrumPulse has two related but separate planes:
- The execution engine in
execution/is a Python agent. It can run from GitHub Actions, cron, launchd, systemd, or a direct command. - The SaaS control plane in
dashboard/is a Next.js dashboard with a FastAPI API and database.
A board managed by the scheduled engine is not automatically connected in the SaaS dashboard. The scheduled bot reads its deployment secrets; the dashboard reads an organization-specific integration record. Configure each plane deliberately.
Safe by default#
New organizations use dry-run mode. Dry runs analyze the board and record proposed activity without applying board changes. Live writes also depend on plan eligibility, workspace mode, action-specific gates, confirmation rules, and execution caps.
Continue with Key concepts or complete the quick start.