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.
Intake to sprint commitment
Turn incoming work into a prioritised, reviewed iteration scope.
3 stages · 0 approvals
Roles and responsibilities
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Capture issue
Issues land in the system through three paths: (a) UI creation by Developers, QA, or the Project Lead; (b) Reporter creation by internal users outside the squad (constrained to Bug / Task / Improvement / Incident types); (c) the issue-creation-from-webhook workflow firing on inbound email, Slack /issue slash command, support-helpdesk Ticket promote, or it-itsm Incident promote. The webhook code resolves target Project + Component from routing rules (subject prefix, channel, sender domain), creates the Issues row with Status: the Workflow's InitialStatus, Priority: Medium defaulted, and emails the Reporter with the IssueKey acknowledgement. Bug-type Issues trigger bug-priority-recompute immediately.
Plan iteration
On the Backlog's GroomingCadence, the Product Owner opens the Project Backlog view, ranks Issues via BacklogRank, sets Estimate on IssueTypes.RequiresEstimate = true rows, assigns ParentEpic and tentative FixVersion. For Sprint planning, the Scrum Master opens a Future Sprints row (with Goal, StartDate, EndDate, Board, CapacityPoints defaulted from TeamVelocity.TrailingThreeAverage), pulls top-ranked Backlog Issues into the Sprint by setting Issues.Sprint to the Future Sprint, until the committed estimate matches capacity.
Start sprint
Scrum Master flips the Sprint Status: Future → Active. The sprint-start-snapshot workflow fires via the configured record event, walks every Issues row attached to the Sprint, bulk-inserts one SprintCommitments row per Issue freezing the CommittedEstimate, CommittedStatus, and CommittedAssignee snapshot at sprint-start, stamps Sprints.StartedAt, and emails the kickoff digest with committed scope to the Scrum Master + Project Lead. The Sprint board becomes the squad's daily surface.
Approvals and controls
0 approvals required in this process
- Keep componentVersion and workflow references in the same project.
- An active start snapshot cannot be edited retroactively.
- Reporter access does not reveal internal project work.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Capture issue | IssuesIssueTypes | Record scoped work with source identity |
| 2 Plan iteration | BacklogsIssuesSprints | Set priority and a consistent estimate unit |
| 3 Start sprint | SprintsSprintCommitments | Freeze one starting commitment per issue |
Process reports
All reportsBacklog 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.
Cycle 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.
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.
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.
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
› intake to sprint commitment · capture issue on Issues, IssueTypes
✓ Issues land in the system through three paths: (a) UI creation by Developers, QA, or the Project Lead; (b) Reporter creation by internal users outside the squad (constrained to Bug / Task / Improvement / Incident types); (c) the issue-creation-from-webhook workflow firing on inbound email, Slack /issue slash command, support-helpdesk Ticket promote, or it-itsm Incident promote.
› intake to sprint commitment · plan iteration on Backlogs, Issues, Sprints
✓ On the Backlog's GroomingCadence, the Product Owner opens the Project Backlog view, ranks Issues via BacklogRank, sets Estimate on IssueTypes.RequiresEstimate = true rows, assigns ParentEpic and tentative FixVersion.
› intake to sprint commitment · start sprint on Sprints, SprintCommitments
✓ Scrum Master flips the Sprint Status: Future → Active.
Other processes
3 moreWork to verified outcome
Apply the same workflow and quality checks to every delivery transition.
3 stages · 1 approval
Completed work to release cut
Review eligible issue scope before recording the release version.
3 stages · 1 approval
Sprint close to next plan
Preserve closed outcomes before rolling work into the next iteration.
3 stages · 0 approvals