The Agile Enterprise

Scaled Agile Frameworks, the Agile Manifesto, and Lean Six Sigma

Ethical Concerns: Dilution of Agile Principles

Introduction

As teams and organizations gain experience with Agile, they feel the need to scale Agile beyond a team of 5-9 software developers. Sometimes, especially when in their desire to scale fast, they ask for external help, it becomes tempting to adopt complex frameworks and borrow tools from other methodologies like Lean Six Sigma. While learning from diverse approaches can add value, ethical concerns arise when Lean Six Sigma practices, like kanban and kaizen, or flow metrics, are disguised as new Agile innovations and when scaled frameworks drift away from the core values of the Manifesto for Agile Software Development.

Focus on Metrics Over Values

Scaled agile frameworks often introduce a heavy emphasis on metrics, measurements, and standardized processes. While metrics can provide structure, over-reliance on them risks overshadowing the Manifesto for Agile Software Development’s focus on individuals and interactions. When teams are judged primarily by adherence to process or by numerical targets, the cultural foundation of agile, empowerment, collaboration, and adaptability can erode. This shift may result in a "checklist" mindset that values process compliance over delivering real value to customers.

Compromised Customer Focus

The Manifesto for Agile Software Development places customer collaboration above contract negotiation, stressing the importance of frequent feedback and adaptation to customer needs. However, when scaled frameworks and borrowed Lean Six Sigma tools become the primary drivers, organizations may inadvertently deprioritize genuine customer engagement. Internal processes and performance metrics can take precedence, leading to products and services that are optimized for internal efficiency rather than for customer value.

Risks of Copying from Lean Six Sigma

Passing off Lean Six Sigma content as original Agile practices is not only misleading but also blurs the distinctions between methodologies. This can:

• Undermine the intellectual honesty of the organization
• Confuse teams, stakeholders, and customers about what agile actually stands for
• Result in practices that prioritize optimization and standardization over adaptability and learning

Upholding Integrity and Authenticity

To maintain ethical standards and the true spirit of Agile, organizations should:

• Acknowledge the origins of any metrics, tools, or processes they adopt
• Ensure all frameworks and adaptations are aligned with the core values of the Manifesto for Agile Software Development
• Foster a culture that values people, collaboration, and customer feedback above process adherence
• Regularly review scaled frameworks and practices to avoid process overreach and loss of customer focus

Conclusion

Misalignment between scaled Agile frameworks and the Manifesto for Agile Software Development, especially when coupled with unacknowledged borrowing from Lean Six Sigma, can dilute Agile principles, compromise customer focus, and undermine organizational integrity. By prioritizing authenticity and alignment with agile values, organizations can avoid these ethical pitfalls and sustain long-term success.

Have you seen agile principles diluted or customer focus compromised in your organization due to scaled frameworks or borrowed practices?

Share your experiences and insights in the comments below.

Scaled Agile Frameworks, the Agile Manifesto, and Lean Six Sigma

Ethical Concerns: Impact on Teams and Culture

As Agile practices mature, many organisations adopt frameworks that introduce greater structure and process. Some also incorporate traditional practices, tools, and metrics, sometimes presenting them as novel Agile solutions. While learning from other methodologies can be beneficial, significant ethical concerns arise when content is copied, relabelled as ‘scaled’ Agile, and implemented without alignment to the core values of the Manifesto for Agile Software Development.

Misrepresentation

When organizations rebrand Lean Six Sigma practices as new agile metrics or tools, they mislead stakeholders—teams, leaders, and customers. This undermines the integrity of the agile movement and erodes trust both internally and externally.

Loss of Authenticity

Agile is built on principles of collaboration, self-organization, and customer feedback. Introducing practices that prioritize process and control over people and adaptability contradicts these core values, leading to a loss of authenticity in agile adoption.

Impact on Teams and Culture

Demoralization

Teams required to adopt frameworks that stray from agile principles may feel demotivated. Instead of feeling empowered, they may experience a culture of compliance, where innovation and creativity are stifled by rigid processes and externally imposed metrics.

Resistance to Change

When teams recognize that the adopted frameworks do not align with the Manifesto for Agile Software Development, they may push back or disengage. This resistance can lead to conflict, reduced morale, and ultimately, lower effectiveness of agile transformations.

The Dangers of Copying Content

Passing off traditional tools and processes as original Agile practices is not only misleading, but it also confuses teams about what Agile truly represents. Agile transformations risk becoming checklist-driven, focusing on optimization and standardization rather than adaptability, learning, and delivering customer value. This can:

• Undermine intellectual honesty
• Confuse teams and stakeholders about Agile’s true essence
• Damage organizational credibility

The Path Forward: Upholding Agile Values

To ensure ethical and effective Agile transformations, organizations must:

• Clearly acknowledge the origins of any practices or tools they adopt
• Align frameworks and adaptations with the Manifesto for Agile Software Development
• Foster a culture of empowerment, transparency, and learning
• Evaluate new practices through the lens of authenticity, customer value, and team engagement

Conclusion

Misalignment between scaled Agile frameworks and the Manifesto for Agile Software Development, especially when driven by unacknowledged borrowing from traditional delivery approaches, poses serious ethical and cultural risks. Organizations that value integrity, authenticity, and team empowerment will be better positioned to realize the full potential of Agile.

