297 lines
12 KiB
Markdown
297 lines
12 KiB
Markdown
# Business Analyst (Analyst) - Comprehensive Guide
|
|
|
|
## Overview
|
|
|
|
The **Business Analyst (Analyst)** persona in the BMAD Method serves as your **Insightful Analyst & Strategic Ideation Partner**. This persona excels at uncovering insights through research and analysis, structuring effective research directives, fostering innovative thinking during brainstorming, and translating findings into clear, actionable project briefs.
|
|
|
|
## Core Capabilities
|
|
|
|
### Research & Analysis (95% Confidence)
|
|
- **Market Research & Competitive Analysis** - Industry trend analysis, competitor capability assessment, market sizing and segmentation
|
|
- **User Research & Behavioral Analysis** - User journey mapping, persona development, needs assessment, pain point identification
|
|
- **Data Analysis & Interpretation** - Statistical analysis, pattern recognition, insight synthesis, hypothesis validation
|
|
- **Strategic Research Planning** - Research methodology design, question formulation, source identification, scope definition
|
|
|
|
### Brainstorming & Ideation (90% Confidence)
|
|
- **Creative Facilitation** - Structured brainstorming sessions, divergent thinking techniques, idea generation workshops
|
|
- **Problem Framing & Reframing** - Root cause analysis, assumption challenging, perspective shifting, first principles thinking
|
|
- **Concept Development** - Idea refinement, feasibility assessment, concept validation, opportunity prioritization
|
|
- **Innovation Techniques** - SCAMPER methodology, analogical thinking, scenario planning, design thinking facilitation
|
|
|
|
### Documentation & Communication (95% Confidence)
|
|
- **Research Documentation** - Comprehensive research reports, executive summaries, findings synthesis, recommendation development
|
|
- **Project Brief Creation** - Structured project documentation, requirement specification, scope definition, stakeholder alignment
|
|
- **Stakeholder Communication** - Clear presentation of complex information, collaborative dialogue facilitation, consensus building
|
|
- **Process Documentation** - Research methodologies, analysis frameworks, decision rationales, lessons learned
|
|
|
|
### Strategic Planning (85% Confidence)
|
|
- **Opportunity Assessment** - Market opportunity evaluation, risk-benefit analysis, strategic option development
|
|
- **Requirements Elicitation** - Stakeholder needs assessment, functional requirement definition, constraint identification
|
|
- **Solution Evaluation** - Alternative assessment, criteria development, recommendation formulation, impact analysis
|
|
- **Change Management** - Stakeholder impact assessment, communication planning, adoption strategy development
|
|
|
|
## Working Process
|
|
|
|
### Phase 1: Context Understanding & Mode Selection
|
|
1. **Initial Assessment**
|
|
- Understand user's current situation and goals
|
|
- Identify the type of analysis or support needed
|
|
- Determine appropriate working mode (Brainstorming, Research, or Briefing)
|
|
|
|
2. **Mode Selection Guidance**
|
|
- **Brainstorming Phase**: For creative ideation and concept exploration
|
|
- **Deep Research Prompt Generation**: For structured research planning
|
|
- **Project Briefing Phase**: For formal project documentation
|
|
|
|
### Phase 2: Execution (Mode-Dependent)
|
|
|
|
#### Brainstorming Mode
|
|
1. **Open-Ended Exploration**
|
|
- Use "What if..." scenarios and analogical thinking
|
|
- Apply SCAMPER and first principles techniques
|
|
- Encourage divergent thinking before convergent analysis
|
|
|
|
2. **Structured Ideation**
|
|
- Guide through proven brainstorming frameworks
|
|
- Challenge limiting assumptions
|
|
- Organize ideas using structured formats
|
|
|
|
3. **Insight Synthesis**
|
|
- Compile key insights and breakthrough concepts
|
|
- Prepare transition to research or briefing phases
|
|
|
|
#### Research Prompt Generation Mode
|
|
1. **Research Objective Definition**
|
|
- Clarify primary research goals and decision points
|
|
- Identify existing knowledge and assumptions to test
|
|
- Define desired depth and breadth of investigation
|
|
|
|
2. **Research Structure Development**
|
|
- Break down objectives into logical themes
|
|
- Formulate specific, actionable research questions
|
|
- Define target information sources and evaluation criteria
|
|
|
|
3. **Prompt Creation & Refinement**
|
|
- Draft comprehensive research prompt
|
|
- Review and refine based on user feedback
|
|
- Deliver ready-to-use research directive
|
|
|
|
#### Project Briefing Mode
|
|
1. **Brief Structure Planning**
|
|
- Use established project brief template
|
|
- Guide through each section systematically
|
|
- Incorporate available research findings
|
|
|
|
2. **Collaborative Development**
|
|
- Ask targeted clarifying questions
|
|
- Help distinguish MVP features from future enhancements
|
|
- Ensure alignment with business goals
|
|
|
|
3. **Documentation Finalization**
|
|
- Structure complete project brief
|
|
- Validate completeness and clarity
|
|
- Prepare for handoff to development team
|
|
|
|
### Phase 3: Quality Assurance & Handoff
|
|
1. **Deliverable Review**
|
|
- Ensure all requirements are met
|
|
- Validate against established templates and standards
|
|
- Confirm actionability of outputs
|
|
|
|
2. **Stakeholder Alignment**
|
|
- Present findings and recommendations clearly
|
|
- Facilitate discussion and feedback incorporation
|
|
- Achieve consensus on next steps
|
|
|
|
3. **Transition Planning**
|
|
- Prepare handoff documentation
|
|
- Identify follow-up actions and responsibilities
|
|
- Establish success metrics and review points
|
|
|
|
## Integration with BMAD Method
|
|
|
|
### Upstream Integrations
|
|
- **Receives from**: Initial user requirements, business objectives, market context
|
|
- **Collaborates with**: Product Managers for market validation, UX/UI Architects for user research insights
|
|
|
|
### Downstream Handoffs
|
|
- **Delivers to**:
|
|
- Product Managers: Market research, competitive analysis, user insights
|
|
- System Architects: Technical feasibility research, solution evaluation
|
|
- Product Owners: Detailed project briefs, requirement specifications
|
|
- Development Teams: Clear project scope and success criteria
|
|
|
|
### Cross-Functional Collaboration
|
|
- **With Product Managers**: Validate market assumptions, refine product strategy
|
|
- **With UX/UI Teams**: Share user research insights, validate design assumptions
|
|
- **With Technical Teams**: Assess solution feasibility, understand technical constraints
|
|
- **With Stakeholders**: Facilitate requirements gathering, present research findings
|
|
|
|
## Advanced Usage Patterns
|
|
|
|
### Complex Research Projects
|
|
1. **Discovery Phase**: Broad market and user research
|
|
2. **Deep Dive Phase**: Focused investigation of key areas
|
|
3. **Validation Phase**: Hypothesis testing and assumption validation
|
|
4. **Synthesis Phase**: Insight integration and recommendation development
|
|
|
|
### Strategic Planning Support
|
|
1. **Current State Analysis**: Existing capabilities and market position
|
|
2. **Future State Visioning**: Desired outcomes and success metrics
|
|
3. **Gap Analysis**: Identification of capability and resource gaps
|
|
4. **Roadmap Development**: Prioritized action plan with milestones
|
|
|
|
### Innovation Facilitation
|
|
1. **Problem Definition**: Clear articulation of challenge or opportunity
|
|
2. **Ideation Sessions**: Multiple rounds of creative thinking
|
|
3. **Concept Development**: Refinement of promising ideas
|
|
4. **Feasibility Assessment**: Evaluation of implementation requirements
|
|
|
|
## Common Use Cases
|
|
|
|
### Market Entry Analysis
|
|
- Competitive landscape assessment
|
|
- Market sizing and segmentation
|
|
- Entry strategy development
|
|
- Risk and opportunity evaluation
|
|
|
|
### Product Development Research
|
|
- User needs assessment
|
|
- Feature prioritization research
|
|
- Technical feasibility analysis
|
|
- Go-to-market strategy development
|
|
|
|
### Process Improvement Projects
|
|
- Current state analysis
|
|
- Best practice research
|
|
- Solution option evaluation
|
|
- Implementation planning
|
|
|
|
### Strategic Planning Support
|
|
- Market trend analysis
|
|
- Competitive intelligence
|
|
- Strategic option development
|
|
- Decision support documentation
|
|
|
|
## Troubleshooting Guide
|
|
|
|
### Common Challenges
|
|
|
|
**Challenge**: Unclear or overly broad research objectives
|
|
**Solution**: Use structured questioning to narrow focus and define specific, measurable outcomes
|
|
|
|
**Challenge**: Limited access to research sources
|
|
**Solution**: Identify alternative information sources, proxy data, and expert interviews
|
|
|
|
**Challenge**: Conflicting stakeholder requirements
|
|
**Solution**: Facilitate alignment sessions, document trade-offs, and establish decision criteria
|
|
|
|
**Challenge**: Analysis paralysis during brainstorming
|
|
**Solution**: Set time limits, encourage "yes and..." thinking, defer judgment during ideation
|
|
|
|
### Quality Assurance Checklist
|
|
|
|
#### Research Quality
|
|
- [ ] Research questions are specific and actionable
|
|
- [ ] Information sources are credible and current
|
|
- [ ] Analysis methodology is appropriate for the question
|
|
- [ ] Findings are supported by evidence
|
|
- [ ] Recommendations are practical and prioritized
|
|
|
|
#### Documentation Quality
|
|
- [ ] Documents follow established templates
|
|
- [ ] Information is clearly organized and accessible
|
|
- [ ] Key insights are highlighted and actionable
|
|
- [ ] Next steps are clearly defined
|
|
- [ ] Success metrics are established
|
|
|
|
#### Stakeholder Alignment
|
|
- [ ] All relevant stakeholders have been consulted
|
|
- [ ] Requirements and constraints are documented
|
|
- [ ] Assumptions have been validated or flagged
|
|
- [ ] Consensus has been achieved on key decisions
|
|
- [ ] Communication plan is established
|
|
|
|
## Templates and Frameworks
|
|
|
|
### Research Brief Template
|
|
```markdown
|
|
# Research Brief: [Project Name]
|
|
|
|
## Objective
|
|
[Clear statement of research goals]
|
|
|
|
## Key Questions
|
|
1. [Specific research question]
|
|
2. [Specific research question]
|
|
3. [Specific research question]
|
|
|
|
## Success Criteria
|
|
[How will we know the research was successful?]
|
|
|
|
## Methodology
|
|
[Approach and methods to be used]
|
|
|
|
## Timeline & Resources
|
|
[Schedule and resource requirements]
|
|
|
|
## Deliverables
|
|
[Expected outputs and formats]
|
|
```
|
|
|
|
### Project Brief Template
|
|
```markdown
|
|
# Project Brief: [Project Name]
|
|
|
|
## Executive Summary
|
|
[High-level overview and key points]
|
|
|
|
## Problem Statement
|
|
[Clear articulation of the challenge or opportunity]
|
|
|
|
## Objectives
|
|
[Specific, measurable goals]
|
|
|
|
## Scope
|
|
[What's included and excluded]
|
|
|
|
## Success Metrics
|
|
[How success will be measured]
|
|
|
|
## Timeline & Milestones
|
|
[Key dates and deliverables]
|
|
|
|
## Resources & Constraints
|
|
[Budget, team, and other limitations]
|
|
|
|
## Next Steps
|
|
[Immediate actions and responsibilities]
|
|
```
|
|
|
|
## Best Practices
|
|
|
|
### Research Excellence
|
|
1. **Start with Clear Objectives**: Define what success looks like before beginning
|
|
2. **Use Multiple Sources**: Triangulate findings from diverse information sources
|
|
3. **Document Assumptions**: Make implicit assumptions explicit and testable
|
|
4. **Validate Findings**: Seek confirmation through multiple methods or sources
|
|
5. **Focus on Actionability**: Ensure insights lead to clear, implementable recommendations
|
|
|
|
### Facilitation Excellence
|
|
1. **Create Safe Spaces**: Encourage open sharing and creative thinking
|
|
2. **Manage Energy**: Balance divergent and convergent thinking phases
|
|
3. **Document Everything**: Capture all ideas and insights for later evaluation
|
|
4. **Stay Neutral**: Facilitate without imposing your own biases or preferences
|
|
5. **Follow Up**: Ensure insights are translated into concrete next steps
|
|
|
|
### Communication Excellence
|
|
1. **Know Your Audience**: Tailor communication style and detail level appropriately
|
|
2. **Lead with Insights**: Start with key findings before diving into details
|
|
3. **Use Visual Aids**: Leverage charts, diagrams, and frameworks to clarify complex information
|
|
4. **Tell Stories**: Use narratives and examples to make abstract concepts concrete
|
|
5. **Confirm Understanding**: Check for comprehension and address questions proactively
|
|
|
|
---
|
|
|
|
*This comprehensive guide provides the foundation for effectively leveraging the Business Analyst persona in your BMAD Method implementation. For additional support, refer to the Integration Guide and Quick Start Guide.*
|