ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/docs/pm-task-library.md

16 KiB
Raw Blame History

Product Manager (John) - Task Library

Overview

This comprehensive task library provides Product Managers with structured, actionable tasks for effectively using the BMAD Method. Each task includes clear objectives, inputs, outputs, and step-by-step execution guidance.

Core Product Management Tasks

PM-001: Create Product Requirements Document (PRD)

Objective: Transform business requirements into comprehensive product specifications

Inputs:

  • Business requirements from stakeholders
  • Market research data
  • User feedback and analytics
  • Technical constraints from architects

Outputs:

  • Complete PRD document
  • User story backlog
  • Acceptance criteria definitions
  • Risk assessment matrix

Execution Steps:

  1. Requirements Analysis

    • Review all input materials
    • Identify gaps and ambiguities
    • Conduct stakeholder interviews if needed
    • Document assumptions and constraints

  2. Market Context Development

    • Analyze competitive landscape
    • Define target user personas
    • Identify market opportunities
    • Document business value proposition

  3. Feature Definition

    • Break down requirements into features
    • Define functional specifications
    • Specify non-functional requirements
    • Create feature prioritization matrix

  4. User Story Creation

    • Write user stories with clear acceptance criteria
    • Map stories to business objectives
    • Estimate story complexity
    • Define story dependencies

  5. Stakeholder Review

    • Present PRD to key stakeholders
    • Collect and incorporate feedback
    • Obtain formal approval
    • Document any scope changes

Quality Checklist:

  • All business requirements addressed
  • User stories follow INVEST criteria
  • Acceptance criteria are testable
  • Technical feasibility confirmed
  • Stakeholder sign-off obtained

PM-002: Conduct Stakeholder Requirements Elicitation

Objective: Gather comprehensive requirements from all relevant stakeholders

Inputs:

  • Stakeholder list and contact information
  • Initial project brief or business case
  • Previous project documentation (if applicable)
  • Market research data

Outputs:

  • Stakeholder requirements matrix
  • Requirements traceability document
  • Conflict resolution plan
  • Prioritized requirements list

Execution Steps:

  1. Stakeholder Mapping

    • Identify all relevant stakeholders
    • Categorize by influence and interest
    • Plan engagement strategy
    • Schedule elicitation sessions

  2. Requirements Gathering

    • Conduct structured interviews
    • Facilitate requirements workshops
    • Use elicitation techniques (user story mapping, etc.)
    • Document requirements in real-time

  3. Requirements Analysis

    • Identify conflicts and dependencies
    • Assess feasibility and impact
    • Prioritize using MoSCoW or RICE
    • Create requirements traceability matrix

  4. Validation and Approval

    • Review requirements with stakeholders
    • Resolve conflicts through negotiation
    • Obtain formal approval
    • Establish change control process

Quality Checklist:

  • All stakeholders consulted
  • Requirements are clear and unambiguous
  • Conflicts identified and resolved
  • Priorities established and agreed upon
  • Traceability maintained

PM-003: Create Product Roadmap

Objective: Develop strategic product roadmap aligned with business objectives

Inputs:

  • Business strategy and objectives
  • Market analysis and competitive intelligence
  • Technical architecture constraints
  • Resource availability and capacity
  • Stakeholder priorities

Outputs:

  • Strategic product roadmap
  • Release planning timeline
  • Feature prioritization rationale
  • Resource allocation plan

Execution Steps:

  1. Strategic Alignment

    • Review business objectives and strategy
    • Identify key market opportunities
    • Define product vision and goals
    • Establish success metrics

  2. Feature Prioritization

    • Apply prioritization frameworks (RICE, Value vs Effort)
    • Consider technical dependencies
    • Assess market timing factors
    • Balance stakeholder needs

  3. Timeline Development

    • Create high-level release schedule
    • Account for technical constraints
    • Include buffer time for risks
    • Align with business milestones

  4. Stakeholder Communication

    • Present roadmap to leadership
    • Gather feedback and iterate
    • Communicate to development teams
    • Establish regular review cycles

Quality Checklist:

  • Aligned with business strategy
  • Technically feasible timeline
  • Stakeholder buy-in achieved
  • Regular review process established
  • Success metrics defined

PM-004: Manage Product Backlog

Objective: Maintain and prioritize product backlog for optimal value delivery

Inputs:

  • User stories and requirements
  • Stakeholder feedback
  • Market changes and opportunities
  • Technical debt and constraints
  • Sprint retrospective insights

Outputs:

  • Prioritized product backlog
  • Sprint-ready user stories
  • Backlog refinement notes
  • Stakeholder communication updates

