Proposed Backlog Management and Sprint Planning Workflow Guide

[junminahn]

1. Add an idea column or use a ready to review tag within the unreviewed column for preliminary ideas or incomplete tickets.
2. When a ticket has sufficient details in the unreviewed column, discuss it during a backlog refinement session and move reviewed items to the ready column. As a team, agree on Story Points during refinement.
3. Schedule backlog refinement sessions dynamically based on the volume of tickets in the unreviewed column.
4. After the larger team’s sprint review, assess the team’s capacity and estimate an achievable number of Story Pointsand move tickets to the prioritized backlog based on their priority.
5. Summarize tickets at a high level to prepare for the larger team’s sprint planning session.
6. During sprint planning, assign tickets to team members based on the team and also individual members’ capacity. Story Points does not change unless requirements have changed.
7. In the sprint retrospective, review team and individual achievements, analyzing the sprint’s success. If completed Story Points differ from the plan, discuss what went well and areas for improvement.

[Iryna-Kaplun]

Clarifying questions/comments:

1. I have created 2 additional labels called "idea" and "ready to review". Let's try using it for the proposed purpose to enhance visibility on the idea tickets and those that are ready for review
2. We as a team started reviewing, refining and estimating the tickets in the Unreviewed column before moving them to Ready column
3. We scheduled an additional backlog refinement meeting last Spring and we'll have more ad hoc refinement sessions if needed.
4. PO will work on ticket prioritization and will move the tickets from Ready to Prioritized Backlog
5. The team has a prep meeting on Sprint Wednesday to discuss and summarize the tickets at a high level and prepare for the workstream lead sprint planning session.
6. As a team, we'll continue the conversation about the past sprint analyzing what didn't go well and why.