Purpose
Platform Owner Meetings create a regular alignment point between Product Owners, Platform Owners and relevant stakeholders. They are used to review sprint outcomes, confirm near-term priorities, check roadmap and backlog health, and make sure the work being planned by the team still reflects business priorities.
There are two related cadences: a bi-weekly sprint review and planning alignment session around each sprint boundary, and a monthly roadmap and backlog review focused on the next three sprints and wider platform direction.
Bi-weekly alignmentReview sprint commitments, what was delivered, de-scoped or carried forward, and priorities for the next sprint.
Monthly roadmap reviewReview roadmap, backlog priorities, upcoming work and the next three sprints.
Quarterly sign-off inputPrepare platform priorities and decisions for quarterly planning and commitment review.
Attendees
- Product Owner: required; facilitates the session and brings the sprint, backlog and roadmap evidence.
- Platform Owner: required; confirms business priority, direction and sign-off decisions.
- Relevant stakeholders / Business SMEs: included where specific features, constraints or upcoming events need review.
- Scrum Master / Delivery Manager: optional; supports sprint evidence, delivery risks and action tracking.
- Engineering Lead / Tech Lead: optional; included when feasibility, dependencies, blockers or technical sequencing need discussion.
- Support Lead: optional; included where BAU demand, support readiness or recurring service desk demand impacts prioritisation.
Input
- Current sprint report, including what was committed, delivered, de-scoped, not completed, carried forward or added mid-sprint.
- Updated Jira roadmap, Jira Projects and platform backlog views.
- Current sprint goals, next sprint goals, open blockers, dependencies and risks.
- Upcoming events, platform constraints, resource availability and business deadlines.
- Product discovery outputs, Ideas Backlog items and features marked to be prioritised or parked for future consideration.
- Quarterly planning board and any items proposed for rollover, de-scope or next-quarter commitment.
Output
- Confirmed priorities for the next sprint or planning cycle.
- Agreement on what stays committed, rolls over, moves to discovery, is parked, or is de-scoped.
- Platform Owner comments and decisions captured with enough context for wider technology visibility.
- Risks, blockers, dependency decisions or escalations clearly owned.
- Jira roadmap, Jira Projects and the platform backlog updated to reflect agreed priorities and status.
- Actions for quarterly planning, Executive Steering Committee or cross-platform dependency discussions where needed.
Responsibilities
- Product Owner: schedule and facilitate the sessions, prepare sprint evidence, maintain the forward-looking backlog and keep Jira roadmap and Jira Projects up to date.
- Product Owner: ensure stories for the next sprint are refined and future sprint items are actively progressing through refinement.
- Platform Owner: confirm business priority, provide context, approve or challenge proposed commitments and support decisions on rollover, de-scope or discovery.
- Scrum Master / Delivery Manager: support action tracking, dependency visibility and sprint ceremony alignment.
- Engineering Lead / Tech Lead: provide feasibility, complexity, risk and sequencing input.
- Stakeholders: provide business context early, not only at sign-off.