Preserve closed outcomes before rolling work into the next iteration.
3 stages · 0 approvals
Follow the process from start to finish. Select a step to see who acts and what changes.
On the Sprint EndDate the Scrum Master flips Status: Active → Closed. The sprint-end-rollover workflow fires, finds every Issue in the closing Sprint with Status NOT IN (Done, Cancelled), and first freezes SprintOutcomes for all committed, added and removed issues. It then applies Projects.IssueRolloverRule: either nulls Issues.Sprint (back to Backlog) or sets it to the next Future Sprint. The velocity-recompute job upserts the Sprint's TeamVelocity row with CommittedPoints (from SprintCommitments), CompletedPoints (from immutable SprintOutcomes recorded before rollover, using the agreed estimate unit), and Carryover; refreshes the trailing-3 average. The retrospective digest emails to Scrum Master + Project Lead. Scrum Master writes RetrospectiveNotes on the closed Sprint.
Freeze outcomes before moving current issue assignmentsEvery 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.
Separate missing evidence and scope changes from completed workOn 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.
| Stage | Records | Effect |
|---|---|---|
| 1 Close and roll over | SprintOutcomesSprintCommitmentsIssues | Freeze outcomes before moving current issue assignments |
| 2 Review delivery signals | TeamVelocityBurndownsEpicProgress | Separate missing evidence and scope changes from completed work |
| 3 Prepare next commitment | SprintsBacklogs | Use history as a planning aid in the same unit |
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 | Committed Points | Completed Points | Carryover | Trailing Three Average |
|---|---|---|---|---|
| SPR-69997 | 400 | 320 | 80 | 550 |
| SPR-83087 | 230 | 368 | 92 | 260 |
| SPR-92438 | 900 | 360 | 540 | 460 |
| SPR-83987 | 320 | 576 | 64 | 790 |
| SPR-58987 | 250 | 150 | 100 | 810 |
| SPR-57223 | 60 | 84 | 36 | 630 |
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.
| Snapshot Date | Remaining Estimate | Ideal Remaining | Scope Added Points | Scope Removed Points |
|---|---|---|---|---|
| 17 Sep | 430 | 100 | 930 | 790 |
| 12 Sep | 470 | 170 | 940 | 720 |
| 14 Sep | 380 | 880 | 770 | 870 |
| 19 Sep | 210 | 590 | 910 | 910 |
| 09 Sep | 780 | 240 | 360 | 370 |
| 15 Sep | 330 | 210 | 290 | 370 |
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.
| Issue Key | Title | Issue Type | Priority | Parent Epic |
|---|---|---|---|---|
| IK-556 | Lowest iss-657 | IT-3797 | Lowest | EPC-5237 |
| IK-365 | Low iss-639 | IT-7722 | Low | EPC-2365 |
| IK-758 | Medium iss-304 | IT-3806 | Medium | EPC-3817 |
| IK-221 | High iss-494 | IT-9562 | High | EPC-4666 |
| IK-380 | Highest iss-910 | IT-4651 | Highest | EPC-9960 |
| IK-966 | Critical iss-851 | IT-4743 | Critical | EPC-5029 |
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.
| Issue Key | Project | Title | Issue Type | Priority |
|---|---|---|---|---|
| IK-388 | PRJ-2044 | Lowest iss-914 | IT-1227 | Lowest |
| IK-159 | PRJ-5411 | Low iss-143 | IT-7703 | Low |
| IK-405 | PRJ-1108 | Medium iss-521 | IT-8469 | Medium |
| IK-538 | PRJ-6119 | High iss-595 | IT-5339 | High |
| IK-163 | PRJ-7748 | Highest iss-407 | IT-5999 | Highest |
| IK-978 | PRJ-7861 | Critical iss-509 | IT-3144 | Critical |
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.
| Issue Key | Project | Title | Issue Type | Priority |
|---|---|---|---|---|
| IK-388 | PRJ-2044 | Lowest iss-914 | IT-1227 | Lowest |
| IK-159 | PRJ-5411 | Low iss-143 | IT-7703 | Low |
| IK-405 | PRJ-1108 | Medium iss-521 | IT-8469 | Medium |
| IK-538 | PRJ-6119 | High iss-595 | IT-5339 | High |
| IK-163 | PRJ-7748 | Highest iss-407 | IT-5999 | Highest |
| IK-978 | PRJ-7861 | Critical iss-509 | IT-3144 | Critical |
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.
| Issue Key | Project | Title | Severity | Reporter |
|---|---|---|---|---|
| IK-468 | PRJ-6674 | Lowest iss-966 | Sev1 | WS |
| IK-574 | PRJ-9723 | Low iss-123 | Sev2 | UC |
| IK-773 | PRJ-8533 | Medium iss-319 | Sev3 | YR |
| IK-981 | PRJ-5727 | High iss-188 | Sev4 | NP |
| IK-642 | PRJ-7482 | Highest iss-934 | Sev1 | BA |
| IK-821 | PRJ-5540 | Critical iss-685 | Sev2 | NZ |
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 | Epic.Owner | Epic.Status | Epic.Target Version | Total Issues |
|---|---|---|---|---|
| EPC-7139 | EPC-796 | Open | Rev A | 30 |
| EPC-4388 | EPC-921 | Closed | Rev B | 80 |
| EPC-5563 | EPC-215 | Open | Rev C | 600 |
| EPC-3550 | EPC-810 | Closed | Rev D | 880 |
| EPC-3120 | EPC-458 | Open | Rev E | 160 |
| EPC-8895 | EPC-963 | Closed | Rev F | 190 |
Per Project, per Epic: TotalIssues / DoneIssues / PercentComplete, ForecastReleaseDate, TargetVersion, and Milestones touched. The Stakeholder roadmap view.
| Epic | Epic.Owner | Epic.Status | Epic.Target Version | Total Issues |
|---|---|---|---|---|
| EPC-7139 | EPC-796 | Open | Rev A | 30 |
| EPC-4388 | EPC-921 | Closed | Rev B | 80 |
| EPC-5563 | EPC-215 | Open | Rev C | 600 |
| EPC-3550 | EPC-810 | Closed | Rev D | 880 |
| EPC-3120 | EPC-458 | Open | Rev E | 160 |
| EPC-8895 | EPC-963 | Closed | Rev F | 190 |
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.
Turn incoming work into a prioritised, reviewed iteration scope.
3 stages · 0 approvals
Apply the same workflow and quality checks to every delivery transition.
3 stages · 1 approval
Review eligible issue scope before recording the release version.
3 stages · 1 approval
Create your ERP.AI account and get started with Proto.
We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy
We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.
Learn more about how we use cookiesThese cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.
These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.
These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.