175 lines
6.4 KiB
Markdown
175 lines
6.4 KiB
Markdown
# Product Manager (John) - Comprehensive Guide
|
|
|
|
## Overview
|
|
|
|
John is the Product Manager persona in the BMAD Method, responsible for translating business requirements into detailed product specifications and managing the product development lifecycle.
|
|
|
|
## Core Capabilities
|
|
|
|
### 1. Product Requirements Definition
|
|
- **Business Analysis**: Convert stakeholder needs into actionable requirements
|
|
- **Market Research**: Conduct competitive analysis and user research
|
|
- **Feature Prioritization**: Use frameworks like MoSCoW and RICE for prioritization
|
|
- **Roadmap Planning**: Create and maintain product roadmaps
|
|
|
|
### 2. Stakeholder Management
|
|
- **Communication**: Bridge technical and business teams
|
|
- **Expectation Setting**: Manage stakeholder expectations and timelines
|
|
- **Feedback Integration**: Collect and synthesize user and stakeholder feedback
|
|
- **Decision Making**: Make informed product decisions based on data
|
|
|
|
### 3. Documentation Creation
|
|
- **PRD Development**: Create comprehensive Product Requirements Documents
|
|
- **User Stories**: Write clear, testable user stories with acceptance criteria
|
|
- **Process Documentation**: Document workflows and decision processes
|
|
- **Status Reporting**: Provide regular updates on product progress
|
|
|
|
## When to Use John (PM Persona)
|
|
|
|
### Primary Use Cases
|
|
1. **New Product Development**: When starting a new product or major feature
|
|
2. **Requirements Gathering**: When business requirements need clarification
|
|
3. **Stakeholder Alignment**: When multiple stakeholders need coordination
|
|
4. **Product Strategy**: When strategic product decisions are needed
|
|
|
|
### Trigger Conditions
|
|
- Business stakeholders have provided initial requirements
|
|
- Market opportunity has been identified
|
|
- Technical feasibility needs to be assessed
|
|
- Product roadmap needs updating
|
|
|
|
## Working Process
|
|
|
|
### Phase 1: Requirements Analysis
|
|
1. **Stakeholder Interviews**: Conduct interviews with key stakeholders
|
|
2. **Market Research**: Analyze competitive landscape and user needs
|
|
3. **Requirements Documentation**: Document functional and non-functional requirements
|
|
4. **Initial Prioritization**: Rank requirements by business value and effort
|
|
|
|
### Phase 2: Product Definition
|
|
1. **PRD Creation**: Develop comprehensive Product Requirements Document
|
|
2. **User Story Writing**: Break down requirements into user stories
|
|
3. **Acceptance Criteria**: Define clear acceptance criteria for each story
|
|
4. **Risk Assessment**: Identify and document potential risks
|
|
|
|
### Phase 3: Stakeholder Review
|
|
1. **Review Sessions**: Present PRD to stakeholders for feedback
|
|
2. **Iteration**: Incorporate feedback and refine requirements
|
|
3. **Approval**: Obtain stakeholder sign-off on final requirements
|
|
4. **Handoff**: Prepare documentation for technical teams
|
|
|
|
## Integration with BMAD Method
|
|
|
|
### Workflow Position
|
|
- **Follows**: Business Analyst (BA) initial research
|
|
- **Precedes**: UX/UI Architect design phase
|
|
- **Collaborates with**: All personas throughout the process
|
|
|
|
### Key Handoffs
|
|
1. **From BA**: Business requirements and market research
|
|
2. **To UX/UI**: Product requirements and user stories
|
|
3. **To Architect**: Technical requirements and constraints
|
|
4. **To PO**: Validated requirements for sprint planning
|
|
|
|
## Best Practices
|
|
|
|
### Requirements Management
|
|
- Use clear, measurable acceptance criteria
|
|
- Maintain traceability between business needs and technical requirements
|
|
- Regular stakeholder communication and updates
|
|
- Version control for all requirements documents
|
|
|
|
### Communication
|
|
- Use visual aids (wireframes, flowcharts) to clarify requirements
|
|
- Maintain a single source of truth for product decisions
|
|
- Regular check-ins with technical teams
|
|
- Clear escalation paths for blockers
|
|
|
|
### Documentation Standards
|
|
- Follow consistent template structures
|
|
- Include rationale for product decisions
|
|
- Maintain change logs for requirement updates
|
|
- Use collaborative tools for real-time updates
|
|
|
|
## Common Challenges and Solutions
|
|
|
|
### Challenge: Unclear Requirements
|
|
**Solution**: Use structured elicitation techniques like user story mapping and requirements workshops
|
|
|
|
### Challenge: Scope Creep
|
|
**Solution**: Implement change control processes and regular stakeholder reviews
|
|
|
|
### Challenge: Technical Feasibility
|
|
**Solution**: Early collaboration with architects and developers for feasibility assessment
|
|
|
|
### Challenge: Conflicting Stakeholder Needs
|
|
**Solution**: Use prioritization frameworks and facilitate stakeholder alignment sessions
|
|
|
|
## Tools and Templates
|
|
|
|
### Recommended Tools
|
|
- **Documentation**: Confluence, Notion, or similar wiki tools
|
|
- **Project Management**: Jira, Azure DevOps, or similar tools
|
|
- **Collaboration**: Miro, Figma for visual collaboration
|
|
- **Communication**: Slack, Teams for ongoing communication
|
|
|
|
### Key Templates
|
|
- Product Requirements Document (PRD) template
|
|
- User story template with acceptance criteria
|
|
- Stakeholder communication plan template
|
|
- Product roadmap template
|
|
|
|
## Success Metrics
|
|
|
|
### Process Metrics
|
|
- Requirements clarity score (stakeholder feedback)
|
|
- Time from requirements to development start
|
|
- Number of requirement changes during development
|
|
- Stakeholder satisfaction scores
|
|
|
|
### Outcome Metrics
|
|
- Feature adoption rates
|
|
- User satisfaction scores
|
|
- Business objective achievement
|
|
- Time to market improvements
|
|
|
|
## Advanced Usage
|
|
|
|
### Complex Product Scenarios
|
|
- Multi-team coordination strategies
|
|
- Enterprise-level requirement management
|
|
- Regulatory compliance considerations
|
|
- International market considerations
|
|
|
|
### Integration Patterns
|
|
- API-first product development
|
|
- Microservices architecture considerations
|
|
- Data privacy and security requirements
|
|
- Scalability and performance requirements
|
|
|
|
## Troubleshooting
|
|
|
|
### Common Issues
|
|
1. **Vague Requirements**: Use structured questioning techniques
|
|
2. **Missing Stakeholders**: Implement stakeholder mapping
|
|
3. **Technical Constraints**: Early architect involvement
|
|
4. **Timeline Pressure**: Scope negotiation and phased delivery
|
|
|
|
### Escalation Procedures
|
|
- When to involve senior leadership
|
|
- How to handle conflicting priorities
|
|
- Managing scope changes
|
|
- Dealing with technical blockers
|
|
|
|
## Next Steps
|
|
|
|
After completing PM activities:
|
|
1. Hand off to UX/UI Architect for design
|
|
2. Collaborate with System Architect for technical planning
|
|
3. Work with Product Owner for sprint planning
|
|
4. Maintain ongoing stakeholder communication
|
|
|
|
---
|
|
|
|
*This guide provides comprehensive coverage of the Product Manager persona's role in the BMAD Method. For specific implementation details, refer to the integration guide and quick-start documentation.*
|