Core ERP Backlog Prioritization (**NEW**)
Core ERP represents all clients that are not currently on Unity or in the current wave of Unity merges.
Core ERP engineering will handle client committed SOW work to be coded on non Unity branches and technical debt for non unity clients
Cross Company Team Communication
Because Core ERP services so many needs across Product, Services, and Support, it is imperative that we collaborate as a single team to groom the backlog for each sprint.
Backlog Grooming
The first Core ERP Backlog grooming sessions will take Thursday, June 1, 2023 and continue every two weeks
This allows for the priorities to be reviewed by the Scrum Master and Scrum Teams on Friday with questions presented Monday and a final list on Tuesday for selection
Backlog grooming will include representatives from Product, Services, and Support
The purpose is to ensure the most critical SOW feature tickets and most critical technical debt bug tickets are at the top of the backlog list
This is also the time to discuss any committed dates so that those are not missed
Ticket Escalation after start of Sprint
Below denotes how to handle tickets that need inclusion in a sprint that has already started.
Send a note in Teams or Slack to the Product Mangers of the team (@a user and @a user )
Note the ticket requesting escalation and provide reason for request
Product Managers will contact the Scrum Master to determine what tickets have not been started and are eligible for removal
Product Managers will determine which ticket to swap for the requested escalation
Disclaimers
Product reserves the right to deny the inclusion request if there are no available tickets to swap out.
Scrum Masters will not be expected to absorb additional capacity after the start of the sprint.
Only Product Managers should be reaching out to Scrum Masters or the Engineering team
If Services or Support have a question, please direct them to the Product Manager