Handbook
Methodology guides (blueprint)
**Purpose:** Deeper, **product-agnostic** guides than the short tables in [`SDLC.md`](../SDLC.md) or project [`TRACKING-METHODOLOGIES.md`](../../../sdlc/TRACKING-METHODOLOGIES.md) (in a consuming repo
Methodology guides (blueprint)
Purpose: Deeper, product-agnostic guides than the short tables in Software development lifecycle (SDLC) or project TRACKING-METHODOLOGIES.md (in a consuming repo's sdlc/). Each file explains the methodology on its own terms, links to authoritative external material, and states how it fits an agentic workflow (humans + automation + optional coding agents) and the engineering-tracking foundation (contributor → events → work units).
Audience: Teams adopting SDLC blueprint; project-specific overrides stay in sdlc/ and docs/.
Foundation (methodology-neutral)
These documents apply regardless of which methodology you choose.
| Guide | Topics |
|---|---|
| Roles & archetypes | Five archetypes: summary + detail (responsibilities, artifacts, ceremonies) + methodology tweaks per archetype; Owner/Implementer; title quick-reference; methodology roll-up; specialty hats vs Contributor. Handbook: methodologies-roles.html. |
| Ceremonies | Foundation (Ceremony foundation (methodology-neutral)): C1–C6, phase + archetype matrices, practice suggestions per intent. Bridge (Methodology bridge — foundation intents ↔ named ceremonies): intents ↔ methodology names, blends, calendar mapping. Forks per methodology. Handbook: methodologies-ceremonies.html. |
Iterative Agile frameworks
Frameworks that organize work in iterations or cadences with cross-functional teams and regular feedback. Most share roots in the Agile Manifesto.
| Guide | Topics |
|---|---|
| Agile (umbrella) | Values, principles, how Scrum/Kanban/XP combine; choosing a primary rhythm. |
| Scrum | Roles, events, artifacts, sprint flow; agentic fit; tracking. Prescriptive package: Scrum — deep-dive package (blueprint). |
| Kanban | Flow, WIP, policies, service classes; board vs git. Prescriptive package: Kanban — deep-dive package (blueprint). |
| Extreme Programming (XP) | Practices, technical excellence, pairing, CI. Prescriptive package: Extreme Programming (XP) — deep-dive package (blueprint). |
| Feature-Driven Development (FDD) | Model-driven, feature-centric; five activities; chief programmers and class ownership; designed for larger teams. |
| Crystal | Family of methods scaled by team size and criticality; seven properties shared across variants (Clear, Yellow, Orange, Red). |
| DSDM | Agile governance framework; MoSCoW prioritization; fixed time/cost, variable scope; integrates with PRINCE2. |
| Shape Up | Basecamp's methodology: 6-week cycles, appetites, shaping, betting table, hill charts; full team autonomy during build. |
Sequential and risk-driven models
Models that emphasize upfront planning, formal verification, or risk-driven iteration. Common in regulated industries and safety-critical systems.
| Guide | Topics |
|---|---|
| Phased delivery | Sequential phases, gates, baselines vs incremental. Prescriptive package: Phased delivery — deep-dive package (blueprint). |
| V-Model | Verification and validation pairing; each development level maps to a test level; traceability-driven. Prescriptive package: V-Model — deep-dive package (blueprint). |
| Spiral Model | Risk-driven iterative development; four quadrants per cycle; anchor-point milestones (LCO, LCA, IOC). Prescriptive package: Spiral Model — deep-dive package (blueprint). |
| RAD (Rapid Application Development) | Prototyping-centric; rapid iterations, user involvement, timeboxing; historical precursor to modern Agile. |
Scaling frameworks
Frameworks designed to coordinate multiple teams delivering a shared product or portfolio of products.
| Guide | Topics |
|---|---|
| SAFe (Scaled Agile Framework) | Multi-team coordination, PI Planning, ART, portfolio governance; scaling Lean-Agile. Prescriptive package: SAFe — deep-dive package (blueprint). |
| Disciplined Agile (DA) | PMI's process-decision toolkit: goal-driven approach with multiple lifecycle options (Agile, Lean, CD, Exploratory, Program). |
Lean and continuous delivery
Principles and practices focused on optimizing flow, eliminating waste, and unifying development with operations.
| Guide | Topics |
|---|---|
| Lean Software Development | Seven principles (eliminate waste, amplify learning, decide late, deliver fast, empower, build integrity, optimize the whole); value-stream thinking; Kaizen. Prescriptive package: Lean Software Development — deep-dive package (blueprint). |
| DevOps | Culture + practices + toolchain unifying Dev and Ops; CI/CD, IaC, monitoring, DORA metrics, incident response. Prescriptive package: DevOps — deep-dive package (blueprint). |
Complementary practices
Practices that enhance any methodology rather than replacing it. They address specific aspects of specification, testing, or development.
| Guide | Topics |
|---|---|
| Spec-driven development | Written intent leads implementation; docs↔code loop; agentic fit. SDD I/O: Spec-driven development — SDD I/O package, templates templates/sdd/. Handbook: spec-driven.html. |
| BDD (Behavior-Driven Development) | Given-When-Then scenarios as living specifications and automated acceptance tests; complements TDD and spec-driven development. |
AI-native delivery
Methodologies designed for AI-augmented development with explicit challenge discipline, decision memory, and evidence-based release rigor.
| Guide | Topics |
|---|---|
| Forge SDLC | AI-native delivery methodology: Ore→Ingot→Spark→Charge pipeline; Versonas (discipline challenge agents covering 16 disciplines); Ember Log (decision memory); Assay Gate (evidence-based release); hat-switching for solo-to-enterprise scaling. Prescriptive package: Forge — deep-dive package (blueprint). |
Cross-cutting
Guides that apply alongside any methodology, addressing how agents, automation, AI, and testing interact with the SDLC.
| Guide | Topics |
|---|---|
| Agentic SDLC | Cross-cutting: agents, review, identity, limits — not a replacement for the guides above. |
| Testing knowledge base | Test levels, types, and design techniques (ISTQB-aligned); modern strategies (shift-left, TDD, BDD, contract testing, AI-augmented); test automation frameworks landscape and selection guidance. Not a methodology — a reference that all methodologies draw from. Now a standalone discipline package under Testing & quality assurance. |
Handbook (HTML): docs/methodologies.html (hub) and docs/methodologies-*.html; spec-driven is docs/spec-driven.html. Scrum/Kanban/phased/XP subchapters (Foundation, Ceremonies, Process) are generated with tables + Mermaid via docs/build_methodology_chapters.py; Scrum — Roles is hand-maintained in HTML.
Maintainers: curated external URLs, executive summaries (why each link matters here), and a quick curl check pattern — REFERENCE-LINKS.md. Keep handbook methodologies-*.html blurbs in sync when URLs or intent change.
Project tracking (optional): sdlc/TRACKING-FOUNDATION.md pattern in repos that add sdlc/.
Canonical source
Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/README.md first; regenerate with docs/build-handbook.py.