Intake to sprint commitment

Step by step

1. Capture issue Reporter

   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); © 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 initial status, Priority: Medium defaulted, and emails the Reporter with the issue key acknowledgement. Bug-type Issues trigger bug-priority-recompute immediately.

   • Record scoped work with source identity
   • Updates Issues, Issue types

2. Plan iteration Project Lead / Product Owner

   On the Backlog’s grooming cadence, the Product Owner opens the Project Backlog view, ranks Issues via backlog rank, sets Estimate on issue type requires estimate = true rows, assigns parent epic and tentative fix version. For Sprint planning, the Scrum Master opens a Future Sprints row (with Goal, start date, end date, Board, capacity points defaulted from team velocity trailing three average), pulls top-ranked Backlog Issues into the Sprint by setting issue sprint to the Future Sprint, until the committed estimate matches capacity.

   • Set priority and a consistent estimate unit
   • Updates Backlogs, Issues, Sprints

3. Start sprint Scrum Master / Iteration Manager

   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 sprint commitments row per Issue freezing the committed estimate, committed status, and committed assignee snapshot at sprint-start, stamps sprint started at, and emails the kickoff digest with committed scope to the Scrum Master + Project Lead. The Sprint board becomes the squad’s daily surface.

   • Freeze one starting commitment per issue
   • Updates Sprints, Sprint commitments

Reporter

Internal user outside the squad who needs to file Issues — IT help requesters, internal customers of an API team, stakeholders who hit a bug. Can create Issues and comment on own Issues; sees nothing else.

Project Lead / Product Owner

Owns the Project end-to-end — backlog priority, release planning, estimate overrides, scope decisions. The DRI for the product the Project ships.

Scrum Master / Iteration Manager

Runs the Sprint cadence and the Board. Owns ceremonies (planning, standup, review, retro), WIP discipline, and the burndown.