# Product Owner Master Checklist

This comprehensive checklist validates project artifacts, backlog management, and process adherence from a Product Owner perspective. Used to ensure quality and completeness across all product management activities.

## Required Documents
- Current PRD or requirements document
- Epic and story files
- Sprint planning documents
- Backlog priority documentation
- Definition of Ready and Done criteria

## LLM Instructions
Execute this checklist to validate product management artifacts and processes. Focus on quality, completeness, consistency, and alignment with business objectives.

## Section 1: Backlog Management and Prioritization

**LLM Prompt:** "Evaluate the current state of backlog management, priority alignment, and epic/story organization to ensure optimal value delivery."

### Backlog Structure and Organization
- [ ] **Product backlog properly organized**
  - Evidence: Epics and stories are logically grouped
  - Hierarchy: Clear epic-story-task relationships maintained
  
- [ ] **Priorities clearly defined and justified**  
  - Evidence: Priority rationale documented for each epic/story
  - Business value: High-value items prioritized appropriately
  
- [ ] **Epic roadmap alignment verified**
  - Evidence: Epics align with product roadmap and business objectives
  - Dependencies: Epic dependencies identified and managed
  
- [ ] **Story sizing consistency maintained**
  - Evidence: Story points applied consistently across backlog
  - Velocity: Story sizes support predictable sprint planning

### Value Delivery Focus
- [ ] **User value clearly articulated**
  - Evidence: Each story has clear user value proposition
  - Outcome focus: Stories focus on outcomes, not just outputs
  
- [ ] **MVP scope well-defined**
  - Evidence: Clear distinction between MVP and future features
  - Scope management: Feature creep prevented through clear boundaries

**Section 1 Pass Criteria:** Backlog must be well-organized with clear priorities and value alignment.

## Section 2: Requirements Quality and Completeness

**LLM Prompt:** "Assess the quality and completeness of requirements documentation to ensure development teams have clear guidance."

### Requirements Documentation Quality
- [ ] **Acceptance criteria are complete and testable**
  - Evidence: All stories have GIVEN-WHEN-THEN criteria where appropriate
  - Testability: Criteria can be objectively verified
  
- [ ] **Business rules clearly documented**
  - Evidence: Complex business logic is well-specified
  - Completeness: Edge cases and exceptions handled
  
- [ ] **User personas and scenarios defined**
  - Evidence: Clear understanding of target users and use cases
  - Context: User journey and context properly documented
  
- [ ] **Non-functional requirements specified**
  - Evidence: Performance, security, accessibility requirements included
  - Standards: Compliance and regulatory requirements addressed

### Requirements Traceability
- [ ] **Requirements traced to business objectives**
  - Evidence: Clear link between features and business goals
  - ROI: Return on investment considerations documented
  
- [ ] **Change impact analysis documented**
  - Evidence: Impact of requirement changes properly assessed
  - Communication: Stakeholder communication for changes maintained

**Section 2 Pass Criteria:** Requirements must be complete, testable, and traceable to business value.

## Section 3: Sprint Planning and Execution Oversight

**LLM Prompt:** "Evaluate sprint planning effectiveness and execution oversight to ensure consistent value delivery."

### Sprint Planning Quality
- [ ] **Sprint goals clearly defined**
  - Evidence: Each sprint has specific, measurable objectives
  - Alignment: Sprint goals align with epic and product objectives
  
- [ ] **Story readiness validated**
  - Evidence: Stories meet Definition of Ready before sprint inclusion
  - Dependencies: All story dependencies resolved or managed
  
- [ ] **Team capacity and velocity considered**
  - Evidence: Sprint commitment matches team capacity
  - Sustainability: Workload is sustainable for team health
  
- [ ] **Risk assessment completed**
  - Evidence: Sprint risks identified and mitigation planned
  - Contingency: Backup plans for high-risk items

### Execution Monitoring
- [ ] **Progress tracking mechanisms in place**
  - Evidence: Clear metrics for tracking sprint progress
  - Visibility: Progress visible to all stakeholders
  
- [ ] **Impediment identification and resolution**
  - Evidence: Process for identifying and addressing blockers
  - Escalation: Clear escalation paths for impediment resolution

