BMAD-METHOD/docs/templates/po-checklist.md

Product Owner (PO) Validation Checklist

This checklist serves as a comprehensive framework for the Product Owner to validate the complete MVP plan before development execution. The PO should systematically work through each item, documenting compliance status and noting any deficiencies.

1. PROJECT SETUP & INITIALIZATION

1.1 Project Scaffolding

• Epic 1 includes explicit steps for project creation/initialization
• If using a starter template, steps for cloning/setup are included
• If building from scratch, all necessary scaffolding steps are defined
• Initial README or documentation setup is included
• Repository setup and initial commit processes are defined (if applicable)

1.2 Development Environment

• Local development environment setup is clearly defined
• Required tools and versions are specified (Node.js, Python, etc.)
• Steps for installing dependencies are included
• Configuration files (dotenv, config files, etc.) are addressed
• Development server setup is included

1.3 Core Dependencies

• All critical packages/libraries are installed early in the process
• Package management (npm, pip, etc.) is properly addressed
• Version specifications are appropriately defined
• Dependency conflicts or special requirements are noted

2. INFRASTRUCTURE & DEPLOYMENT SEQUENCING

2.1 Database & Data Store Setup

• Database selection/setup occurs before any database operations
• Schema definitions are created before data operations
• Migration strategies are defined if applicable
• Seed data or initial data setup is included if needed
• Database access patterns and security are established early

2.2 API & Service Configuration

• API frameworks are set up before implementing endpoints
• Service architecture is established before implementing services
• Authentication framework is set up before protected routes
• Middleware and common utilities are created before use

2.3 Deployment Pipeline

• CI/CD pipeline is established before any deployment actions
• Infrastructure as Code (IaC) is set up before use
• Environment configurations (dev, staging, prod) are defined early
• Deployment strategies are defined before implementation
• Rollback procedures or considerations are addressed

2.4 Testing Infrastructure

• Testing frameworks are installed before writing tests
• Test environment setup precedes test implementation
• Mock services or data are defined before testing
• Test utilities or helpers are created before use

3. EXTERNAL DEPENDENCIES & INTEGRATIONS

3.1 Third-Party Services

• Account creation steps are identified for required services
• API key acquisition processes are defined
• Steps for securely storing credentials are included
• Fallback or offline development options are considered

3.2 External APIs

• Integration points with external APIs are clearly identified
• Authentication with external services is properly sequenced
• API limits or constraints are acknowledged
• Backup strategies for API failures are considered

3.3 Infrastructure Services

• Cloud resource provisioning is properly sequenced
• DNS or domain registration needs are identified
• Email or messaging service setup is included if needed
• CDN or static asset hosting setup precedes their use

4. USER/AGENT RESPONSIBILITY DELINEATION

4.1 User Actions

• User responsibilities are limited to only what requires human intervention
• Account creation on external services is properly assigned to users
• Purchasing or payment actions are correctly assigned to users
• Credential provision is appropriately assigned to users

4.2 Developer Agent Actions

• All code-related tasks are assigned to developer agents
• Automated processes are correctly identified as agent responsibilities
• Configuration management is properly assigned
• Testing and validation are assigned to appropriate agents

5. FEATURE SEQUENCING & DEPENDENCIES

5.1 Functional Dependencies

• Features that depend on other features are sequenced correctly
• Shared components are built before their use
• User flows follow a logical progression
• Authentication features precede protected routes/features

5.2 Technical Dependencies

• Lower-level services are built before higher-level ones
• Libraries and utilities are created before their use
• Data models are defined before operations on them
• API endpoints are defined before client consumption

5.3 Cross-Epic Dependencies

• Later epics build upon functionality from earlier epics
• No epic requires functionality from later epics
• Infrastructure established in early epics is utilized consistently
• Incremental value delivery is maintained

6. MVP SCOPE ALIGNMENT

6.1 PRD Goals Alignment

• All core goals defined in the PRD are addressed in epics/stories
• Features directly support the defined MVP goals
• No extraneous features beyond MVP scope are included
• Critical features are prioritized appropriately

6.2 User Journey Completeness

• All critical user journeys are fully implemented
• Edge cases and error scenarios are addressed
• User experience considerations are included
• Accessibility requirements are incorporated if specified

6.3 Technical Requirements Satisfaction

• All technical constraints from the PRD are addressed
• Non-functional requirements are incorporated
• Architecture decisions align with specified constraints
• Performance considerations are appropriately addressed

7. RISK MANAGEMENT & PRACTICALITY

7.1 Technical Risk Mitigation

• Complex or unfamiliar technologies have appropriate learning/prototyping stories
• High-risk components have explicit validation steps
• Fallback strategies exist for risky integrations
• Performance concerns have explicit testing/validation

7.2 External Dependency Risks

• Risks with third-party services are acknowledged and mitigated
• API limits or constraints are addressed
• Backup strategies exist for critical external services
• Cost implications of external services are considered

7.3 Timeline Practicality

• Story complexity and sequencing suggest a realistic timeline
• Dependencies on external factors are minimized or managed
• Parallel work is enabled where possible
• Critical path is identified and optimized

8. DOCUMENTATION & HANDOFF

8.1 Developer Documentation

• API documentation is created alongside implementation
• Setup instructions are comprehensive
• Architecture decisions are documented
• Patterns and conventions are documented

8.2 User Documentation

• User guides or help documentation is included if required
• Error messages and user feedback are considered
• Onboarding flows are fully specified
• Support processes are defined if applicable

9. POST-MVP CONSIDERATIONS

9.1 Future Enhancements

• Clear separation between MVP and future features
• Architecture supports planned future enhancements
• Technical debt considerations are documented
• Extensibility points are identified

9.2 Feedback Mechanisms

• Analytics or usage tracking is included if required
• User feedback collection is considered
• Monitoring and alerting are addressed
• Performance measurement is incorporated

VALIDATION SUMMARY

Category Statuses

Category	Status	Critical Issues
1. Project Setup & Initialization	PASS/FAIL/PARTIAL
2. Infrastructure & Deployment Sequencing	PASS/FAIL/PARTIAL
3. External Dependencies & Integrations	PASS/FAIL/PARTIAL
4. User/Agent Responsibility Delineation	PASS/FAIL/PARTIAL
5. Feature Sequencing & Dependencies	PASS/FAIL/PARTIAL
6. MVP Scope Alignment	PASS/FAIL/PARTIAL
7. Risk Management & Practicality	PASS/FAIL/PARTIAL
8. Documentation & Handoff	PASS/FAIL/PARTIAL
9. Post-MVP Considerations	PASS/FAIL/PARTIAL

Critical Deficiencies

• List all critical issues that must be addressed before approval

Recommendations

• Provide specific recommendations for addressing each deficiency

Final Decision

• APPROVED: The plan is comprehensive, properly sequenced, and ready for implementation.
• REJECTED: The plan requires revision to address the identified deficiencies.