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
91f6c41be1509025f0c520adab856788ae7a4d0a
BMAD-METHOD/docs/_archive/how-to-workflows/run-sprint-planning.md
Alex Verkhovsky 91f6c41be1 docs: radical reduction of documentation scope for v6 beta (#1406) 
* docs: radical reduction of documentation scope for v6 beta

Archive and basement unreviewed content to ship a focused, minimal doc set.

Changes:
- Archive stale how-to workflow guides (will rewrite for v6)
- Archive outdated explanation and reference content
- Move unreviewed content to basement for later review
- Reorganize TEA docs into dedicated /tea/ section
- Add workflow-map visual reference page
- Simplify getting-started tutorial and sidebar navigation
- Add explanation pages: brainstorming, adversarial-review, party-mode,
  quick-flow, advanced-elicitation
- Fix base URL handling for subdirectory deployments (GitHub Pages forks)

The goal is a minimal, accurate doc set for beta rather than
comprehensive but potentially misleading content.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* refactor: restructure BMM and agents documentation by consolidating and flattening index files.

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-25 14:00:26 -06: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