"Individuals and interactions over processes and tools" is value 1 of the agile-manifesto-four-values and the humanistic core of the Agile movement. It was not a unanimous first choice — the signatories at snowbird-meeting-2001 had to decide on ordering — but it reflects a genuine convergence across traditions that all arrived at Snowbird having found that people matter more than methodology.
What It Rejected
The value targets a specific pathology of 1990s enterprise software methodology: the belief that process could substitute for people. The Capability Maturity Model (CMM) and ISO 9001-based quality frameworks were built on the premise that a sufficiently well-defined process, rigorously followed, would produce consistent software quality regardless of who was doing the work. This was not an unreasonable hypothesis — manufacturing had demonstrated that process standardization could transform quality — but it imported a model from physical production into knowledge work where it did not fit.
The practical consequence was a consulting and certification industry that sold process compliance as a substitute for building capable teams. Organizations would spend enormous resources on CMM level assessments while individual developers worked in dysfunctional conditions.
The Evidence from the Traditions
Every methodology represented at Snowbird had independently reached similar conclusions. alistair-cockburn's crystal work placed people and their interactions at the center: Cockburn had empirically studied what distinguished successful from unsuccessful projects and found that team communication patterns mattered more than process choices. His project communication model — the closer the communication channel (face-to-face over email, verbal over written), the higher the bandwidth — was already a formal articulation of why interactions matter.
kent-beck's extreme-programming embedded the value in practices: pair-programming is a continuous, high-bandwidth interaction; the on-site customer is an interaction structure; collective code ownership is a practice that requires constant interaction. XP's practices were not arbitrary — they were selected to maximize the quality of human interaction around code.
jeff-sutherland and ken-schwaber's scrum expressed it through self-organizing-teams: the team that chooses how to do its work harnesses individual judgment and interpersonal coordination in ways that a prescribed process cannot.
What "Over" Does Not Mean
The value does not claim that processes and tools are worthless. The manifesto's qualifying clause preserves their legitimacy: "while there is value in the items on the right." The claim is about priority: when process compliance and human judgment conflict, prefer human judgment. When tool standardization and effective collaboration conflict, prefer collaboration.
This creates a genuine and unresolved tension in the movement. Version control, continuous integration servers, issue trackers, and collaboration platforms are tools that enable the interactions the value prioritizes. The productive reading is not "tools bad" but "tools that constrain individuals and inhibit interaction bad; tools that expand capacity for effective interaction good."
Legacy
The humanistic turn the value represents connects the Agile movement to a longer tradition in software thinking — Peopleware (DeMarco and Lister), Weinberg's quality of software life, the software craft movement — that had been making the same argument outside the process-improvement mainstream for decades. Agile gave these arguments institutional form.