Understanding Unethical Behavior in a Scrum Team
Ethical behavior is crucial in any professional setting, including Scrum Teams. Unethical behavior can damage trust, reduce productivity, and negatively impact the overall success of a project. It’s important to recognize and address unethical actions to maintain a healthy and effective team environment.
Exam Question
What would be an example of a Scrum Team member displaying unethical behavior?
Explanation
Example of Unethical Behavior
- Falsifying Work Progress:
Scenario: A Developer in a Scrum Team consistently reports that their tasks are completed during the Daily Scrum, despite knowing that the work is incomplete or of poor quality. This misrepresentation is intended to avoid scrutiny or pressure from the team and stakeholders.
Impact: This behavior undermines the transparency that Scrum relies on. It can lead to inaccurate progress tracking, poor decision-making, and a decrease in the overall quality of the product. Over time, this could erode trust within the team and with stakeholders.
Why It’s Unethical
- Breach of Trust:
Explanation: Scrum is built on the principles of transparency, inspection, and adaptation. When a team member deliberately misrepresents their work, it violates the trust that the team relies on to function effectively. Trust is a core element of successful collaboration and team dynamics. - Compromising the Product’s Integrity:
Explanation: By falsifying progress, the team member risks delivering an Increment that doesn’t meet the Definition of Done or the quality standards expected by the stakeholders. This can result in technical debt, additional rework, and ultimately a product that fails to meet user needs.
How a Scrum Master Should Respond
- Addressing the Behavior:
Explanation: The Scrum Master should address the issue directly with the team member, highlighting the importance of honesty and transparency in the Scrum framework. They should encourage open communication and create an environment where team members feel safe admitting challenges or delays. - Promoting a Culture of Accountability:
Explanation: The Scrum Master can work with the team to establish or reinforce a culture of accountability, where each member understands the importance of their role in delivering quality work. This might involve revisiting the Scrum values, such as courage and openness, during a Retrospective.
Relevance to the PSM III Exam
Understanding how to handle unethical behavior is crucial for Scrum Masters, especially in the context of maintaining a healthy team environment and ensuring the success of the Scrum framework. In the PSM III exam, showcasing an ability to identify and address such issues is important for demonstrating advanced Scrum mastery.
Key Takeaways
- Unethical Behavior: Misrepresenting work progress is a clear example of unethical behavior in a Scrum Team.
- Breach of Trust: Such actions violate the trust that is essential for successful collaboration and transparency in Scrum.
- Role of the Scrum Master: It is the Scrum Master’s responsibility to address unethical behavior, promote a culture of accountability, and ensure that the team adheres to Scrum values.
Conclusion
Unethical behavior, such as falsifying work progress, can have serious repercussions on a Scrum Team’s effectiveness and the quality of the product being developed. As a Scrum Master, it’s essential to address such issues promptly and foster an environment of transparency, trust, and accountability.

Get ready for the official PSM III exam
80+ PSM III essay practice questions, each with a model answer and an in-depth explanation.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 24 random questions in 150 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSM III exam fee is paid separately to Scrum.org.
More PSM III exam questions
- What is meant by a team or organization practicing ‘zombie’ or ‘mechanical’ Scrum?
- Technical debt is the sole concern of the Developers”. As a Scrum Master, do you agree with this statement? Why or why not?
- A fellow Scrum Master asks for your input. His team members see no value in defining a Sprint Goal and he has trouble explaining its use to them. What would you tell this Scrum Master?
- Your Scrum Team has one-month Sprints. The Developers argue that since this period is quite long, a Daily Scrum is a bit too much. They instead want a weekly update meeting. What is your opinion on this?
- How does the Cone of Uncertainty influence the work being done by a Scrum Team during a product’s development lifetime?
