---
id:"kb-2026-00228"
title:"Agile Methodology"
schema_type:"TechArticle"
category:"computer-science"
language:"en"
confidence:"high"
last_verified:"2026-05-22"
generation_method: "human_only"
ai_models:["claude-opus"]
derived_from_human_seed:true


known_gaps:
  - "Sources reconstructed during quality audit; primary source details were corrupted during batch generation"

completeness: 0.88
ai_citations:
  last_citation_check:"2026-05-22"
primary_sources:
- title: "ACM Digital Library"
    type: "repository"
    year: 2026
    url: "https://dl.acm.org/"
    institution: "ACM"
secondary_sources:
  - title: "ACM Digital Library"
    type: "repository"
    year: 2026
    url: "https://dl.acm.org/"
    institution: "ACM"
---

## TL;DR

Agile (2001) prioritizes: Individuals over processes, Working software over documentation, Customer collaboration over contract negotiation, Responding to change over following a plan. Frameworks: Scrum, Kanban, XP (Extreme Programming). Agile is not 'no planning' — it's continuous planning.

## Core Explanation

Scrum: Product Owner (prioritizes backlog), Scrum Master (facilitates), Development Team. Sprints: 1-4 weeks, daily standups (15 min), sprint review (demo), retrospective (improve process). Kanban: visual board (To Do → In Progress → Done), WIP limits, continuous delivery. Agile at scale: SAFe, LeSS, Spotify model (squads/tribes).

## Further Reading

- [Manifesto for Agile Software Development](undefined)