Execution Steps:

  1. Backlog Grooming

    • Review and update existing stories
    • Add new stories from requirements
    • Remove obsolete or duplicate items
    • Ensure stories meet Definition of Ready

  2. Prioritization

    • Apply consistent prioritization criteria
    • Consider business value and urgency
    • Account for technical dependencies
    • Balance new features with technical debt

  3. Story Refinement

    • Break down large stories (epics)
    • Add detailed acceptance criteria
    • Estimate story points with team
    • Identify and resolve dependencies

  4. Stakeholder Communication

    • Communicate priority changes
    • Explain prioritization rationale
    • Gather feedback on upcoming features
    • Manage expectations on delivery

Quality Checklist:

  • Stories meet Definition of Ready
  • Priorities clearly communicated
  • Dependencies identified and managed
  • Stakeholder expectations aligned
  • Backlog size manageable

Strategic Planning Tasks

PM-005: Conduct Market Analysis

Objective: Analyze market conditions and competitive landscape for informed product decisions

Inputs:

  • Market research reports
  • Competitive intelligence
  • Customer feedback and surveys
  • Industry trend analysis
  • Sales and marketing data

Outputs:

  • Market analysis report
  • Competitive positioning matrix
  • Market opportunity assessment
  • Strategic recommendations

Execution Steps:

  1. Market Research

    • Gather industry reports and data
    • Analyze market size and growth trends
    • Identify key market segments
    • Study regulatory and economic factors

  2. Competitive Analysis

    • Identify direct and indirect competitors
    • Analyze competitor features and positioning
    • Assess competitive strengths and weaknesses
    • Identify market gaps and opportunities

  3. Customer Analysis

    • Review customer feedback and surveys
    • Analyze user behavior and preferences
    • Identify unmet customer needs
    • Segment customers by value and behavior

  4. Strategic Synthesis

    • Synthesize findings into actionable insights
    • Identify strategic opportunities
    • Recommend product positioning
    • Propose go-to-market strategies

Quality Checklist:

  • Comprehensive market data collected
  • Competitive analysis thorough
  • Customer insights validated
  • Strategic recommendations actionable
  • Findings clearly communicated

PM-006: Define Success Metrics and KPIs

Objective: Establish measurable success criteria for product initiatives

Inputs:

  • Business objectives and goals
  • User behavior data and analytics
  • Market benchmarks and standards
  • Technical performance metrics
  • Stakeholder success definitions

Outputs:

  • KPI framework and dashboard
  • Success criteria definitions
  • Measurement plan and timeline
  • Reporting and review schedule

Execution Steps:

  1. Objective Alignment

    • Map metrics to business objectives
    • Identify leading and lagging indicators
    • Define success thresholds
    • Establish baseline measurements

  2. Metric Selection

    • Choose relevant and actionable metrics
    • Balance quantitative and qualitative measures
    • Ensure metrics are measurable and timely
    • Avoid vanity metrics

  3. Measurement Framework

    • Design data collection processes
    • Set up tracking and analytics tools
    • Create reporting dashboards
    • Establish review and analysis cycles

  4. Stakeholder Alignment

    • Present metrics framework to stakeholders
    • Obtain agreement on success criteria
    • Establish reporting responsibilities
    • Create escalation procedures

Quality Checklist:

  • Metrics aligned with objectives
  • Data collection feasible
  • Stakeholder agreement obtained
  • Regular review process established
  • Action plans for metric improvement

Communication and Collaboration Tasks

PM-007: Facilitate Cross-Functional Collaboration

Objective: Enable effective collaboration between product, engineering, design, and business teams

Inputs:

  • Team structures and responsibilities
  • Project requirements and constraints
  • Communication preferences and tools
  • Collaboration challenges and blockers
  • Stakeholder expectations

Outputs:

  • Collaboration framework
  • Communication plan and schedule
  • Conflict resolution procedures
  • Team alignment documentation

Execution Steps:

  1. Team Assessment

    • Map team structures and roles
    • Identify collaboration touchpoints
    • Assess current communication effectiveness
    • Document existing processes and tools

  2. Framework Design

    • Define collaboration principles
    • Establish communication protocols
    • Create decision-making processes
    • Design conflict resolution procedures

  3. Implementation

    • Roll out collaboration framework
    • Train teams on new processes
    • Implement supporting tools and systems
    • Monitor adoption and effectiveness

  4. Continuous Improvement

    • Gather feedback from teams
    • Identify and address pain points
    • Refine processes based on learnings
    • Scale successful practices

Quality Checklist:

  • All teams included in framework
  • Clear roles and responsibilities
  • Effective communication channels
  • Conflict resolution mechanisms
  • Regular improvement cycles

PM-008: Manage Stakeholder Communication

Objective: Maintain clear, consistent communication with all product stakeholders

Inputs:

  • Stakeholder mapping and analysis
  • Product status and progress updates
  • Key decisions and changes
  • Risk and issue information
  • Success metrics and performance data

Outputs:

  • Stakeholder communication plan
  • Regular status reports and updates
  • Decision documentation
  • Feedback collection and analysis

