Regular Review: The product team reviews this backlog on a regular cadence to ensure items are in the correct order based on priority. Given the work has not been started, priority order is subject to change up until it has been discussed with engineering to be worked on in the meeting described below.
Customer impact, reach, expected effort, committed delivery dates, and other relevant factors are considered when debating and determining priorities.
Pre-Sprint Product<>Engineering Planning
Purpose & Cadence: The product team will meet with the Software Pod Engineering Lead (Evan) every Monday before a new sprint to align on the upcoming sprint’s feature work.
Sprint Work Alignment: Input from both product and engineering will be considered to determine what work will be done in the upcoming sprint - including factors such as prioritization order, current work in progress, and team capacity. For example, the engineering lead might decide that only the #3 item from the backlog can be picked up due to capacity constraints, even if the #1 and #2 items are higher priority.
Cross-Pod Collaboration: If new work requires collaboration with other pods (SRE/Data), additional ad-hoc syncs will be arranged with those leads.
Ticket Updates: When new features are started, their status is to be updated to active and moved from the Product Leadership Backlog to the Software Pod Board in ADO.