The Complete Business Analyst's Guide to BMAD-METHOD™: From Zero to Expert Project Planning in 30 Minutes
A step-by-step tutorial for Business Analysts to set up and master Mary, the AI Business Analyst that transforms chaotic project ideas into comprehensive, professional documentation
Prerequisites: Node.js v20+ (Download from nodejs.org)
Open your terminal and run:
npx bmad-method installThis command automatically:
- ✅ Detects if you have an existing installation
- ✅ Downloads the latest BMAD framework
- ✅ Sets up the AI agents and templates
- ✅ Creates the necessary project structure
📖 For detailed installation instructions, troubleshooting, and advanced setup options, see the official BMAD-METHOD™ repository.
You should see confirmation output like:
✓ BMAD-METHOD™ installed successfully
✓ AI agents configured
✓ Templates ready
✓ Ready to start planning!
BMAD works in multiple environments. Choose the one that fits your workflow:
Claude Code, Qwen CLI, or similar command-line AI tools:
/analystChatGPT, Claude Web, Gemini, or other browser-based AI:
- Upload the BMAD agent files or copy the analyst prompt
- Type: "Act as Mary, the BMAD Business Analyst"
Regardless of your environment, you'll see Mary's welcome message with 9 available commands. Bookmark this page - we'll walk through each command with real examples.
As a Business Analyst, you know the pain:
The 3 AM Panic: You're three weeks into development when the client asks, "Wait, where's the user authentication flow?" It was never documented.
The Requirements Shuffle: Your team interprets "user-friendly interface" five different ways, leading to five different implementations.
The Stakeholder Maze: The investor wants rapid deployment, the technical lead demands perfect architecture, and the marketing manager insists on features that don't exist yet.
BMAD-METHOD™ eliminates these scenarios by providing a structured, AI-guided process that ensures nothing gets missed, everything gets documented, and all stakeholders are aligned from day one.
When you type /analyst, you're not just getting another chatbot. You're accessing Mary, an AI Business Analyst trained on proven methodologies who guides you through structured discovery processes.
Here's exactly what you'll see when you start:
Hello, I'm Mary, your Business Analyst. Here are the commands I can help you with:
1. brainstorm {topic}: Facilitate structured brainstorming session.
2. create-competitor-analysis: Create a competitor analysis document.
3. create-project-brief: Create a project brief document.
4. doc-out: Output full document in progress to current destination file.
5. elicit: Run the advanced elicitation task.
6. perform-market-research: Create a market research document.
7. research-prompt {topic}: Create a deep research prompt.
8. yolo: Toggle Yolo Mode.
9. exit: Exit the Business Analyst persona.
How can I assist you today?
For Business Analysts, here's the typical workflow:
- Start with Command 3 (create-project-brief) for new projects
- Use Command 1 (brainstorm) to explore specific challenges
- Apply Command 7 (research-prompt) to generate research for external AI tools
- Finish with Command 5 (elicit) to validate and refine your documentation
Let's walk through each step with a real project example.
Type the command:
3
Mary responds with mode selection:
Understood. I will help you create a new project brief using the standard template.
This will create a new file at docs/brief.md.
First, please choose how you'd like to proceed:
1. Interactive Mode: We'll work through each section of the brief together,
and you can provide feedback and refinements at each step.
2. YOLO Mode: I'll generate a complete first draft of the entire project
brief for you to review at the end.
Please select an option by number.
For Business Analysts: Always choose Option 1 (Interactive Mode). This ensures comprehensive coverage and quality control.
Mary guides you through these sections systematically:
- Executive Summary - One-paragraph project essence
- Problem Statement - Quantified pain points with market context
- Proposed Solution - Your unique approach and differentiators
- Target Users - Detailed personas with specific needs
- Goals & Success Metrics - SMART objectives with measurable KPIs
- MVP Scope - Clear must-have vs. nice-to-have boundaries
- Post-MVP Vision - Long-term roadmap and expansion opportunities
- Technical Considerations - Architecture preferences and constraints
- Constraints & Assumptions - Budget, timeline, and resource limitations
- Risks & Open Questions - Proactive issue identification
- Appendices - Supporting research and stakeholder input
Here's the game-changer: For each section, Mary provides quality assurance options:
Project Brief Elicitation Actions
Choose a number (0-8) or 9 to proceed:
0. Expand section with more specific details
1. Validate against similar successful products
2. Stress test assumptions with edge cases
3. Explore alternative solution approaches
4. Analyze resource/constraint trade-offs
5. Generate risk mitigation strategies
6. Challenge scope from MVP minimalist view
7. Brainstorm creative feature possibilities
8. If only we had [resource/capability/time]...
9. Proceed to next section
Pro Tip: Don't rush through these. Use options 1, 2, and 5 for critical sections like Problem Statement and MVP Scope.
Here's what Mary produced for a TikTok trend analysis project:
Executive Summary
PromoCraft is a web platform that automatically detects trending styles and topics
on TikTok and converts them into ready-to-use prompts for AI image generation tools.
It solves the problem of creators and marketers struggling to keep up with the rapid
pace of visual trends, saving them time by providing a direct bridge between social
media trends and AI content creation. The initial target market is individual
content creators and small marketing agencies.
When reviewed using option 2 (stress test assumptions), Mary identified that the assumption "creators struggle with trend detection" needed validation through user research - a critical insight that prevented building the wrong solution.
When you need to explore unclear aspects of your project, use Mary's brainstorming:
Command:
*brainstorm timeline based on project brief
Mary's Response:
I can facilitate a brainstorming session to help you think through the timeline.
First, a few questions to set us up for success:
1. Besides the project brief itself, are there any other constraints or
parameters we should consider for the timeline?
2. Is our goal today a broad exploration of all possibilities, or a more
focused ideation on a specific timeline structure?
3. I can capture our session in a structured document for you to reference
later. Shall I do that? (Yes is the default)
Your Input Example:
1. should be delivered as an MVP with tiktok trend collector, gen image by
SeeDream 4.0, and a simple UI.
2. let focus first.
3. Yes.
Mary's Structured Output: Mary doesn't just collect ideas. She produces organized, actionable plans like this 5-phase breakdown:
# Brainstorming Session Results
### Phase 1: Backend Foundation & Core Logic
1. Research TikTok Data Source: Investigate and decide on the method for getting trend data
2. Research SeeDream API: Get API access and analyze documentation
3. Initial Setup: Initialize backend server and design database schema
### Phase 2: TikTok Trend Collector Implementation
1. Develop Data Collector: Implement script to pull raw data from TikTok
2. Develop Trend Logic: Write algorithm to process data and identify trends
3. Implement Data Storage: Create logic to save trends into database
4. Schedule Automation: Set up recurring job (cron job) to run collector
5. Create API Endpoint: Build backend endpoint (/api/trends) for UI
[Continues with Phases 3-5...]
This isn't random brainstorming - it's structured analysis that directly feeds into your development planning.
The Problem: As a BA, you often need deep research on topics you're unfamiliar with (APIs, technical feasibility, market analysis).
The Solution: Mary generates focused research prompts you can use with ChatGPT, Claude, or Perplexity.
Command:
*research-prompt TikTok trend collection
Mary's Complete Research Prompt (copy this directly into ChatGPT):
Deep Research Prompt: Technical Methods for TikTok Trend Collection
Research Objective
To identify, analyze, and recommend the most effective and reliable technical
method for collecting trend data from TikTok. The research must determine the
feasibility, cost, scalability, and limitations of each potential approach to
inform the core architecture of the "PromoCraft" MVP.
Background Context
The project requires building a "TikTok trend collector" as a core feature.
The viability and development timeline of this feature are critically dependent
on the technical method chosen for data acquisition.
Research Questions
Primary Questions (Must Answer)
1. Official TikTok API: Does TikTok provide a formal API for accessing data on
trends, videos, hashtags, and sounds? What are the access requirements, rate
limits, costs, and specific terms of service?
2. Third-Party Data Providers: Who are the leading third-party services that
provide TikTok data/analytics via an API? Provide a comparison based on pricing,
data freshness, breadth of data points, and limitations.
3. Web Scraping Feasibility: What are the current techniques for scraping TikTok?
What are the primary technical challenges and associated legal and ethical risks?
Expected Deliverables
- Executive Summary: A clear, data-backed recommendation for the single best data
collection method for the MVP
- Detailed Analysis: Official API Report, Third-Party Provider Comparison,
Scraping Feasibility Report
- Supporting Materials: List of all URLs for APIs, data providers, and key articles
Success Criteria
The research is considered successful if it delivers a clear, actionable
recommendation that enables the development team to immediately begin designing
and building the trend collector with a well-defined technical strategy.
Result: When used with ChatGPT, this prompt generated a comprehensive 118-line research document with executive summary, comparison tables, decision matrix, and implementation timeline - exactly what you need for technical planning.
The Problem: Your project brief looks complete, but you suspect there might be gaps or issues you haven't considered.
The Solution: Mary's elicitation mode provides systematic quality assurance.
Command:
*elicit
Mary's Analysis Options:
Advanced Elicitation Options
Choose a number (0-8) or 9 to proceed:
0. Critique and Refine
1. Identify Potential Risks
2. Assess Alignment with Goals
3. Expand or Contract for Audience
4. Agile Team Perspective Shift
5. Stakeholder Round Table
6. Hindsight is 20/20: The 'If Only...' Reflection
7. Red Team vs Blue Team
8. Tree of Thoughts Deep Dive
9. Proceed / No Further Actions
Example: Stakeholder Round Table (Option 5)
Mary simulates different stakeholder perspectives:
Simulated Stakeholder Round Table
1. Victoria, the Investor:
"The phased timeline is an improvement, but what's the total estimated
time-to-market in weeks? The constraint to 'minimize reliance on paid APIs'
is wise, but what is the actual monthly budget we're allocating for
'cost-effective third-party providers'? We need to put a number on that."
2. Alex, the Technical Lead:
"The plan's biggest vulnerability is the approval time for the official TikTok
APIs. If that takes weeks, Phase 2 is dead in the water. We need to de-risk
this by building against a third-party provider first, in parallel with the
official application."
3. David, the Marketing Manager:
"This brief is technically sound, but who are we marketing the MVP to on day one?
The success metrics are good, but they're meaningless without an acquisition plan.
How will we get our first 100 users? A Product Hunt launch? Targeting specific
creator communities?"
Actionable Insights:
1. De-risk the Timeline: Development should begin using third-party API immediately
2. Add a Budget: Specific monthly budget for third-party APIs needed
3. Define Go-To-Market: New section needed for user acquisition strategy
Result: Mary identified three critical gaps that would have caused major issues during development and launch.
After completing all analysis, use Mary's export command:
*doc-out
Mary automatically updates your project brief with all improvements and creates a comprehensive brief.md file with:
- Professional formatting ready for stakeholder review
- Complete 11-section documentation covering every project aspect
- Research references and supporting materials
- Clear next steps for development team handoff
- Traditional planning: 15-20 hours across multiple meetings and revisions
- BMAD planning: 3-4 hours for comprehensive documentation
- Savings: 75% reduction in planning time
- Requirements completeness: 95% vs. 60% traditional methods
- Stakeholder alignment: Issues identified during planning vs. mid-development
- Risk mitigation: Proactive identification vs. reactive problem-solving
- Client confidence: Professional documentation impresses stakeholders
- Team efficiency: Clear requirements reduce development questions by 70%
- Project success: Higher completion rates with fewer scope changes
Week 1: Install BMAD and complete your first project brief
Week 2: Use research prompts to enhance one technical decision
Week 3: Apply elicitation to validate an existing project
Week 4: Train a colleague and compare results with traditional methods
Solution: Provide more specific information upfront. Paste existing documentation, user stories, or stakeholder feedback into your initial conversation.
Solution: Focus on quality over speed. Each section builds on the previous one. Use Mary's elicitation options liberally - they catch issues early.
Solution: This is actually a success! BMAD revealed alignment issues before development started. Use Mary's elicitation mode to address their concerns systematically.
Solution: The brief.md output is markdown format, easily imported into Jira, Confluence, Notion, or any documentation platform.
- Templates: Customize Mary's templates for organizational standards
- Integration: Export briefs directly to project management tools
- Training: Establish BMAD as standard BA methodology across teams
- Client Presentations: Professional briefs improve proposal success rates
- Scope Validation: Use elicitation to confirm client requirements
- Risk Assessment: Proactive identification reduces project failures
As AI transforms every industry, Business Analysts who master agentic tools like BMAD-METHOD™ will become indispensable. While others struggle with incomplete requirements and misaligned stakeholders, you'll deliver comprehensive, professional documentation that drives successful projects.
Traditional BA skills + BMAD methodology = 10x more effective planning
The investment is minimal (30 minutes to learn, 3 hours for first project), but the impact is transformational.
Major consulting firms and enterprise teams are already integrating agentic planning methodologies. Early adopters report:
- 40% faster project kickoffs
- 60% fewer mid-project requirement changes
- 85% stakeholder satisfaction with documentation quality
- Install now:
npx bmad-method install(5 minutes) - First brief: Complete one project brief with Mary (2-3 hours)
- Share results: Show your team the professional output
- Scale adoption: Train colleagues and establish as standard methodology
You'll know BMAD is working when:
- ✅ Stakeholders stop asking "what exactly are we building?"
- ✅ Developers have fewer questions during sprint planning
- ✅ Project scope changes decrease dramatically
- ✅ You become the go-to person for "how should we plan this project?"
Traditional BA approach: Manual documentation, scattered requirements, reactive problem-solving
Agentic BA approach: AI-guided discovery, systematic validation, proactive risk management
The choice is clear. The question isn't whether agentic tools will transform business analysis - it's whether you'll lead that transformation or be disrupted by colleagues who do.
- BMAD-METHOD™ Official: github.com/bmad-code-org/BMAD-METHOD
- Planning Guides Collection: Awesome Agentic Software
- Discord Community: 15,000+ developers sharing BMAD experiences
- Installation Support: Complete setup documentation and troubleshooting
- BMAD Certification: Professional certification program (coming 2025)
- Enterprise Training: Custom workshops for teams and organizations
- Consulting Services: Expert implementation support for large-scale adoption
- Jira Plugin: Direct export from Mary to Jira epics and stories
- Confluence Integration: One-click publishing to team wikis
- Slack Bot: Mary integration for team collaboration
- API Access: Custom integrations for enterprise workflows
Don't let another project start with incomplete requirements. Don't let another stakeholder meeting end with confusion. Don't let another development team struggle with unclear objectives.
Install BMAD-METHOD™ now and experience the difference systematic, AI-enhanced planning makes.
npx bmad-method install
/analyst
3 # create-project-brief
1 # Interactive ModeYour first comprehensive project brief is just 30 minutes away.
👏 Found this guide helpful? Give it 50 claps to help other BAs discover BMAD!
🔄 Share this with your team - they'll thank you when your next project runs smoothly
💬 Questions? Drop them in the comments - the BMAD community is incredibly helpful
🚀 Tag a colleague who struggles with project planning - this could change their career
The future of business analysis is agentic. Join the thousands of BAs already using BMAD-METHOD™ to deliver exceptional project planning results.