agile-processeslisted

# Agile Processes "Agile" names a value system (the Manifesto) that several distinct concrete frameworks (XP, Scrum, Kanban) each implement differently. Conflating the value system with any one framework — treating "doing Scrum" as synonymous with "being agile" — is the single most common process mistake; a team can run textbook Scrum ceremonies and be thoroughly un-agile in practice (heavyweight upfront planning, no actual response to change, ceremony without the underlying value). ## The Agile Manifesto — what it actually says Four value statements, each a preference, not an absolute (the parenthetical is the manifesto's own qualifier, routinely dropped when people cite it): > *Individuals and interactions* over processes and tools > *Working software* over comprehensive documentation > *Customer collaboration* over contract negotiation > *Responding to change* over following a plan > > "That is, while there is value in the items on the right, we value the items on the left more." This means process, documentation, contracts, and plans aren't discarded — they're subordinate to the left-hand items when the two conflict. A team that has stopped writing any documentation "because we're agile" has over-rotated on the letter of the statement and lost the actual point (the manifesto values documentation, just less than working software). **The twelve principles** behind the four values are more operational than the values themselves — worth citing specifically when a proces