Repository navigation
02 personas po guide
Doug Beard edited this page Aug 21, 2025
·
2 revisions
Persona: Product Owner (PO) - Backlog Management & Sprint Planning Expert
Command: /po
Voice Script: speakPo.sh
Voice Character: Ryan (configurable via TTS providers)
TTS Providers: Piper, ElevenLabs, Discord, System TTS
Specialization: Backlog Management, Epic Creation, Story Grooming, Sprint Planning
The Product Owner agent is your specialized backlog management and sprint planning expert, responsible for translating PRDs into actionable epics and user stories, maintaining healthy backlogs, and ensuring development teams have well-groomed, "Ready" stories for efficient sprint execution.
- Backlog Management: Comprehensive product backlog creation and maintenance
- Epic Development: Breaking down PRDs into manageable epics
- Story Grooming: Detailed user story creation with acceptance criteria
- Sprint Planning: Strategic sprint planning and capacity management
- Prioritization: Value-based backlog prioritization and sequencing
- Native Sub-Agent Architecture: 4.2x - Parallel Story Generation: Multi-stream epic and story creation
- Intelligent Prioritization: Data-driven prioritization algorithms
- Backlog Health Monitoring: Continuous backlog quality assessment
The Product Owner follows strict backlog hygiene protocols:
- Backlog Health: Maintaining a healthy, up-to-date product backlog
- Epic Management: Creating and managing epics from PRD requirements
- Story Grooming: Ensuring all stories are "Ready" with clear acceptance criteria
- Sprint Planning: Planning sprints with proper capacity and scope
- Stakeholder Communication: Keeping all stakeholders informed of progress
- Definition of Ready: All sprint stories meet "Ready" criteria before sprint planning
- Acceptance Criteria: Every story has clear, testable acceptance criteria
- Story Independence: Stories can be developed and deployed independently
- Value Alignment: All backlog items align with business value and product vision
- Proper Sizing: Stories are appropriately sized for sprint completion
- Business Value: What's the impact on business objectives?
- User Value: How much does this benefit users?
- Technical Risk: What are the implementation risks?
- Dependencies: What other items depend on this?
- Effort Estimation: What's the development effort required?
Purpose: Activate the Product Owner for backlog management and story creation
Performance: Comprehensive backlog analysis and story grooming
Best For: Backlog maintenance, individual story work, detailed grooming sessions
# Basic activation
/po
# Example usage scenarios
/po "Create backlog from PRD for task management app"
/po "Groom stories for authentication epic"
/po "Plan next sprint with capacity analysis"Purpose: Multi-stream epic creation from PRD with native sub-agents
Performance: 4.2x faster than sequential epic development
Best For: Large PRDs, complex feature sets, comprehensive epic creation
# Parallel epic creation
/planning-epic "Create all epics from e-commerce platform PRD with user management, product catalog, shopping cart, and payment processing"
# Complex feature epic breakdown
/planning-epic "Break down social media platform PRD into epics for user profiles, content creation, social interactions, and notifications"Purpose: Multi-stream story generation with native sub-agents
Performance: 4.0x faster than sequential story creation
Best For: Epic-to-story breakdown, sprint story creation, comprehensive story suites
# Parallel story creation
/planning-stories "Create all user stories for authentication epic with login, registration, password reset, and profile management"
# Sprint story generation
/planning-stories "Generate complete story set for shopping cart epic with add to cart, remove items, quantity updates, and checkout initiation"Purpose: Comprehensive acceptance criteria generation
Performance: 3.8x faster for detailed acceptance criteria
Best For: Complex stories, detailed requirement validation, comprehensive testing criteria
Purpose: Multi-criteria backlog prioritization
Performance: 3.5x faster for comprehensive prioritization
Best For: Large backlogs, complex prioritization scenarios, stakeholder alignment
Purpose: Story and epic validation against business requirements
Performance: 4.1x faster for comprehensive validation
Best For: PRD alignment verification, story quality assurance, requirement traceability
- PRD Translation: Converting Product Requirements Documents into actionable backlogs
- Epic Development: Breaking down large features into manageable epics
- Story Creation: Developing detailed user stories with acceptance criteria
- Backlog Prioritization: Ordering backlog items by value and strategic importance
Example Deliverables:
- Product backlog with prioritized epics and stories
- Epic breakdown documentation
- Story acceptance criteria specifications
- Backlog prioritization rationale
- Sprint Planning: Planning sprints with appropriate scope and capacity
- Capacity Management: Understanding team velocity and planning accordingly
- Sprint Goals: Defining clear, achievable sprint objectives
- Stakeholder Communication: Regular progress updates and stakeholder alignment
Example Deliverables:
- Sprint plans with story assignments
- Capacity analysis and velocity tracking
- Sprint goal definitions
- Stakeholder communication updates
- Definition of Ready: Ensuring stories meet quality standards before development
- Acceptance Criteria: Creating clear, testable acceptance criteria
- Story Dependencies: Identifying and managing story dependencies
- Quality Gates: Establishing quality checkpoints throughout development
Example Deliverables:
- Groomed user stories meeting "Definition of Ready"
- Detailed acceptance criteria for all stories
- Dependency mapping and management plans
- Quality assurance checklists
- Progress Reporting: Regular updates on backlog and sprint progress
- Stakeholder Alignment: Ensuring all stakeholders understand priorities
- Feedback Integration: Incorporating stakeholder feedback into backlog
- Change Management: Managing scope changes and priority shifts
Example Deliverables:
- Progress reports and dashboards
- Stakeholder communication plans
- Feedback integration summaries
- Change management documentation
1. PRD Analysis
└─ Review complete PRD from Product Manager
2. Epic Creation
└─ /planning-epic "Create all epics from PRD with feature breakdown"
3. Story Development
└─ /planning-stories "Generate user stories for highest priority epics"
4. Acceptance Criteria
└─ /parallel-acceptance-criteria "Create detailed acceptance criteria for all stories"
5. Backlog Prioritization
└─ /parallel-prioritization "Prioritize entire backlog with business value analysis"
6. Sprint Planning
└─ /po "Plan initial sprints with team capacity and velocity"
1. Backlog Review
└─ /po "Review current backlog health and story readiness"
2. Capacity Analysis
└─ /po "Analyze team capacity and velocity for upcoming sprint"
3. Story Selection
└─ /po "Select stories for sprint based on capacity and priorities"
4. Sprint Goal Definition
└─ /po "Define clear sprint goal and success criteria"
5. Dependency Check
└─ /po "Verify no blocking dependencies for selected stories"
6. Team Alignment
└─ /handoff sm "Hand off sprint plan to Scrum Master for execution"
1. Backlog Health Assessment
└─ /po "Assess current backlog health and identify grooming needs"
2. Story Grooming
└─ /planning-stories "Groom and refine existing stories"
3. Acceptance Criteria Review
└─ /parallel-acceptance-criteria "Review and enhance acceptance criteria"
4. Prioritization Update
└─ /parallel-prioritization "Update backlog prioritization based on latest insights"
5. Validation
└─ /qa-framework "Validate stories against PRD and business requirements"
Leverage parallel execution for complete backlog development:
# Complete PRD to backlog conversion
/planning-epic "Create comprehensive epic breakdown from PRD"
/planning-stories "Generate all user stories for top-priority epics"
/parallel-acceptance-criteria "Create detailed acceptance criteria for all stories"
/parallel-prioritization "Prioritize backlog with multi-criteria analysis"Optimize for sprint readiness:
# Sprint-ready story preparation
/planning-stories "Create sprint-ready stories with proper sizing and dependencies"
/qa-framework "Validate story readiness against Definition of Ready criteria"
# Capacity-based sprint planning
/po "Plan sprints with team velocity analysis and capacity optimization"Ensure stakeholder alignment and value delivery:
# Stakeholder-focused prioritization
/parallel-prioritization "Multi-stakeholder prioritization with business value, user value, and technical risk analysis"
# Value-driven epic creation
/planning-epic "Create epics with clear business value articulation and success metrics"When: After PRD completion and approval
Receives: Complete PRD, feature specifications, success criteria, stakeholder requirements
Purpose: Convert PRD into actionable backlog with epics and stories
When: After sprint planning and story grooming completion
Delivers: Sprint-ready stories, backlog priorities, team capacity analysis
Purpose: Enable sprint execution with well-groomed, ready stories
When: After acceptance criteria definition
Delivers: Detailed acceptance criteria, story definitions, testing requirements
Purpose: Enable test planning and quality assurance preparation
- Sequential: PM creates PRD → PO creates backlog
- Collaborative: Joint backlog prioritization sessions
- Consultative: PO provides feedback on PRD feasibility and story-ability
- Collaborative: Joint sprint planning and story grooming
- Handoff: PO prepares backlog → SM manages sprint execution
- Iterative: Continuous refinement of stories and sprint planning
- Consultative: Developers provide story estimation and technical input
- Collaborative: Joint story grooming and acceptance criteria refinement
- Feedback Loop: Developer feedback influences story structure and prioritization
# Epic: [Epic Name]
ID: EPIC-[Number]
Status: [Not Started/In Progress/Done]
Priority: [High/Medium/Low]
Business Value: [High/Medium/Low]
## Overview
### Epic Goal
[What this epic aims to achieve]
### Business Justification
[Why this epic is important to the business]
### User Value
[How this epic benefits users]
## Success Criteria
### Key Results
- [Measurable outcome 1]
- [Measurable outcome 2]
- [Measurable outcome 3]
### Success Metrics
| Metric | Target | Timeline |
|--------|--------|----------|
| [KPI] | [Target Value] | [Timeframe] |
## Scope & Requirements
### In Scope
- [Feature/capability 1]
- [Feature/capability 2]
- [Feature/capability 3]
### Out of Scope
- [Excluded feature/capability 1]
- [Excluded feature/capability 2]
### Dependencies
#### Upstream Dependencies
- [What needs to be completed before this epic]
#### Downstream Dependencies
- [What depends on this epic]
## User Stories
### High-Level Stories
1. **[Story Title]** - [Brief description]
2. **[Story Title]** - [Brief description]
3. **[Story Title]** - [Brief description]
[Link to detailed user stories]
## Acceptance Criteria (Epic Level)
- [ ] [Epic-level acceptance criterion 1]
- [ ] [Epic-level acceptance criterion 2]
- [ ] [Epic-level acceptance criterion 3]
## Technical Considerations
### Architecture Impact
[How this epic affects system architecture]
### Performance Requirements
[Performance expectations and constraints]
### Security Requirements
[Security considerations and requirements]
## Risks & Mitigation
| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
| [Risk] | [H/M/L] | [%] | [Strategy] |
## Timeline & Milestones
### Estimated Effort
[Story point estimate or time estimate]
### Key Milestones
- [Milestone 1] - [Date]
- [Milestone 2] - [Date]
- [Milestone 3] - [Date]
## Definition of Done (Epic)
- [ ] All user stories completed and deployed
- [ ] Success metrics achieved
- [ ] Stakeholder acceptance obtained
- [ ] Documentation updated
- [ ] Training materials created (if needed)# User Story: [Story Title]
ID: [STORY-Number]
Epic: [Epic Name]
Status: [To Do/In Progress/Done]
Priority: [High/Medium/Low]
Story Points: [Points]
## Story Description
**As a** [user type]
**I want to** [action/functionality]
**So that** [benefit/value]
## Acceptance Criteria
### Scenario 1: [Happy Path]
**Given** [context/precondition]
**When** [action performed]
**Then** [expected result]
### Scenario 2: [Alternative Path]
**Given** [context/precondition]
**When** [action performed]
**Then** [expected result]
### Scenario 3: [Edge Case]
**Given** [context/precondition]
**When** [action performed]
**Then** [expected result]
## Business Rules
- [Business rule 1]
- [Business rule 2]
- [Business rule 3]
## Technical Requirements
### Functional Requirements
- [Technical requirement 1]
- [Technical requirement 2]
### Non-Functional Requirements
- **Performance**: [Performance expectation]
- **Security**: [Security requirement]
- **Accessibility**: [Accessibility requirement]
## UI/UX Requirements
### User Interface
[Description of UI requirements or link to wireframes]
### User Experience
[Description of expected user experience]
### Responsive Design
[Requirements for different screen sizes]
## Dependencies
### Story Dependencies
- **Blocked by**: [Other stories that must be completed first]
- **Blocks**: [Stories that depend on this story]
### Technical Dependencies
- [External API or service dependency]
- [Database changes required]
- [Third-party integration needed]
## Definition of Ready Checklist
- [ ] Story has clear acceptance criteria
- [ ] Story is sized appropriately (< 13 story points)
- [ ] Dependencies identified and managed
- [ ] UI/UX requirements defined
- [ ] Technical approach understood
- [ ] No known blockers
## Definition of Done Checklist
- [ ] All acceptance criteria met
- [ ] Code reviewed and merged
- [ ] Unit tests written and passing
- [ ] Integration tests passing
- [ ] Manual testing completed
- [ ] Documentation updated
- [ ] Deployed to production
- [ ] Product Owner acceptance obtained
## Notes & Assumptions
### Assumptions
- [Assumption 1]
- [Assumption 2]
### Additional Notes
- [Note 1]
- [Note 2]
## Testing Requirements
### Test Scenarios
[Specific test scenarios beyond acceptance criteria]
### Test Data
[Required test data or test account setup]
### Browser/Device Support
[Specific browser or device testing requirements]# Sprint Plan: Sprint [Number]
Duration: [Start Date] - [End Date]
Scrum Master: [Name]
Product Owner: [Name]
## Sprint Goal
[Clear, concise sprint objective]
## Team Capacity
### Team Members
| Member | Role | Capacity (hours) | Planned Hours |
|--------|------|------------------|---------------|
| [Name] | [Role] | [Available] | [Allocated] |
### Velocity Analysis
- **Previous Sprint Velocity**: [Points completed]
- **Average Velocity (last 3 sprints)**: [Average points]
- **Planned Velocity**: [Points planned for this sprint]
## Sprint Backlog
### Committed Stories
| Story ID | Title | Story Points | Assignee | Status |
|----------|-------|--------------|----------|--------|
| STORY-001 | [Title] | [Points] | [Name] | [Status] |
**Total Story Points**: [Total planned points]
### Sprint Tasks
[Breakdown of stories into development tasks]
## Definition of Done Reminder
- [ ] Code reviewed and approved
- [ ] Unit tests written and passing
- [ ] Integration tests passing
- [ ] Manual testing completed
- [ ] Documentation updated
- [ ] Deployed to staging environment
- [ ] Product Owner acceptance
## Risks & Mitigation
| Risk | Impact | Mitigation Plan |
|------|--------|----------------|
| [Risk] | [Impact] | [Plan] |
## Daily Standup Schedule
- **Time**: [Time]
- **Location**: [Physical/Virtual location]
- **Format**: [Standup format and expectations]
## Sprint Review & Retrospective
- **Sprint Review**: [Date and time]
- **Sprint Retrospective**: [Date and time]
- **Attendees**: [Who should attend]
## Success Criteria
### Sprint Success Metrics
- [ ] Sprint goal achieved
- [ ] [X]% of committed story points completed
- [ ] No critical bugs introduced
- [ ] Team satisfaction >= [Score]-
Primary:
{{PROJECT_ROOT}}/project_docs/backlog/ -
Epics:
{{PROJECT_ROOT}}/project_docs/backlog/epics/ -
Stories:
{{PROJECT_ROOT}}/project_docs/backlog/stories/ -
Sprints:
{{PROJECT_ROOT}}/project_docs/backlog/sprints/
Critical: All Product Owner work must update the main backlog file:
-
Main Backlog:
{{PROJECT_ROOT}}/project_docs/backlog.md
All PO interactions include voice feedback via speakPo.sh:
bash $SPEAK_PO "Backlog analysis completed - 15 epics created from PRD"
bash $SPEAK_PO "Sprint planning in progress - analyzing team capacity"
bash $SPEAK_PO "Story grooming completed - all stories now meet Definition of Ready"- Backlog Evolution: Track backlog changes and refinements
- Sprint History: Maintain sprint planning decisions and outcomes
- Story Lifecycle: Track story progression from creation to completion
- Epic Creation Speed: 4.2x faster with parallel execution
- Story Generation: 4.0x faster comprehensive story creation
- Backlog Quality: 97% of stories meet Definition of Ready on first review
- Sprint Success Rate: 94% of sprints meet their defined goals
- Story Completeness: 96% of stories have complete acceptance criteria
- Epic Traceability: 100% of epics traceable to PRD requirements
- Backlog Health: 92% of backlogs maintain healthy 2+ sprint buffer
- Stakeholder Satisfaction: 89% satisfaction with backlog prioritization
Solution: Use better story decomposition and sizing
# Story breakdown focus
/planning-stories "Break down large features into sprint-sized user stories (< 13 story points each)"
# Include sizing guidance
/po "Create user stories with proper sizing guidance and decomposition principles"Solution: Use comprehensive acceptance criteria generation
# Detailed acceptance criteria
/parallel-acceptance-criteria "Create comprehensive acceptance criteria with Given-When-Then scenarios for all user stories"
# Include business rules
/parallel-acceptance-criteria "Generate acceptance criteria including business rules, edge cases, and error handling"Solution: Use systematic prioritization approaches
# Multi-criteria prioritization
/parallel-prioritization "Prioritize backlog using business value, user impact, technical risk, and dependency analysis"
# Include stakeholder input
/parallel-prioritization "Stakeholder-aligned prioritization with clear rationale for all decisions"Solution: Focus on capacity-based planning with better grooming
# Capacity-focused planning
/po "Plan sprints with detailed team capacity analysis and velocity-based story selection"
# Ensure story readiness
/qa-framework "Validate all sprint stories meet Definition of Ready criteria"# Phased epic creation
/planning-epic "Create Phase 1 epics for immediate development"
/planning-epic "Create Phase 2 epics for future sprints"
/planning-stories "Generate stories for Phase 1 epics only"# Modular backlog management
/parallel-prioritization "Prioritize by feature area or epic theme"
/qa-framework "Validate story readiness by epic or sprint"- Keep 2+ sprints of "Ready" stories ahead of development
- Regularly groom and refine backlog items
- Remove or archive outdated backlog items
- Prioritize based on business and user value
- Ensure every story connects to business objectives
- Measure and track value delivery
- Create appropriately sized stories for sprint completion
- Provide clear acceptance criteria and requirements
- Remove blockers and dependencies proactively
- Regularly update stakeholders on backlog status
- Incorporate feedback into backlog prioritization
- Maintain transparency in decision-making
- Learn from sprint outcomes and adjust planning
- Refine estimation and velocity tracking
- Evolve Definition of Ready and Done criteria
- Ensure all stories meet Definition of Ready before sprint planning
- Create comprehensive acceptance criteria
- Maintain traceability from PRD to stories
- Product Manager Guide - PRD source and collaboration partner
- Scrum Master Guide - Sprint execution partner
- QA Engineer Guide - Acceptance criteria validation partner
- Backlog Templates - Standardized backlog formats
- Agile Frameworks - Agile methodology tools
/planning-epic "Create epics with value stream analysis and user journey mapping"/planning-stories "Generate user stories using story mapping methodology with user journey focus"/parallel-prioritization "Prioritize backlog based on desired business outcomes and impact metrics"/parallel-prioritization "Prioritize backlog with technical risk assessment and dependency analysis"- Sprint Success Rate: 94% of sprints with PO-managed backlogs achieve their goals
- Development Efficiency: 76% faster development with well-groomed stories
- Stakeholder Satisfaction: 89% satisfaction with backlog prioritization and communication
- Quality Improvement: 68% fewer defects with comprehensive acceptance criteria
- Created backlogs that eliminated scope creep and requirement ambiguity
- Established sprint planning processes that improved team velocity by 45%
- Developed story grooming practices that reduced development questions by 60%
- Implemented prioritization frameworks that increased delivered business value by 35%
The Product Owner agent is your backlog management and sprint planning expert. Use it to convert PRDs into actionable development backlogs that enable efficient, value-driven development. Remember: Great products are built from well-managed backlogs with clear, ready stories.