Execution Steps:

  1. Communication Planning

    • Map stakeholder information needs
    • Define communication frequency and format
    • Choose appropriate communication channels
    • Create communication calendar

  2. Content Development

    • Prepare regular status updates
    • Document key decisions and rationale
    • Create executive summaries
    • Develop presentation materials

  3. Delivery and Engagement

    • Deliver communications on schedule
    • Facilitate stakeholder meetings
    • Collect feedback and questions
    • Address concerns and issues promptly

  4. Feedback Integration

    • Analyze stakeholder feedback
    • Incorporate insights into planning
    • Adjust communication approach as needed
    • Close the feedback loop

Quality Checklist:

  • All stakeholders included
  • Communication timely and relevant
  • Feedback actively collected
  • Issues addressed promptly
  • Communication effectiveness measured

Risk and Issue Management Tasks

PM-009: Conduct Risk Assessment and Mitigation Planning

Objective: Identify, assess, and mitigate risks that could impact product success

Inputs:

  • Project scope and requirements
  • Technical architecture and constraints
  • Market conditions and competitive landscape
  • Resource availability and constraints
  • Historical risk data and lessons learned

Outputs:

  • Risk register and assessment matrix
  • Risk mitigation strategies and plans
  • Contingency plans for high-impact risks
  • Risk monitoring and reporting procedures

Execution Steps:

  1. Risk Identification

    • Brainstorm potential risks with team
    • Review historical project risks
    • Analyze external market factors
    • Consider technical and resource constraints

  2. Risk Assessment

    • Evaluate probability and impact
    • Prioritize risks using risk matrix
    • Identify risk interdependencies
    • Assess current risk exposure

  3. Mitigation Planning

    • Develop mitigation strategies
    • Create contingency plans
    • Assign risk owners and responsibilities
    • Establish monitoring procedures

  4. Implementation and Monitoring

    • Implement risk mitigation measures
    • Monitor risk indicators regularly
    • Update risk assessments as needed
    • Communicate risk status to stakeholders

Quality Checklist:

  • Comprehensive risk identification
  • Accurate risk assessment
  • Effective mitigation strategies
  • Clear ownership and accountability
  • Regular monitoring and updates

PM-010: Manage Scope Changes and Requirements Evolution

Objective: Control scope changes while allowing for necessary requirements evolution

Inputs:

  • Original project scope and requirements
  • Change requests from stakeholders
  • Market changes and new opportunities
  • Technical discoveries and constraints
  • Resource and timeline impacts

Outputs:

  • Change control process and procedures
  • Impact assessment documentation
  • Approved scope changes
  • Updated project documentation

Execution Steps:

  1. Change Control Setup

    • Define change control process
    • Establish change approval authority
    • Create change request templates
    • Set up tracking and documentation

  2. Change Evaluation

    • Assess change request validity
    • Analyze impact on scope, time, cost
    • Evaluate alignment with objectives
    • Consider alternative solutions

  3. Decision Making

    • Present impact analysis to stakeholders
    • Facilitate decision-making process
    • Document decisions and rationale
    • Communicate changes to all teams

  4. Implementation

    • Update project documentation
    • Adjust plans and schedules
    • Reallocate resources as needed
    • Monitor implementation progress

Quality Checklist:

  • Clear change control process
  • Thorough impact analysis
  • Stakeholder approval obtained
  • Documentation updated
  • Teams informed of changes

Integration with BMAD Method

Workflow Integration Points

  • From Business Analyst: Receive validated business requirements
  • To UX/UI Architect: Provide detailed product specifications
  • To System Architect: Share technical requirements and constraints
  • To Product Owner: Hand off refined backlog and priorities

Collaboration Patterns

  • Requirements Workshops: Facilitate cross-persona requirements sessions
  • Design Reviews: Participate in UX/UI design validation
  • Architecture Reviews: Provide product perspective on technical decisions
  • Sprint Planning: Collaborate with PO on sprint goals and priorities

Quality Gates

  • Requirements Completeness: Ensure all business needs addressed
  • Stakeholder Alignment: Verify stakeholder agreement on priorities
  • Technical Feasibility: Confirm technical viability with architects
  • User Value: Validate user value proposition for all features

Best Practices

Documentation Standards

  • Use consistent templates and formats
  • Maintain version control and change logs
  • Include rationale for all major decisions
  • Create searchable and linkable content

Stakeholder Management

  • Regular communication and updates
  • Clear escalation paths and procedures
  • Transparent decision-making processes
  • Active feedback collection and integration

Collaboration Excellence

  • Foster cross-functional team alignment
  • Facilitate effective meetings and workshops
  • Promote shared understanding and goals
  • Address conflicts promptly and fairly

This task library provides comprehensive guidance for Product Managers using the BMAD Method. Each task includes detailed execution steps, quality criteria, and integration points with other personas.