ros/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-01-30 04:32:02 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
efbe839a0a9752a3ac6ffa8b4785b290119be2d2
BMAD-METHOD/docs/how-to/workflows/run-sprint-planning.md
forcetrainer e535f94325 docs: comprehensive style guide update with reference and glossary standards 
Style Guide Additions:
- Add Reference Structure section with 6 document types (Index, Catalog,
  Deep-Dive, Configuration, Glossary, Comprehensive)
- Add Glossary Structure section with table-based format leveraging
  Starlight's right-nav for navigation
- Include checklists for both new document types

Reference Docs Updated:
- agents/index.md: Catalog format, universal commands tip admonition
- configuration/core-tasks.md: Configuration format with admonitions
- configuration/global-config.md: Table-based config reference
- workflows/index.md: Minimal index format
- workflows/core-workflows.md: Catalog format
- workflows/document-project.md: Deep-dive with Quick Facts admonition
- workflows/bmgd-workflows.md: Comprehensive format, removed ~30 hr rules

Glossary Rewritten:
- Converted from 373 lines with ### headers to 123 lines with tables
- Right nav now shows 9 categories instead of 50+ terms
- Added italic context markers (*BMGD.*, *Brownfield.*, etc.)
- Alphabetized terms within categories
- Removed redundant inline TOC

All Docs:
- Remove horizontal rules (---) per style guide
- Remove "Related" sections (sidebar handles navigation)
- Standardize admonition usage
- Archive deleted workflow customization docs

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-12 00:23:05 -05:00

2.3 KiB
Raw Blame History

title, description
title description
How to Run Sprint Planning How to initialize sprint tracking for implementation

Use the sprint-planning workflow to initialize the sprint tracking file and organize work for implementation.

When to Use This

  • Once at the start of Phase 4 (Implementation)
  • After implementation-readiness gate passes
  • When starting a new sprint cycle

:::note[Prerequisites]

  • BMad Method installed
  • SM (Scrum Master) agent available
  • Epic files created from create-epics-and-stories
  • Implementation-readiness passed (for BMad Method/Enterprise) :::

Steps

1. Load the SM Agent

Start a fresh chat and load the SM (Scrum Master) agent.

2. Run the Workflow

*sprint-planning

3. Provide Context

Point the agent to your epic files created during Phase 3.

4. Review Sprint Organization

The agent organizes stories into the sprint tracking file.

What You Get

A sprint-status.yaml file containing:

  • All epics with their stories
  • Story status tracking (TODO, IN PROGRESS, READY FOR REVIEW, DONE)
  • Dependencies between stories
  • Priority ordering

Story Lifecycle States

State Description
TODO Story identified but not started
IN PROGRESS Story being implemented
READY FOR REVIEW Implementation complete, awaiting code review
DONE Accepted and complete

Typical Sprint Flow

Sprint 0 (Planning Phase):

  • Complete Phases 1-3
  • PRD/GDD + Architecture complete
  • Epics+Stories created via create-epics-and-stories

Sprint 1+ (Implementation Phase):

Start of Phase 4:

  1. SM runs sprint-planning (once)

Per Story (repeat until epic complete):

  1. SM runs create-story
  2. DEV runs dev-story
  3. DEV runs code-review
  4. Update sprint-status.yaml

After Epic Complete:

  • SM runs retrospective
  • Move to next epic

Tips

  • Run sprint-planning only once — At Phase 4 start
  • Use sprint-status during Phase 4 — Check current state anytime
  • Keep sprint-status.yaml as single source of truth — All status updates go here
  • Update story status after each stage — Keep it current

Next Steps

After sprint planning:

  1. Create Story — Prepare the first story for implementation
  2. Implement Story — Run dev-story with the DEV agent
  3. Code Review — Quality assurance after implementation