Bibliography / References for Further Study

Extreme Programming (primary sources)

• Kent Beck, Extreme Programming Explained: Embrace Change (2nd ed., 2004) - the canonical source for the 12 practices
• Kent Beck & Cynthia Andres, Planning Extreme Programming (2000)
• Ron Jeffries, Ann Anderson, Chet Hendrickson, Extreme Programming Installed (2000)

Agile / Kanban / Lean

• Manifesto for Agile Software Development - the four value-pairs, useful as a structural contrast point for whatever manifesto format this project lands on
• Mary Poppendieck & Tom Poppendieck, Lean Software Development: An Agile Toolkit (2003) - source of the "eliminate waste" framing referenced under Simple Design/YAGNI
• David J. Anderson, Kanban: Successful Evolutionary Change for Your Technology Business (2010) - WIP limits, pull systems

Architecture / Design Discipline

• Neal Ford, Rebecca Parsons, Patrick Kua, Building Evolutionary Architectures (2017) - source of "fitness functions," relevant to bounding refactoring/scope creep and possibly Metaphor's replacement
• Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software (2003) - relevant background for Domain Gap Surfacing and ADR-level spec work
• Michael Nygard's ADR format (original blog post: "Documenting Architecture Decisions", 2011; see also adr.github.io) - likely the direct ancestor of the spec-first ADR practice

DevOps / SRE (relevant to Merge/Integration Authority)

• Gene Kim, Kevin Behr, George Spafford, The Phoenix Project (2013) - narrative introduction to DevOps flow concepts
• Google, Site Reliability Engineering (2016, free online: sre.google/books) - error budgets, postmortems, relevant to merge-bottleneck/candidate-build thinking
• Jez Humble & David Farley, Continuous Delivery (2010) - the deeper technical background behind CI/CD risk-tiering

Adjacent "AI-Native SDLC" Literature (for direct comparison - see Chapter 8)

• Anthropic Applied AI team, "The AI-Native SDLC playbook" (Claude Blog, August 21, 2026) - the primary comparison point for Chapter 8; org-scale, artifact-driven (intent.md/spec.md/plan.md), no XP lineage
• AWS (Raja SP), "AI-Driven Development Lifecycle (AI-DLC)" (2025) - a competing org-scale framing, worth reading alongside the Anthropic playbook for contrast

AI-Assisted Development

• Kent Beck, Software Design: Tidy First?:
  • "Trust Factory" (June 2026) - reframes XP practices as trust-manufacturing mechanisms, examines the code-vs-trust deficit in AI development, and references emerging "XPAI"
  • "Augmented Coding: Beyond the Vibes" (June 2025) - foundational distinction between "vibe coding" and disciplined "augmented coding" bounded by TDD and structural hygiene
  • "The Genie Eats The Seed Corn" (published as "Augmented Coding & Design", May 2025) - how AI coding assistants lack incentives to refactor, eating into future maintainability for short-term feature output
• Anthropic's engineering blog and documentation on Claude Code (claude.com/docs) - primary source for tooling architecture, workflows, and capabilities
• GitHub's engineering blog on Copilot usage patterns - useful comparative data on AI-pairing at scale in human teams, different context (large orgs, not solo/small-team) but relevant contrast
• arXiv Software Engineering (cs.SE) - repository for preprints and empirical research on AI pair programming, LLM code review, and agentic software development

Adjacent/Contrasting Methodologies (mentioned but not adopted)

• Harlan Mills et al. on Cleanroom Software Engineering (IBM technical reports, 1980s; see also Mills et al., "Cleanroom Software Engineering," IEEE Software, 1987) - mostly of historical interest but relevant to the "formal spec, AI implements faithfully" thread
• Dan North, "Introducing BDD" (2006, original article) - Given/When/Then framing, relevant to Spec-First Prompting's executable-adjacent variants

Versioning / Release Discipline

• Tom Preston-Werner, Semantic Versioning 2.0.0 - the canonical SemVer spec
• Conventional Commits - specification for adding human- and machine-readable meaning to commit messages, referenced under Coding Standards
• CalVer - informal reference for calendar-based versioning schemes and when teams choose it over SemVer