🎯 Sprint Validation Readiness Dashboard

Release 6 - Sprint 23 | Order Management & eB2B Workstreams

Workstream view:

Dashboard Generated:

⏰
VALIDATION DEADLINES
BPO + PO Validations
--:--:--
Oct 6, 6:00 PM CEST
UX Validation
--:--:--
Oct 13, 6:00 PM CEST
ℹ️ Data Refresh: ADO data last extracted on October 19, 2026 at 12:01 PM CEST. Validations completed in ADO after this time may not be reflected yet. Dashboard will be refreshed periodically.

πŸ—‚οΈ Sprint Scope Composition

πŸ“Š Overall Sprint Readiness

πŸ“ˆ Validation Progress by Type

πŸ”₯ Validation Status Heatmap

How to read this table

The Solutioning Status indicates the maturity of each User Story and whether it is ready for stakeholder review. It is automatically derived from the ADO State and Assigned To fields.

βšͺ Not Started The User Story has not yet been picked up by the Salesforce team. No validation can be requested at this stage.
πŸ” In ADO: State = New, any assignee.
🟠 In Progress The Salesforce team is actively designing the User Story. If validation is required, the item is not yet ready for review. Validation will be requested once the solution reaches a more stable state.
πŸ” In ADO: State = In Design, any assignee.
🟑 Under Finalisation The Salesforce team is finalising the User Story after design. If validation is required, reviewers may already start providing feedback, understanding that minor updates or clarifications may still be introduced.
πŸ” In ADO: State = Design Completed and assigned to a Salesforce team member.
🟒 Finalised The Salesforce team has completed the User Story. If validation is required, the item is ready for stakeholder review and approval.
πŸ” In ADO: State = Design Completed and unassigned or assigned to someone outside the Salesforce team β€” or any state beyond Design Completed (e.g. Ready to build, In Build, Ready for QA…).
πŸ’Ž Best Effort This item is not part of the committed sprint scope. It will be delivered based on team bandwidth β€” if capacity allows, it will be completed within the sprint; otherwise it will roll over. Validation may be requested but is not guaranteed within the sprint timeline.

πŸ“‹ User Story Validation Tracker

🧩 Sprint Enablers

Enabler stories managed as part of this sprint. Enablers are not subject to the standard validation cycle and are tracked separately from the Validation Status Heatmap.

πŸ” Change Requests

Items flagged as Change Requests, managed as part of this sprint. Change Requests are tracked separately and excluded from the Validation Status Heatmap.

🩺 Sprint Health Checks

Backlog hygiene indicators to surface gaps before Sprint Planning and Release readiness reviews. Click a tile to drill into the affected work items.