In 30 seconds
- Good people talking well beat a perfect process run by strangers.
- Processes and tools should support conversations, not replace them.
- If a tool slows people down, change the tool.
What it means
Software is built by people, and the quality of their collaboration drives the result more than any tool. This value, the first of four agile values, asks teams to fix how they communicate before reaching for more process.
In practice
- Walk over or call instead of opening a ticket for a quick question
- Pair on hard problems rather than splitting them up
- Keep teams small and stable so trust can build
- Choose tools the team agrees help, not ones imposed for reporting
Signs it's backwards
- People say "raise a ticket" to a colleague sitting nearby
- The tool's workflow decides how the team works
- Meetings follow scripts nobody finds useful
Myth vs reality
Myth · Agile teams don't need process.
Reality · They need light process that people own and adapt.
Myth · This value is anti-tool.
Reality · Tools are fine when they serve people.
Myth · Interactions means more meetings.
Reality · It means better, shorter conversations at the right time.
FAQ
How does this apply to remote teams?
Prefer video and quick chat over long written threads for complex topics.
Does this conflict with compliance?
No; meet compliance with the lightest process that works.
Which agile principle backs this value?
Face-to-face conversation is the most effective way to share information.