The Agile Manifesto states its four values as 'X over Y' — what does that phrasing claim about the right-hand items?
answer
- Four pairs, then one more sentence
- Both columns name things professionals do
- The word over compares two goods
- Read what the closing line grants
basics
~20 sThe right-hand items still have value — the Manifesto says only that the left-hand items are valued more when the two compete. It is a ranking under tension, not a licence to drop documentation, plans, contracts or process.
solid answer
~40 sThe Manifesto lists four pairs: **individuals and interactions** over processes and tools, **working software** over comprehensive documentation, **customer collaboration** over contract negotiation, and **responding to change** over following a plan. The sentence after the list is the part candidates skip: while there is value in the items on the right, the authors value the items on the left more. So 'over' is a tie-breaker, not a delete key. It fires only when the two items in a pair compete for the same hour or the same decision; outside that moment it says nothing. A team still writes documents, still plans, still signs agreements — it just refuses to let those outrank a conversation, a running product or a customer's changed need. 'Agile means no documentation' is the classic misread, and interviewers listen for it.
go deeper
Be ready to list all four pairs from memory and to add the closing line about the right-hand items. This is a screening question, and forgetting that closing line is the most common way to lose the mark on it.
Explain the mechanics: each pair names two things a professional team does, and the ranking only fires when the two compete for the same hour or decision. Bring a concrete example of a choice you made on either side of one pair.
Show judgement about when the right-hand item genuinely wins in a real system — a durable interface, an audit record, a hand-off across timezones — and explain why choosing it is applying the values rather than departing from them.
Own the organisational reading: the values are a tie-breaker you can hand a team, not a standard you can audit. Be ready to say how you keep documents and agreements proportionate without letting either become the unit of progress.
## The four pairs, and the sentence that follows them The Manifesto for Agile Software Development is a very short document: four value statements, one qualifying sentence, and twelve principles published alongside them. The four statements are: - **Individuals and interactions** over processes and tools - **Working software** over comprehensive documentation - **Customer collaboration** over contract negotiation - **Responding to change** over following a plan The qualifier is the part most candidates skip: while there is value in the items on the right, the authors value the items on the left more. Everything about how to read the four pairs is in that sentence. Without it, 'over' looks like a delete key — no documents, no process, no agreements, no plans. With it, 'over' is what it was written to be: a tie-breaker between two things that both have value. ## Each pair names two goods, not a good and an evil Read the right-hand column on its own and it is a list of things professional teams do. Processes and tools are how work stays repeatable. Comprehensive documentation is how understanding survives the people who had it. Contract negotiation is how two organisations agree what money buys. A plan is how a team notices that something changed — you cannot respond to a change you had no expectation to compare it against. So the pairs are not a hierarchy of virtue. They are a rule for one specific moment: when the two items in a pair compete for the same hour, the same decision or the same budget, favour the left. Outside that moment the value is silent. A team that spends a morning writing an interface document, trading it against nothing, has not violated a value; it has simply done work. ## Reading a pair under pressure | The collision | The right-hand pull | The left-hand pull | What the value decides | | --- | --- | --- | --- | | A routing rule changes in week 6 of a 118-item quarter | the plan everyone agreed to | the customer's current need | re-plan openly; the plan was a forecast | | A colleague in another timezone needs a design | a 40-page specification | a 2-page sketch plus a recorded walkthrough | pick the cheapest artefact that transfers understanding | | A stakeholder asks whether the work is on track | a status document | the running product, demonstrated | show the thing itself | | Scope is disputed | the clause in the agreement | a conversation about what is actually needed | talk first, keep the agreement as the backstop | Notice that in the second row the answer still includes a document. Choosing the left-hand item usually means choosing a smaller version of the right-hand one, not none of it. ## The misreads an interviewer is listening for - **'Agile means no documentation.'** The most common single error. It converts a ranking into a prohibition, and it usually signals someone who read the four pairs and not the sentence after them. - **'Agile means no planning.'** Responding to change presupposes something to respond from. The value ranks new information above the stale plan; it does not remove the plan. - **'The right-hand items are obsolete.'** They are things the authors said explicitly have value. A team producing no documents, no plan and no agreement has not implemented the Manifesto; it has ignored half of it. - **'The values are a process.'** They are preferences, stated as preferences. Nothing in the four pairs tells you how long an iteration is, who is accountable for what, or how work is sized. - **Reciting without a decision.** A candidate who lists the pairs but cannot give one occasion where the ranking changed what they did has memorised a poster. ## Why the phrasing was chosen The 'X over Y' construction does something a list of rules cannot: it stays usable in cases its authors never saw. A rule about documentation would have to say how much documentation, for which kind of system, under which regulator — and it would be wrong somewhere immediately. A ranking under tension delegates the judgement to the people holding the tension while still saying which way to lean. That is also why the document is short enough to memorise and why it prescribes no practice at all: the pairs are a decision aid, not a method. It also explains why the values survive being applied in places that look nothing alike. A team building a forklift-routing product for one warehouse operator and a team maintaining a widely-used public interface face very different documentation economics. The second team may reasonably choose the right-hand item most weeks. It is still applying the value, because the value asks which one wins when the two compete — and in that context the honest answer is the right-hand item. ## What a strong answer sounds like Name the four pairs. Add the closing sentence in your own words. Then give one concrete decision: a time you deliberately chose the right-hand item and why that was consistent with the values, and a time you chose the left. Interviewers use this question early precisely because the shape of the answer separates people who absorbed the intent from people who memorised a list.
- Give an example where you would deliberately choose a right-hand item.When the outcome has to be reproducible without me: an audit record the domain requires, a stable interface other teams build against, or a hand-off to a colleague in another timezone who cannot ask me a question for fourteen hours. There, comprehensive documentation genuinely beats a conversation. The value pair does not forbid it — it says only that when a document and a conversation compete for the same hour and either would do, take the conversation.
- Which of the four values do teams claim most often and honour least?Responding to change. Almost every team says it welcomes change, then routes each request into an approval queue with a monthly cycle. The measurable tell is latency: how long between a customer changing their mind and the team changing what it builds. If that is months, the team is following a plan, whatever it calls its way of working.
- Does the Manifesto say the right-hand items are unimportant?It says they are valued less than the left-hand items, which is a relative ranking rather than a verdict that they do not matter. The authors listed them precisely because they are worth having. A team with no documentation, no plan and no agreement has not implemented the Manifesto; it has implemented half of it and discarded the rest.
'Over' works like a preference expressed in a will rather than a prohibition: everything named still has value, and the document only says whose claim is honoured first when two of them collide.
saying these in an interview costs you the question
- Claims agile means producing no documentation at all
- Cannot recall the closing line that keeps the right-hand items valuable
- Says planning is forbidden because change is valued over plans
- Treats the four values as a sequence of steps to follow
- Recites the pairs but cannot name one decision they changed
- Calls the right-hand items obsolete practices to be eliminated