Introduction
Agile communities are no strangers to conversations about team dynamics, culture, and ethics. Tuckman’s ‘ladder” of group development, published in 1965, is a core topic in Agile training courses. As Tuckman indicated, all these phases are necessary and inevitable in order for a team to grow, face up to challenges, tackle problems, find solutions, plan work, and deliver results. These inevitable phases are critical to team growth and development. An Agile enterprise must create the support culture and processes for teams and individuals, including one of the most important prerequisites: psychological safety. Psychological safety—the shared belief that the team is safe for interpersonal risk-taking—has become a cornerstone of high-performing teams. When combined with robust team ethics, psychological safety forms the backbone of trust, transparency, and innovation within Agile environments.
Documents such as the PMI Code of Ethics and Professional Conduct, the Agile Practice Guide, ISO 31000, and the PMBOK all underscore the importance of ethical conduct, respect, and open communication. These principles not only shape how teams interact but also influence the ability to deliver value in fast-paced, complex projects.
This blog post explores the relationship between psychological safety and team ethics, the challenges faced by Agile teams, and recommendations to overcome them.
Challenges
The Myth of Respectful Treatment
Respectful treatment is often touted as a given in Agile teams. However, the reality is that even well-intentioned teams can slip into patterns of microaggressions, exclusion, or unintentional disrespect. The PMI Code of Ethics places respect at its core, defining it as “our duty to show a high regard for ourselves, others, and the resources entrusted to us.” Yet, Agile practitioners report that respect can be compromised under high pressure, tight deadlines, or when dealing with strong personalities.
Blame Cultures and Fear of Failure
A culture of blame is the antithesis of psychological safety. The Agile Practice Guide points out that when mistakes are met with finger-pointing rather than learning, teams become risk-averse and innovation stalls. In organizations where blame is common, team members often conceal problems, avoid experimenting, and withhold valuable feedback. This undermines both project outcomes and individual well-being.
Speaking Up: Risk and Retaliation
ISO 31000 highlights the importance of risk communication, yet many Agile teams struggle to speak up about risks, issues, or unethical behaviours. The fear of retaliation, ridicule, or being labelled a troublemaker can silence even the most conscientious team members. This silence can allow ethical breaches, technical debt, or project risks to fester until they become critical.
Handling Toxic Stakeholders
Dealing with toxic stakeholders—whether they are clients, managers, or team members—presents a significant challenge. On Agile forums there are many posts about the detrimental impact of toxic behaviours, such as manipulation, bullying, or undermining team decisions. Agile teams must navigate these situations delicately, balancing the need for stakeholder engagement with the imperative to protect team well-being and uphold ethical standards.
Recommendations
Embed Ethical Principles in Team Norms
Draw on the PMI Code of Ethics and the Agile Practice Guide to establish explicit team norms around respect, responsibility, fairness, and honesty. Make these principles visible—post them in the team area, reference them in retrospectives, and revisit them regularly.
Foster Psychological Safety Deliberately
Almost 3 decades ago, when Extreme Programming was developed, Ron Jeffries advocated for creating environments where it is safe to ask questions, challenge assumptions, and admit mistakes. Leaders, including Scrum Masters, can model vulnerability by admitting their own errors and inviting feedback. Regular check-ins, anonymous feedback channels, and psychological safety assessments can help track progress and uncover hidden issues.
Replace Blame with Curiosity
Use blameless retrospectives, post-mortems, and root cause analyses to transform failures into learning opportunities. Instead of asking “Who is at fault?” ask “What can we learn?” This shift in language and mindset is supported by PMBOK and ISO 31000, which encourage continuous improvement and knowledge sharing.
Empower Speaking Up—Safely
Create clear, confidential pathways for reporting concerns about risks or unethical behaviour. Train team members in assertive communication and active listening. Hold regular risk workshops, as recommended by ISO 31000, to normalize open discussion about uncertainties and potential threats.
Address Toxic Stakeholders Proactively
Equip the team with conflict resolution skills and clear escalation processes. Engage leaders and HR when necessary to address toxic behaviours. Be transparent about boundaries and team values, making it clear that toxic conduct will not be tolerated, in line with the PMI’s fairness and respect principles.
Align with Global Standards
Leverage frameworks like ISO 31000 (Risk Management), the PMBOK Guide, and the Agile Practice Guide to ensure that team practices align with international best practices for ethics, risk, and stakeholder management.
The Bottom Line
High-performing Agile teams do not emerge by accident. They are intentionally built on a foundation of psychological safety and strong ethical values. Respectful treatment, learning from failure, open communication about risks, and effective handling of toxic stakeholders are not just “nice-to-haves”—they are essential components of sustainable project success.
By embedding the PMI’s ethical principles and utilizing proven standards such as ISO 31000, organizations create environments where teams can thrive, innovate, and deliver lasting value.
Questions for Readers
- How does your organisation and the senior management actively foster psychological safety and ethical behaviour?
- What strategies have worked (or failed) when addressing blame cultures or toxic stakeholders in your experience?
- In what ways can Agile teams better align their practices with established ethical and risk management standards?
