> Markdown version of [/videos/431-non-violent-communication-in-agile-teams?t=593](https://www.wearedevelopers.com/videos/431-non-violent-communication-in-agile-teams?t=593). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Non-violent communication in agile teams

Are team friction and cultural clashes derailing your sprints? Discover how non-violent communication transforms your agile ceremonies into hubs of psychological safety.

- **Speakers:** Alexandre Borges
- **Event:** World Congress 2022
- **Published:** June 15, 2022
- **Duration:** 28:33
- **URL:** https://www.wearedevelopers.com/videos/431-non-violent-communication-in-agile-teams

## Summary

Software engineering is inherently people-centric; code is written, reviewed, and utilized by human beings. However, navigating team dynamics and cross-cultural communication often leads to misunderstandings or friction. Non-violent communication (NVC) offers a framework based on empathy and clear observation to improve these interactions. Far from just a soft skill, NVC is positioned as a continuous research process that aligns seamlessly with agile methodologies, leveraging the frequent feedback loops of sprint cycles to foster psychological safety.

Agile ceremonies like retrospectives and daily stand-ups provide built-in opportunities to practice the Empathy Circle. This four-step framework involves objective observation, naming personal feelings, expressing a core wish, and making a clear request. By becoming an empathy agent—symbolized by the NVC giraffe, which represents stepping back and listening actively—developers can bridge cultural communication gaps, such as differing levels of directness across global teams.

While adopting NVC, practitioners must avoid common pitfalls like weaponizing the framework for manipulation, disrupting meeting flows with over-explanation, or becoming easily frustrated when well-intentioned messages are misunderstood. Ultimately, mastering NVC requires rigorous self-observation before addressing others, ensuring that empathy remains authentic rather than performative. Recommended foundational readings include Marshall Rosenberg's work and Paulo Freire's Pedagogy of the Oppressed to deepen this ongoing practice.

**Keywords:** non-violent communication, agile team dynamics, empathy circle framework, cross-cultural team communication, software engineering culture, psychological safety, agile retrospective feedback, active listening techniques, conflict resolution strategies, overcoming communication pitfalls, emotional intelligence in tech, marshall rosenberg frameworks, distributed team collaboration, continuous improvement cycles

## Chapters

1. **Establishing the core principles of non-violent communication** (00:13) — The baseline for healthy interaction requires intentionally avoiding harm to oneself and others in every instance.
1. **Understanding non-violent communication as a research process** (03:27) — Developing self-awareness and compassion becomes a continuous practice of discovering more effective ways to engage with others.
1. **Avoiding common pitfalls during non-violent communication practice** (05:10) — Misinterpreting empathy techniques can easily lead to unintended manipulation, disruptive over-communicating, or painful interpersonal misunderstandings.
1. **Connecting effective communication frameworks with agile methodology** (09:53) — Writing and testing software heavily depends on human collaboration, making interpersonal empathy critical for engineering processes.
1. **Leveraging agile routines for continuous communication practice** (12:17) — Regular sprint intervals, daily standups, and review ceremonies provide frequent opportunities to refine interpersonal exchanges within technical teams.
1. **Navigating the four iterative steps of the empathy circle** (13:51) — Observing situations, naming personal feelings, identifying core wishes, and asking clear questions establishes mutual team alignment.
1. **Becoming an empathy agent to bridge cultural differences** (19:58) — Actively listening and directly asking for clarity helps foster safety and trust across diverse cultural communication styles.
1. **Expanding empathy benefits across professional and personal boundaries** (23:52) — Collaborative problem-solving relies on mutual respect rather than isolated technical skills, which also directly benefits outside relationships.
1. **Recommended reading and managing intentions during communication** (26:36) — Foundational texts provide necessary theoretical background for continuous practice while self-observation helps prevent weaponising emotional language.

## Related Moments

- [Aligning Agile communication needs with collaborative working preferences](https://www.wearedevelopers.com/videos/862-diversity-as-a-growth-and-happiness-factor-in-agile-development) (from "Diversity as a Growth and Happiness Factor in Agile Development")
- [Cultivating a learning-focused and empathetic engineering culture](https://www.wearedevelopers.com/videos/64-shared-mobility-for-everyone) (from "Shared mobility for everyone!")
- [Applying the five core values of extreme programming](https://www.wearedevelopers.com/videos/398-building-the-right-product-and-building-it-right-a-glimpse-into-extreme-programming-atomic-design) (from "Building the Right Product and Building It Right: A Glimpse into Extreme Programming, Atomic Design ")
- [Fostering soft skills and ethics in open source contributions](https://www.wearedevelopers.com/videos/2137-what-to-do-about-hackathons-in-the-time-of-agents-mike-swift) (from "What to Do About Hackathons in the Time of Agents - Mike Swift")
- [Connecting empathy to technical resilience in software development](https://www.wearedevelopers.com/videos/465-empathy-the-secret-sauce-of-resilience) (from "Empathy: The secret sauce of Resilience")
- [Assessing software team maturity through targeted self-reflection questions](https://www.wearedevelopers.com/videos/66-how-to-be-balanced-in-a-software-development-team) (from "How to be balanced in a software development team")

## Related Articles

- [A Guide to Public Speaking For Software Engineers](https://www.wearedevelopers.com/magazine/324-a-guide-to-public-speaking-for-software-engineers)
- [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)
- [Lessons for Vibe Coders and Developers](https://www.wearedevelopers.com/magazine/614-lessons-for-vibe-coders-and-developers)
- [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers)

## Related Jobs

- [Principal UX Researcher, AI & Developer Platforms](https://www.wearedevelopers.com/jobs/ext/2733704-principal-ux-researcher-ai-developer-platforms) at **ARM**
- [Founding Developer Advocate](https://www.wearedevelopers.com/jobs/48425-founding-developer-advocate) at **Plumber**
- [UNIT TRANSFORMATION PARTNER / AGILE COACH](https://www.wearedevelopers.com/jobs/ext/2161121-unit-transformation-partner-agile-coach) at **Wilken GmbH**
- [Staff Software Engineer, Agentic Platform](https://www.wearedevelopers.com/jobs/48464-staff-software-engineer-agentic-platform) at **Docker, Inc.**
- [Senior AI/ML Engineer](https://www.wearedevelopers.com/jobs/48352-senior-ai-ml-engineer) at **PagerDuty**
- [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/2628442-staff-developer-advocate-github-security-lab) at **GitHub**