About Backlog Management
A backlog management skill for Product Owner Agents, focused on prioritizing work by value and keeping items ready for delivery. It covers refinement, readiness checks, stakeholder trade-offs, and common prioritization frameworks.
Key features
- 01MoSCoW, RICE, and WSJF prioritization
- 02Backlog request triage
- 03Epic breakdown into stories
- 04Acceptance criteria and effort estimates
- 05Definition of Ready checks
- 06Roadmap and stakeholder alignment
Use cases
- 01Rank backlog items by value and effort
- 02Refine requests into implementable stories
- 03Check items against Definition of Ready
- 04Explain prioritization trade-offs to stakeholders
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ danhvb/ my-ba-skills --skill backlog-managementAfter installing, type/backlog-managementin Claude Code to confirm it loaded.
Details
From the project READMEBacklog Management Skill
Purpose
Enable the Product Owner Agent to effectively manage the product backlog, prioritize work based on value, and ensure a steady flow of ready work for the team.
Core Responsibilities
- Prioritization: Ordering items to maximize value delivery.
- Refinement: Clarifying and sizing backlog items.
- Readiness: Ensuring items meet the Definition of Ready (DoR).
- Stakeholder Alignment: Balancing competing needs.
Prioritization Frameworks
MoSCoW Method
- Must Have: Critical, non-negotiable for launch.
- Should Have: Important but can wait until next release.
- Could Have: Desirable but impact is less.
- Won't Have: Out of scope for now.
RICE Score
$$ Score = \frac{Reach \times Impact \times Confidence}{Effort} $$
- Reach: How many users impacted?
- Impact: 3 (Massive), 2 (High), 1 (Medium), 0.5 (Low), 0.25 (Minimal).
- Confidence: 100% (High), 80% (Medium), 50% (Low).
- Effort: Person-months/weeks.
WSJF (Weighted Shortest Job First)
Feature of SAFe. $$ WSJF = \frac{Cost of Delay}{Job Size} $$
- Prioritizes high value, time-critical items that are small/quick to do.
Backlog Grooming / Refinement Process
- Review New Requests: Triage incoming suggestions/bugs.
- Estimate High-Level Value: Is this worth doing?
- Break Down Epics: Split large items into implementable stories.
- Add Acceptance Criteria: (Collaborate with BA Agent).
- Estimate Effort: (Collaborate with Dev Team).
- Definition of Ready Check:
- Clear title and description.
- Acceptance criteria defined.
- Dependencies identified.
- Estimated.
Roadmap Planning
- Now: Current sprint/iteration (Detailed).
- Next: Next 1-2 months (High-level stories).
- Later: 3-6 months+ (Epics/Themes).
Stakeholder Communication
- Say "No" by saying "Not yet" or "It's in the backlog."
- Transparently show trade-offs: "If we do X now, Y will be delayed."
Tools
- Jira (Backlog view)
- Lark Base (Table view)
- Trello/Kanban boards
Comments
Markdown supported