Purpose:
Throughout the course of a project's lifecycle, you will need to review and refine the project's Azure Backlog. These steps should be followed to ensure that the overall project stays on track and no user stories or tasks fall through the cracks during the development process.
Best Practices:
PM should conduct their own Backlog Refinement as part of their personal Sprint Planning or during a PM working session. When a PM Working Session is needed it will often be conducted during the daily PM Scrum meeting.
Ideally, you can accomplish this review by undertaking an initial Backlog Cleanup / Feature Parity Check.
Steps to Conduct Backlog Refinement:
Go through each user story and its associated tasks in the backlog, discussing the state of each one with the developers.
Best Practice: Share your screen on the Azure Dev Ops Backlog view where the project in question appears then move through the backlog one item at a time. This enables anyone in attendance to be able view each item's ticket as we discuss it.
Gather this information:
Use Basecamp to relay any follow-up questions for the client then update the Azure ticket with the information from the client. Obviously, this should be done quickly so the developer can keep moving through the task.
Any concerns regarding the complexity of a ticket, the associated hours estimation on a ticket, or any other aspects of the ticket should be discussed with your PM Team Lead prior to being brought to the attention of the client.
It is a great idea to take the opportunity, following the Backlog Refinement Meeting, to utilize the information produced in the meeting to assign the project's remaining tickets in the backlog to future sprints. This will help make your upcoming sprint planning for this project easier.
==Add Caroline's video here for reference==