**Section 3 Pass Criteria:** Sprint planning must be thorough with clear goals and realistic commitments.

## Section 4: Stakeholder Communication and Alignment

**LLM Prompt:** "Assess stakeholder communication effectiveness and alignment on product direction and priorities."

### Stakeholder Engagement
- [ ] **Key stakeholders identified and engaged**
  - Evidence: Stakeholder register maintained with engagement plan
  - Communication: Regular touchpoints scheduled and maintained
  
- [ ] **Product vision communicated clearly**
  - Evidence: Product vision is well-articulated and understood
  - Alignment: Team and stakeholders aligned on product direction
  
- [ ] **Feature requests managed effectively**
  - Evidence: Process for capturing and evaluating feature requests
  - Decision rationale: Clear criteria for feature inclusion/exclusion
  
- [ ] **Customer feedback integrated**
  - Evidence: Customer feedback regularly collected and analyzed
  - Action: Feedback influences product decisions and priorities

### Reporting and Transparency
- [ ] **Progress reporting to stakeholders**
  - Evidence: Regular status updates provided to stakeholders
  - Metrics: Relevant metrics tracked and communicated
  
- [ ] **Decision documentation maintained**
  - Evidence: Product decisions documented with rationale
  - Accountability: Decision history available for reference

**Section 4 Pass Criteria:** Stakeholder communication must be clear, regular, and effective.

## Section 5: Process Adherence and Continuous Improvement

**LLM Prompt:** "Evaluate adherence to defined processes and identify opportunities for continuous improvement."

### Process Compliance
- [ ] **Definition of Ready consistently applied**
  - Evidence: Stories meet DoR criteria before development
  - Quality gate: No stories enter development without meeting DoR
  
- [ ] **Definition of Done validated**
  - Evidence: DoD criteria applied consistently across all deliverables
  - Quality assurance: Quality gates enforced throughout development
  
- [ ] **Change management process followed**
  - Evidence: Requirement changes follow defined change process
  - Impact assessment: Change impacts properly analyzed and communicated
  
- [ ] **Documentation standards maintained**
  - Evidence: All artifacts follow established templates and standards
  - Consistency: Documentation is consistent across the product

### Continuous Improvement
- [ ] **Retrospective insights captured and acted upon**
  - Evidence: Retrospective outcomes drive process improvements
  - Action plans: Improvement actions tracked and implemented
  
- [ ] **Metrics and KPIs tracked**
  - Evidence: Product and process metrics regularly reviewed
  - Decision making: Data drives product decisions and improvements

**Section 5 Pass Criteria:** Processes must be consistently followed with evidence of continuous improvement.

## Final Assessment

### Overall Completion Status
**Pass Criteria:** All 5 sections must achieve 90% or higher pass rate.

### Product Owner Effectiveness Classification
- **Excellent:** All criteria met, strong product ownership
- **Good:** Minor issues, generally effective product management
- **Needs Improvement:** Several issues requiring attention
- **Inadequate:** Major problems requiring immediate action

### Summary Report Template
```
## Product Owner Master Checklist Results

**Assessment Date:** [Date]
**Assessed By:** Product Owner Agent

### Section Pass Rates
- Section 1 (Backlog Management): ___/6 items (___%)
- Section 2 (Requirements Quality): ___/6 items (___%)
- Section 3 (Sprint Planning): ___/6 items (___%)
- Section 4 (Stakeholder Communication): ___/6 items (___%)
- Section 5 (Process Adherence): ___/6 items (___%)

**Overall Status:** [EXCELLENT/GOOD/NEEDS IMPROVEMENT/INADEQUATE]

### Key Strengths
[List areas where product ownership is particularly strong]

### Areas for Improvement
[List items that did not pass with specific recommendations]

### Priority Actions
[Top 3 priority actions to improve product ownership effectiveness]

### Next Assessment
[Recommended timeframe for next assessment]
```

## Usage Notes
- This checklist should be executed regularly (suggested monthly or at major milestones)
- Can be used for self-assessment or external product ownership evaluation
- Results should drive product management process improvements
- Critical for maintaining high-quality product ownership practices