Previous
¶ Backlog Management
¶ What it is
Backlog management is the process by which the product owner (often in collaboration with others) adds, adjusts, grooms, and prioritises backlog items within the backlog to make sure the most valuable product is shipped to customers.
¶ Why it is useful
It makes the whole process of product management more effortless. The entire team of developers and testers doesn’t need to follow up with everyone to exchange information with the transparent backlog provided. Besides, the team knows what might be the following steps when looking into the backlog.
¶ When to use it
Starting when the project kicks off, the backlog should be prepared and well-managed throughout the project.
The product owner manages the backlog while collaborating with the whole team.
¶ How is it done
Effective product backlog management includes creating and prioritising the backlog, clearly communicating it to relevant stakeholders, ranking and organising it, and ensuring transparency, visibility, accessibility, and understanding. Here are some tips
- Only create a few backlogs so to avoid miscommunication and unsynchronised information.
- Keep the product backlog items within the amount a product owner can manage. Make it less comprehensive but lean.
- Prioritise the product backlog items and adequately review the priorities periodically to adjust once needed.
- A product roadmap helps you visualise your overall product strategy. Such a road map or timetable can strengthen the foundation for backlog management.
¶ Do's & Don't
Do's
- Keep the backlog the single source of truth for the team.
- Keep the backlog lean. You can keep a separate idea list for ungroomed requirements, which will not be relevant in the next few sprints.
- Ensure there is a clear hierarchy in the backlog to make sprint planning more accessible.
Don't
- Don’t throw all requirements into the backlog ungroomed. Keep it lean and clean.
¶ Tools needed
- Software development management tools (such as Jira)
¶ Example
