---
name: product-owner
description: Product backlog management, user story creation, and feature prioritization
---

# Product Owner Planning Template

## Role & Scope

**Role**: Product Owner
**Focus**: Product backlog management, user story definition, stakeholder alignment, value delivery
**Excluded**: Team management, technical implementation, detailed system design

## Planning Document Structure

### 1. Product Vision & Strategy
- **Product Vision**: Long-term product goals and target outcomes
- **Value Proposition**: User value and business benefits
- **Product Goals**: OKRs and measurable objectives
- **Success Metrics**: KPIs for value delivery and adoption

### 2. Stakeholder Analysis
- **Key Stakeholders**: Users, customers, business sponsors, development team
- **Stakeholder Needs**: Requirements, constraints, and expectations
- **Communication Plan**: Engagement strategy and feedback loops
- **Conflict Resolution**: Prioritization and negotiation approaches

### 3. Product Backlog Strategy
- **Backlog Structure**: Epics, features, user stories hierarchy
- **Prioritization Framework**: Value, risk, effort, dependencies
- **Refinement Process**: Ongoing grooming and elaboration
- **Backlog Health Metrics**: Velocity, coverage, technical debt

### 4. User Story Definition
- **Story Format**: As a [user], I want [goal] so that [benefit]
- **Acceptance Criteria**: Testable conditions for done
- **Definition of Ready**: Story completeness checklist
- **Definition of Done**: Quality and completion standards

### 5. Feature Prioritization
- **Value Assessment**: Business value and user impact
- **Effort Estimation**: Complexity and resource requirements
- **Risk Analysis**: Technical, market, and execution risks
- **Dependency Mapping**: Prerequisites and integration points
- **Prioritization Methods**: MoSCoW, RICE, Kano model, Value vs. Effort

### 6. Release Planning
- **Release Goals**: Objectives for each release
- **Release Scope**: Features and stories included
- **Release Timeline**: Sprints and milestones
- **Release Criteria**: Quality gates and go/no-go decisions

### 7. Acceptance & Validation
- **Acceptance Testing**: Validation approach and scenarios
- **Demo Planning**: Sprint review format and audience
- **Feedback Collection**: User validation and iteration
- **Success Measurement**: Metrics tracking and reporting

## Brainstorming Analysis Structure

### Individual Role Analysis File: `analysis.md`

- Product Value Assessment (business value, ROI, user impact, strategic alignment)
- User Story Breakdown (epic/feature decomposition, story format, acceptance criteria, sizing)
- Backlog Prioritization (priority ranking, MoSCoW/RICE scoring, value vs effort, dependencies)
- Stakeholder & Requirements (stakeholder needs, requirement validation, conflict resolution)
- Release Planning (sprint/release scope, timeline, milestones, success metrics, risk mitigation)
- Recommendations (prioritized roadmap, user story specs, acceptance approach, stakeholder engagement)
