---
title: "Backlog Management Template"
methodology: "universal"
complexity: "advanced"
owner: "mirichard"
updated: "2026-09-19"
primary_principles: ["value-focus", "adaptability"]
secondary_principles: ["stakeholder-engagement", "evidence-based-decisions"]
principle_rationale: "Orders adaptable delivery choices by stakeholder value and supporting evidence."
---

# Backlog Management Template

## When to Use

- During product planning and delivery when backlog ordering needs explicit value and acceptance criteria.
- When a Product Owner must balance stakeholder requests, dependencies, and refinement readiness.

## When NOT to Use

- As a separate authoritative backlog that duplicates the team's active work system.
- Do not treat completed metadata or a filled checklist as evidence that the underlying work is done. See [Metadata theater](../../../../docs/principles/anti-patterns.md#metadata-theater).

## Pairs Well With

- [User Story Template](../../../../domains/uncertainty/role-based-toolkits/product-owner/user-story-template.md).
- [Backlog Refinement Template](../../../../domains/team/role-based-toolkits/scrum-master/agile-ceremonies/backlog-refinement-template.md).

Selection context: Uncertainty domain; universal methodology; advanced complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../../meta/architecture-research/800-801-context-assessment-model.md).

## Scrum tailoring

These worksheets and suggested agendas are optional practices. In Scrum, the Developers own the plan for delivering the Sprint Goal; selected work is a forecast that can be adapted. A Definition of Ready and story points are optional team practices. Use the product Definition of Done consistently, and treat the Sprint Review as inspection and adaptation rather than a release-approval gate. See the [Scrum Guide](https://scrumguides.org/scrum-guide.html).


## Product Information
- **Product Name**: [Product Name]
- **Product Owner**: [Name]
- **Date**: [Date]
- **Sprint/Release**: [Current Sprint/Release]

## Backlog Overview
- **Total Items**: [Number]
- **Ready for Development**: [Number]
- **In Progress**: [Number]
- **Done**: [Number]

## Prioritization Framework

### Prioritization Criteria
| Criteria | Weight | Description |
|----------|--------|-------------|
| Business Value | 30% | Revenue impact, cost savings, strategic alignment |
| User Impact | 25% | User satisfaction, user experience improvement |
| Technical Risk | 20% | Implementation complexity, technical debt |
| Dependencies | 15% | Blocking other work, external dependencies |
| Effort Required | 10% | Development time, resource requirements |

### Priority Levels
- **P0 - Critical**: Must have, business critical
- **P1 - High**: Should have, significant value
- **P2 - Medium**: Could have, moderate value
- **P3 - Low**: Nice to have, minimal value

## Product Backlog Items

### Current Sprint Backlog
| Item | Priority | Estimate | Status | Assignee | Notes |
|------|----------|----------|--------|----------|-------|
| [User Story 1] | P0 | 8 pts | In Progress | [Name] | [Notes] |
| [User Story 2] | P1 | 5 pts | Done | [Name] | [Notes] |
| [User Story 3] | P1 | 3 pts | To Do | [Name] | [Notes] |

### Next Sprint Candidates
| Item | Priority | Estimate | Dependencies | Ready? |
|------|----------|----------|--------------|--------|
| [User Story 4] | P0 | 13 pts | Story 1 complete | ✅ |
| [User Story 5] | P1 | 8 pts | External API | ❌ |
| [User Story 6] | P1 | 5 pts | None | ✅ |

### Product Roadmap Items
| Epic/Feature | Target Release | Business Value | Status |
|--------------|----------------|----------------|--------|
| [Epic 1] | Q2 2024 | High | In Progress |
| [Epic 2] | Q3 2024 | Medium | Planned |
| [Epic 3] | Q4 2024 | High | Research |

## Backlog Refinement

### Refinement Schedule
- **Weekly Refinement**: [Day and Time]
- **Participants**: Product Owner, Scrum Master, Development Team
- **Duration**: [Duration]

### Refinement Checklist
- [ ] User stories have clear acceptance criteria
- [ ] Stories are estimated by the team
- [ ] Dependencies are identified
- [ ] Stories meet Definition of Ready
- [ ] Priority is clear and justified
- [ ] Technical approach is understood

### Recently Refined Items
| Item | Date Refined | Estimate | Notes |
|------|--------------|----------|-------|
| [Story 1] | [Date] | 8 pts | [Refinement notes] |
| [Story 2] | [Date] | 5 pts | [Refinement notes] |

## Acceptance Criteria Standards

### Story Requirements
- [ ] Clear user story format (As a... I want... So that...)
- [ ] Specific, measurable acceptance criteria
- [ ] Given-When-Then scenarios where appropriate
- [ ] UI/UX requirements defined
- [ ] Performance criteria specified
- [ ] Security considerations noted

### Definition of Ready
- [ ] Story is clearly understood by the team
- [ ] Acceptance criteria are defined
- [ ] Story is estimated
- [ ] Dependencies are identified
- [ ] Designs/mockups available (if needed)
- [ ] Technical approach agreed upon

### Definition of Done
- [ ] All acceptance criteria met
- [ ] Code reviewed and approved
- [ ] Tests written and passing
- [ ] Documentation updated
- [ ] Product Owner acceptance
- [ ] No known defects

## Stakeholder Management

### Key Stakeholders
| Stakeholder | Role | Interest | Communication Method |
|-------------|------|----------|---------------------|
| [Name] | [Role] | [Interest] | [Method] |
| [Name] | [Role] | [Interest] | [Method] |

### Feedback Collection
- **User Feedback**: [Methods for collecting user feedback]
- **Stakeholder Input**: [Regular review meetings, surveys]
- **Market Research**: [Methods for market validation]

## Metrics and KPIs

### Velocity Tracking
| Sprint | Planned | Completed | Velocity |
|--------|---------|-----------|----------|
| Sprint 1 | 25 | 23 | 23 |
| Sprint 2 | 25 | 27 | 27 |
| Sprint 3 | 28 | 25 | 25 |
| **Average** | **26** | **25** | **25** |

### Business Metrics
- **Feature Adoption Rate**: [%]
- **User Satisfaction Score**: [Score]
- **Business Value Delivered**: [Metric]
- **Customer Retention**: [%]

## Risk Management

### Current Risks
| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
| [Risk 1] | High | Medium | [Mitigation strategy] |
| [Risk 2] | Medium | High | [Mitigation strategy] |

### Dependencies
| Dependency | Type | Impact | Status | Owner |
|------------|------|--------|--------|-------|
| [Dependency 1] | External | High | [Status] | [Owner] |
| [Dependency 2] | Internal | Medium | [Status] | [Owner] |

## Backlog Health Metrics

### Health Indicators
- **Backlog Size**: [Number of items]
- **Ready Stories**: [Percentage ready for next sprint]
- **Velocity Stability**: [Trend]
- **Cycle Time**: [Average days from start to done]
- **Lead Time**: [Average days from idea to delivery]

### Quality Metrics
- **Story Completion Rate**: [%]
- **Defect Rate**: [Defects per story]
- **Rework Rate**: [% of stories requiring rework]

## Action Items
- [ ] [Action 1] - Owner: [Name] - Due: [Date]
- [ ] [Action 2] - Owner: [Name] - Due: [Date]
- [ ] [Action 3] - Owner: [Name] - Due: [Date]

## Notes and Decisions
[Space for recording important decisions, changes, and notes about backlog management]

---

**Maintained by**: [Product Owner Name]  
**Last Updated**: [Date]\
**Next Review**: [Date]

*Systematic product backlog management for maximum value delivery*