Hans Christian Andersen’s 1837 fairytale ‘The Emperor’s New Clothes‘ has always been one of my favourite fairytales. Even now, as a grown-up, it continues to capture my imagination and resonates within my professional life. The most striking scene from the fairytale involves a deceived emperor strutting around in ‘invisible’ clothing, with his subjects nodding and praising his nonexistent attire, all out of fear or conformity.
The story is a stark reflection of the perils posed by social pressure, blind obedience to norms, and the human penchant for dodging uncomfortable truths. When viewed through an Agile lens, it underscores the need for transparency, courage, and honesty; principles that are absolutely essential for a team’s success.
Social pressure, a silent saboteur
In the tale, the emperor’s court and subjects play along with the conmen’s deception, terrified of being labelled as inept or foolish. This mirrors how social pressure and conformity can creep into teams and organizations. Picture a team where members shy away from voicing concerns or overlook problems to avoid standing out or being judged. This creates a dangerous loop where issues are swept under the rug, and a false sense of security settles in, much like the emperor’s confidence in his imaginary outfit.
Teams may fall into similar traps, clinging to outdated processes out of habit, or stakeholders might accept half-baked increments without questioning their real value. This lack of straightforward communication hinders growth and stagnates the team’s ability to adapt and improve.
Scrum, for instance, is designed to foster collaboration and teamwork. However, the emphasis on collaboration can sometimes suppress individual voices, especially when challenging the norm or questioning decisions made by senior members. During Sprint Planning or Daily Scrums, some team members might hesitate to question the feasibility of a Sprint Goal or the clarity of a Product Backlog Item, fearing that doing so might disrupt team harmony.
Collaboration should never come at the expense of transparency. The pillars of empiricism—transparency, inspection, and adaptation—are critical to the team’s success. When transparency is compromised due to social pressure, the other pillars crumble, leaving the team stumbling in the dark, much like the fairytale’s emperor, blind to his real situation.
A guardian of truth
The Scrum Master plays a pivotal role in nurturing a culture where honesty is encouraged and the norm. By embodying the Scrum values of openness, courage, and respect, the Scrum Master can help diffuse the negative effects of social pressure. By facilitating candid discussions during Sprint Retrospectives, for instance, the Scrum Master ensures that everyone feels safe enough to voice their concerns and ideas, preventing a ‘naked emperor’ scenario from taking hold.
The Scrum Master cultivates an atmosphere where team members feel safe to take risks—whether that means admitting mistakes or voicing differing opinions. This encourages a mindset where failures are viewed as stepping stones to learning rather than pitfalls to be feared. During critical moments like the Sprint Retrospective, the Scrum Master ensures that the environment is favorable to open dialogue, where no idea is dismissed as trivial, and no concern is dismissed as too minor. This practice builds a bedrock of trust within the team, making honesty the norm.
By leading with transparency, the Scrum Master sets a powerful example, sharing their thoughts with candour and inviting others to do the same. This transparency extends from the Product Backlog’s current state to the progress toward the Sprint Goal, making it non-negotiable. The Scrum Master encourages the team to make their work visible, share obstacles, and discuss impediments without hesitation. Clarity in communication becomes the lifeline of effective Scrum practices.
Whether questioning the status quo or navigating through conflicts, the Scrum Master champions courage. They remind the team that stepping into uncomfortable conversations is not just necessary but integral to growth. Scrum’s core values hinge on this bravery, and the Scrum Master ensures it remains central to the team’s interactions.
The Scrum Master actively listens, validates, and empathizes. By acknowledging issues as they emerge, they prevent problems from being swept under the rug, ensuring that challenges are addressed openly and constructively.
Transparency of artifacts
Transparency is the bedrock on which Scrum stands. Without it, teams cannot inspect and adapt effectively. Every Scrum artifact (the Product Backlog, Sprint Backlog, and Product Increment) must be transparent for the team to make informed decisions. Any lack of transparency, intentional or otherwise, is akin to the emperor’s invisible clothes, an illusion that can have catastrophic consequences.
Consider a situation where the Definition of Done (DoD) is unclear or inconsistently followed. The Increment presented at the Sprint Review may seem complete but might lack the necessary quality or functionality. This gap between perception and reality creates a false sense of progress, ultimately damaging both the product and the team’s credibility. Therefore, clarity and transparency in the DoD, as well as all Scrum artifacts, are essential for maintaining trust and ensuring the team delivers true value.
Honesty as a catalyst
One of the greatest advantages of honesty in Agile and Scrum is its role in driving continuous improvement. Agile practices, grounded in the principles of the Agile Manifesto, place a premium on individuals and interactions, customer collaboration, and adaptability. These principles are intertwined with the concepts of transparency and honest communication.
In Scrum, the Sprint Retrospective is designed to bring to light what is working and what is not. When team members are honest about the challenges they face—be it technical debt, unrealistic expectations, or interpersonal conflicts—they create opportunities for genuine improvement. Without this honesty, the team risks becoming a ‘zombie Scrum’ team, where rituals are performed mechanically and continuous improvement is just a buzzword.
The trap of ‘reassurance in the lie’
A particularly sinister aspect of the emperor’s tale is how everyone, including the emperor himself, becomes complicit in upholding the lie. This ‘reassurance in the lie’ can infiltrate Scrum teams as well. It happens when, out of a desire to avoid conflict or to maintain a supportive environment, team members affirm each other’s misconceptions or downplay significant issues.
Imagine a Product Owner pushing for the release of a feature that isn’t truly ‘Done’ and the team, not wanting to rock the boat, goes along with it. This creates a vicious cycle where subpar quality becomes the norm, and the team’s ability to deliver real value gets compromised. Breaking free from this cycle requires the courage to speak uncomfortable truths.
A delicate balance between conformity and self-management
Conformity can suffocate the self-managing nature of Scrum teams. Scrum teams are meant to be self-managing and cross-functional, with the autonomy to decide how to achieve their goals. Yet, when social pressure leads to conformity, this autonomy gets eroded. Teams may start making decisions based on perceived expectations rather than what they genuinely believe is the best course of action.
To counter this, Scrum Masters must actively champion self-management, reinforcing the idea that the team is empowered to make its own decisions. This not only involves equipping the team with the necessary tools and knowledge but also standing by them when external pressures arise. For instance, if stakeholders push the team to deliver more than what is realistically possible, the Scrum Master should help the team articulate their concerns and negotiate a more feasible plan.
Honesty in the face of affection or difficulty
Support and encouragement are vital in any team dynamic, but they should never come at the cost of honesty. Respect, a core Scrum value, includes being forthright with one another. While it is important to uplift and motivate team members, it is equally important to provide constructive feedback and hold each other accountable within the Scrum framework.
Take the Sprint Review, for example. It might be tempting to focus solely on the positives of the Increment, but true care for the product and the team’s growth means also addressing areas needing improvement. This balanced approach ensures continuous development and aligns the product with customer needs.
Avoiding tough conversations is a common trap for many teams, not just those using Scrum. However, in Scrum, this avoidance can have severe repercussions. When team members sidestep discussing challenges or concerns, they prevent the team from tackling issues that could hinder their progress.
Imagine a scenario where a team member struggles with a specific task but does not feel comfortable voicing this issue. This can lead to delays and diminished quality in the Increment. Over time, this avoidance erodes trust within the team and undermines the Scrum process itself. The Scrum Master’s role is crucial in facilitating these difficult conversations and ensuring the team has the courage to face issues head-on.
The Sprint Retrospective is the Scrum team’s moment to look in the mirror and see their reality clearly. It is a time for reflection; what went well, what didn’t, and how to improve. Just as the emperor would have benefited from a mirror before stepping out in his new clothes, Scrum teams gain invaluable insight from the honest reflection offered by the Retrospective. For the Retrospective to be truly effective, team members must feel safe being candid. If fear or social pressure stifles openness, the Retrospective becomes just another empty ritual. The Scrum Master must cultivate an environment where team members can speak freely, knowing their feedback will be heard and valued.
The courage to be honest
In “The Emperor’s New Clothes”, it is a child, unafraid and unfettered by social pressure, who finally speaks the truth. In Scrum, every team member must find the courage to be that child.
Honesty, transparency, and openness are not just nice-to-haves; they are critical to the success of the Scrum framework. Without them, teams risk becoming like the emperor, parading false progress while real issues fester.
For Scrum teams, the benefits of honesty are undeniable. It leads to better decisions, higher-quality products, and stronger team cohesion. By embracing honesty, teams can avoid ‘naked emperor’ scenarios that erode trust and stifle progress. It is the responsibility of every team member, particularly the Scrum Master, to weave honesty into the team’s culture. Only then can Scrum’s potential be realized, delivering genuine value in a transparent and trustworthy way.