spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

The 12 Principles Behind the Agile Manifesto: Principle Number Six – Promote Face To Face Interaction

Written by SPK Blog Post
Published on January 14, 2019

Welcome back to our series as we continue to examine the 12 principles underlaying the Agile Manifesto! Our topic for this installment is principle six’s guidance on effective communication. This principle states the following:

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.”

In this principle, Agile is expressing its opinion about the best means of exchanging information. It’s not suggesting this is the only means of effective communication, but rather, all things considered, face-to-face communication should be prioritized whenever feasible.

Face to face communication has multiple dimensions with which it can convey meaning. These include tone of voice, body language, environmental cues, and facial expression. Limiting or constraining any of those channels reduces the overall information density of the exchange. It’s not that we are incapable of expressing our meaning through other forms of communication. The point is that face-to-face requires less time and effort to do so.

Many people have experienced the pain and frustration of a poorly connected conference call. Trying to discuss complex issues when every fourth word cuts out, someone’s dog is barking, and the volume is too high for one of the participants can have a real effect. It can turn what would otherwise be a 10 minute discussion into 30 minutes and it can cause people to avoid reaching out to remote personnel in order to avoid the associated hassle. All of this slows down the development cycle and reduces the overall sprint velocity.

Again, sometimes circumstances compel us to use certain forms of communication over others. When Agile suggests face-to-face is the best form of communication it’s not suggesting we shun all others. Rather, whenever possible, we should prioritize in-person communication and seek to foster that whenever we can.

David Hubbell
Senior Software Engineer
SPK & Associates

Latest White Papers

10 AI Use Cases: Accelerating Automotive Embedded Development

10 AI Use Cases: Accelerating Automotive Embedded Development

Software-defined and electric vehicles are only increasing as automotive technology advances. As these features grow, automakers must adapt. Manufacturing a car is not the same as it was years ago. This eBook explores how AI can be used in the automotive development...

Related Resources

Why Aerospace Programs Miss Deadlines Part 2

Why Aerospace Programs Miss Deadlines Part 2

Key Takeaways A connected digital thread helps prevent schedule delays: Linking CAD, simulation, PLM, ALM, and DevOps gives aerospace teams better visibility into dependencies, changes, and risks across the lifecycle. Earlier validation reduces costly rework: Creo and...

What CIOs Get Wrong About PLM and Digital Thread Strategy

What CIOs Get Wrong About PLM and Digital Thread Strategy

PLM and Digital Strategy for CIOs Hello, everyone, and welcome back to another SPK and Associates vlog. My name is Michael Roberts. I'm the Vice President of Sales and Marketing here at SPK and Associates. Today, we're tackling a topic that comes up consistently in...

Why Late-Stage Changes Are Killing Your Time to Market

Why Late-Stage Changes Are Killing Your Time to Market

Key Takeaways Late-stage changes get expensive fast: The farther a problem travels through design, testing, and manufacturing, the more time, cost, and rework it creates. Disconnected systems and weak traceability are major causes: When requirements, design, software,...