Inclusive Language in Agile: A Guide to Modern Terminology

Agile methodologies, established over two decades ago, have significantly transformed how software development teams approach their work. The Scrum framework, a popular Agile methodology, is grounded in a set of core values known as the pillars of Scrum. These pillars guide Scrum teams' operations and are closely tied to the importance of inclusive language. Grab a beverage as this one will be a little longer than what I usually write due to the nature of the content.

Beyond "Backlog Grooming": Alternative Terms

The term "backlog grooming" originated in the early days of Agile and Scrum, referring to the process of refining and prioritizing product backlog items. However, due to its association with harmful practices, many organizations have opted for more neutral or inclusive alternatives.

Some popular options include:

Backlog refinement: Emphasizes improving and clarifying backlog items.

Backlog prioritization: Focuses on determining the relative importance of backlog items.

Backlog work: Encompasses various activities related to the product backlog.

Backlog maintenance: Highlights ongoing updates and management of the product backlog.

Backlog optimization: Suggests a focus on improving the efficiency and effectiveness of the product backlog.

Addressing Multiple Terms

The existence of multiple terms can sometimes lead to confusion.

To address this, consider:

Team agreements: Establish shared understanding through discussions, retrospectives, or written agreements.

Cadence and ways of working: Define clear processes and timelines for backlog activities.

PMO or VMO standards: Leverage organizational standards for terminology and processes.

The Pillars of Scrum and Inclusive Language

The pillars of Scrum are:

Commitment: Scrum teams must be committed to their goals and the process of achieving them.

Focus: Scrum teams must be focused on their work and avoid distractions.

Courage: Scrum teams must have the courage to face challenges and make difficult decisions.

These pillars, combined with inclusive language, contribute to a culture of collaboration, respect, and transparency within Scrum teams.

Personal Perspective and Coaching

Even those committed to inclusive language may make mistakes. Even I have made this error when on an early morning call before coffee or breakfast. Of course I felt awful for it, but adjusted. Humans make mistakes, it does not mean we are bad people or condone bad things. Sometimes when we experience pain, it is a great way to discover new ways of doing things and adjusting to our teams. It does not make them a bad agile professional either. There is a lot of knowledge that good Agilist have to hold in thier heads on Agile alone, never mind business and technical accumen. We also have to be adept with psychology. That is a lot to juggle. This is why it is important to assess ourselves and have a willingness to commit to continuous learning/growth/development. We are servant leaders afterall. Weakness makes us relatable.

When someone uses an insensitive term, it's often helpful to approach them with understanding and offer guidance.

Consider:

Private setting: Have a private conversation to discuss the issue without making the person feel defensive.

"I" statements: Focus on how the term made you feel, rather than blaming the person.

Offer alternatives: Suggest more inclusive terms.

Focus on education: Explain why the term is problematic and how it can be harmful.

Be patient: Change takes time.

Note on Terminology Evolution

While terms like "backlog grooming" and "sprinting" have been used for over two decades, it's important to note that they are not technically incorrect. Many guides and governing bodies still cite them in their materials. When coaching, it's essential to highlight that these terms are not wrong, but the terminology is evolving to use more inclusive options like "refinement." This approach fosters a more inclusive and respectful environment within Scrum teams.

Beyond Stand-Ups and Sprints: Alternative Terms

In addition to "backlog grooming," the term "sprinting" has also faced scrutiny. While it's not inherently harmful, some find it evokes images of physical exertion or competition, which might not align with the collaborative and supportive nature of Agile teams.

Alternatives to "sprinting" include:

Iteration: A more neutral term that simply refers to a time-boxed period of work.

Cycle: Another neutral option that emphasizes the cyclical nature of development.

Sprint cycle: A combination of the terms "sprinting" and "cycle," which can be used if the team prefers the former but wants to acknowledge the evolving terminology.

By adopting these alternative terms, teams can create a more inclusive and welcoming atmosphere for all members. Remember, every team is different. Team members need to remember this as well. Sometimes we get used to what works and try to implement on our proven courses of actions, sometimes we need to pivot and reassess a new plan and that is OK.

Alternative Agile and Scrum Terminology

What other Agile or Scrum terms have your teams challenged?

Why, and what alternatives have you adopted?

Share your experiences in the comments below to contribute to a more inclusive and equitable Agile community.

#Agile #Scrum #InclusiveLanguage #Terminology #Teamwork #AgileTransformation #DiversityAndInclusion #agilecoaching