Backlog Health
Per Project: Backlog count by IssueType, by Priority, and by ParentEpic; share of Backlog rows missing required Estimates (per IssueTypes.RequiresEstimate); share missing FixVersion. The Product Owner's grooming worksheet.
Completed work to release cut
Review eligible issue scope before recording the release version.
3 stages · 1 approval
Roles and responsibilities
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Reconcile code evidence
When a git PR linked to an Issue is merged into the protected branch, the auto-link-to-pr webhook updates the PullRequestLinks row (Status: Open → Merged, MergedAt stamped); if Projects.AutoTransitionOnMerge is on, the Issue auto-transitions InReview → Done (subject to any QA gate in WorkflowTransitions). On InReview → Done, status-transition-routing flips Issues.ResolvedAt, Issues.Resolution: Fixed, recomputes current sprint progress without incrementing an unversioned historical counter, and unblocks any IssueLinks of type IsBlockedBy pointing at this Issue. QA verification of bug-type Issues holds at InReview until QA approves the gated transition.
Approval required
Review release scope
As Issues complete with FixVersion = , the Project Lead readies the Version. On Versions.Status: Unreleased → Released (typically after a release-board sign-off and CI green), release-cut-from-version fires, validates every Issue in the proposed version is completed or explicitly excluded before the reviewed release scope is frozen; for those eligible Issues, stamps ReleasedAt, applies an IssueLabels row released- , updates parent EpicProgress rollups, and emails the release-notes digest (Issues grouped by Type — Story / Bug / Improvement) to the Stakeholder distribution list. A Released Version is not modified — additional fixes ship in the next Version.
Share progress
Every role sees a scope-appropriate dashboard: Developer sees My Open Issues + the Active Sprint Board; Scrum Master sees Sprint Burndown + Velocity Trend + Stalled Issues + WIP Warnings; Project Lead sees Backlog Health + Release Progress + Epic Progress; QA sees Bugs Awaiting Verification + Bug SLA Attainment; Stakeholder sees Epic Roadmap + Release Forecast for assigned Projects; Reporter sees My Reported Issues; Admin sees Workflow + IssueType health. The Sprint Velocity Report and Sprint Burndown drive the ceremonies; the Cycle Time / Lead Time and Throughput by Type reports drive process improvement; the Release Forecast and Epic Roadmap drive stakeholder communications.
Approvals and controls
1 approval required in this process
-
Review release scope
Project Lead / Product Owner signs · share progress waits
Versions, Issues - Exclude unfinished scope through an authorized change.
- Retain prior release records and source revisions.
- Deployment confirmation remains a separate external outcome.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Reconcile code evidence | PullRequestLinksIntegrationEvents | Verify branch, checks and source event identity |
| 2 Review release scope | VersionsIssues | Freeze eligible completed issue scope and source revision |
| 3 Share progress | EpicProgressMilestones | Publish permitted dated delivery context |
Process reports
All reportsCycle Time and Lead Time
Per Project, per IssueType: distribution of elapsed time Created → ResolvedAt (lead time) and StartedAt → ResolvedAt (cycle time), with p50 / p90 markers. Diagnoses queue length and review-stage delays by status.
Throughput by Type
Per Project, per week: count of Issues moved to Status: Done bucketed by IssueType (Story / Bug / Task / Improvement). Pairs with created-count to surface bug pile-up vs. story delivery rate.
Bug SLA Attainment
Per Project, per Severity: Bugs filed in the trailing 30 days, count resolved within the per-Severity SLA target (Sev1: 24h, Sev2: 3 business days, Sev3: 10 business days, Sev4: best-effort), and on-time-rate percent. The QA + on-call leadership report.
Release Forecast
Per Version: total Estimate vs. CompletedEstimate, projected ReleaseDate using the TeamVelocity trailing-3 average against remaining scope, and the per-Epic contribution. Surfaces at-risk releases ahead of cut date.
Epic Roadmap
Per Project, per Epic: TotalIssues / DoneIssues / PercentComplete, ForecastReleaseDate, TargetVersion, and Milestones touched. The Stakeholder roadmap view.
Sprint Velocity Report
Per Project, per Sprint: CommittedPoints vs. CompletedPoints vs. Carryover, with the trailing-3-sprint average overlay. Drills into the per-Issue contribution list for any selected Sprint. The Scrum Master's ceremony report — read at sprint review and retrospective.
Sprint Burndown
Daily burndown chart per Sprint: RemainingEstimate vs. IdealRemaining, with ScopeAddedPoints flagged as a step-up and ScopeRemovedPoints as a step-down. Surfaces mid-sprint scope churn alongside delivery pace.
Run by an agent
Agent support
PM for IT Projects owns the backlog, issue workflow, sprint records and reviewed release cut. Git and CI provide authenticated evidence; deployment, customer billing and employment records remain in their source systems. Proto can explain a gate but cannot manufacture QA approval or a successful deployment.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› completed work to release cut · reconcile code evidence on PullRequestLinks, IntegrationEvents
✓ When a git PR linked to an Issue is merged into the protected branch, the auto-link-to-pr webhook updates the PullRequestLinks row (Status: Open → Merged, MergedAt stamped); if Projects.AutoTransitionOnMerge is on, the Issue auto-transitions InReview → Done (subject to any QA gate in WorkflowTransitions).
› completed work to release cut · review release scope on Versions, Issues
⏸ approval · waiting for the project lead / product owner
# 1 more stage after approval: share progress
Other processes
3 moreIntake to sprint commitment
Turn incoming work into a prioritised, reviewed iteration scope.
3 stages · 0 approvals
Work to verified outcome
Apply the same workflow and quality checks to every delivery transition.
3 stages · 1 approval
Sprint close to next plan
Preserve closed outcomes before rolling work into the next iteration.
3 stages · 0 approvals