Have you experienced repackaging of other methodologies as Agile? How did it impact your team and organization?

Share your experiences in the comments below.

Scaled Agile Frameworks, the Agile Manifesto, and Lean Six Sigma

Ethical Concerns: Integrity and Authenticity

As organizations seek to scale agile practices across large enterprises, many adopt ‘scaled Agile’ frameworks. At the same time, there is a growing trend of incorporating tools and methods from traditional Project, Portfolio, Program Management, and Lean Six Sigma into Agile programs. While cross-pollination of good ideas can be valuable, there are important ethical concerns when traditional practices and content is copied and presented as new agile practices, metrics, or tools—especially when these adaptations misalign with the core values of the Manifesto for Agile Software Development.

Misrepresentation

Presenting traditional practices as original Agile innovations misleads stakeholders—teams, leadership, and customers alike. This kind of misrepresentation undermines the integrity of the Agile movement. Agile is built on transparency and trust; disguising repurposed methodologies erodes confidence and can damage reputation both internally and externally.

Loss of Authenticity

The Agile Manifesto for Software Development values individuals and interactions over processes and tools, and customer collaboration over contract negotiation. When organizations prioritize processes copied from traditional Project Management methodologies or standards, or Lean Six Sigma practices and tools over Agile’s core values, they risk losing authenticity. Teams may become disengaged when forced to follow rigid metrics or tools that do not reflect true agile principles of collaboration, self-organization, and frequent customer feedback.

Misalignment with the Agile Manifesto

Scaled agile frameworks often introduce layers of process and structure to address enterprise complexity. However, if these frameworks ignore or dilute the Manifesto for Agile Software Development, the result can be a process-heavy approach that stifles innovation and responsiveness. The risk is greatest when:

• Decision-making shifts away from empowered teams
• Metrics focus more on efficiency than on delivering customer value
• Feedback loops with actual users are shortened or ignored

The Path Forward: Upholding Agile Values

To maintain ethical integrity, organizations should:

• Align all frameworks and adaptations with the Agile Manifesto’s core values
• Foster a culture of learning and openness, rather than repackaging existing methods as new
• Prioritize collaboration, self-organization, and customer feedback over rigid process adherence

By doing so, enterprises can scale agile in a way that preserves authenticity, builds trust, and delivers true value to both teams and customers.

Conclusion

The ethical concerns around misalignment and misrepresentation are not just theoretical—they directly impact team morale, stakeholder trust, and organizational reputation. As Agile continues to scale, upholding integrity and authenticity is essential to realizing the true promise of agile transformation.

Have you encountered challenges related to Scaled Agile authenticity or ethical concerns in your organization?

Share your thoughts in the comments below.

Take Responsibility for Our Work

AI can assist with estimates, documentation, and reporting, but teams must remain accountable for the final output. Review all Gen AI contributions to ensure they meet Definition of Done and Agile values.

Always Check for Accuracy

Gen AI might generate plausible but incorrect user stories, acceptance criteria, or metrics. Double-check facts and outputs—especially when they inform sprint planning or stakeholder updates.

Protect Privacy

Agile teams often handle sensitive user data during testing and feedback loops. Never expose personal or customer data when prompting Gen AI and anonymize information in retrospectives and demos.

Don’t Disclose Sensitive Information

Avoid sharing proprietary code, business logic, or confidential project details with Gen AI tools—especially those hosted externally. Treat all prompts as potentially public.

Minimise Security Risks

Be alert for vulnerabilities when integrating Gen AI into CI/CD pipelines or Agile tools. Only use approved tools and consult with security experts on any new AI integrations.

Respect and Check IP Rights

If Gen AI helps generate code, UI text, or documentation, verify that no copyrighted or third-party intellectual property is infringed. Attribute sources and ensure compliance with organizational standards.

Take Care Not to Reinforce Unfair Bias

Agile is about building inclusive products. Review Gen AI outputs for bias in recommendations, personas, or automated testing. Promote fairness and diversity in every sprint.

Only Use Gen AI for Valid Work Purposes

Leverage Gen AI to accelerate Agile delivery—not for personal projects, entertainment, or tasks outside your team’s charter. Stay aligned with your organization’s Agile goals.

Be Open About Our Use of Gen AI

Transparency is key in Agile. Disclose when Gen AI is used in sprint artifacts, demos, or documentation. This builds trust with stakeholders and allows for informed feedback.

Human First, AI Assisted
In Agile, Gen AI should support—not replace—teamwork, creativity, and accountability. Teams are still responsible for their deliverables and decisions and should always be able to explain how Gen AI contributed to outcomes. Align outputs with your team’s Definition of Done.

Putting Guardrails into Practice in Agile
Before using Gen AI in your sprints, ask: Have we verified accuracy? Protected privacy? Is our use transparent and secure? Are we reinforcing Agile principles? By staying vigilant, Agile teams can unlock Gen AI’s potential—without sacrificing ethics or trust.

How is your Agile team ensuring responsible Gen AI use while maintaining high standards and team values?

• Does “team accountability” mean no one is responsible for mistakes?
• Can it sometimes shield poor performance or allow issues to go unaddressed?

• Setting explicit expectations for both team and individual roles
• Facilitating open retrospectives that identify root causes without blame
• Ensuring that feedback and recognition are both shared and specific
• Creating a culture where learning from mistakes is valued just as much as celebrating wins