Fabricating Estimates Under Executive Pressure: Navigating the Ethics of Adjusting to Fit the Budget
|
Why Is This Unethical?
|
Risk Management in Agile vs. Traditional Approaches—A Code of Ethics Perspective
Categories:
Scrum,
Risk Management,
Agile,
Change Management,
Leadership,
Lessons Learned,
Decision Making,
Ethics,
Teams,
Organizational Culture,
Governance
Categories: Scrum, Risk Management, Agile, Change Management, Leadership, Lessons Learned, Decision Making, Ethics, Teams, Organizational Culture, Governance
| Risk management is critical in every project, but the way risks are identified, assessed, and communicated can differ greatly between Agile and traditional methodologies. When viewed through the lens of the Project Management Institute’s (PMI) Code of Ethics and Professional Conduct, these differences become even more pronounced. Let’s explore the impact of Agile practices on risk management, how a real Agile implementation compares with a traditional approach, and what this means from an ethical standpoint. Agile Risk Management Practices
Although there is no guidance or a prescriptive approach to risk management, traditional project management methodologies follow a similar pattern:
The PMI Code of Ethics and Professional Conduct is built on four foundational values: Responsibility, Respect, Fairness, and Honesty. Here’s how these values can play out differently in Agile and traditional risk management:
Core Agile values are naturally aligned with PMI’s ethical values by emphasising transparency, shared responsibility, and inclusivity. Traditional methods offer structure and control but may introduce ethical challenges related to communication and accountability. By adopting collaborative and ethical risk management techniques, teams can better serve both their projects and their professional obligations. In principle, a collaborative Agile delivery should manage risk better than a command-and-control approach, but achieving Agile maturity takes time, and very few teams can become self-organised. The challenge of being Agile and effectively managing risk is more obvious when Agile is ‘scaled’ using old practices. Lean, although it may provide cost savings and a faster delivery, requires a standardised process that is contrary to Agile values. Teams transitioning from traditional to Agile or scaling Agile practices beyond a small team of software developers must keep in mind that Agile is empirical, it embraces and needs change and is more dependent on context than traditional project delivery methods. In my opinion, the concept of ‘best practices’ may not exist in Agile. Question for Readers: How does your team ensure that risk management practices align with PMI’s Code of Ethics, and have you observed ethical challenges when shifting between Agile and traditional approaches to risk management? |
Scaled Agile Concerns: Ethical Use of Knowledge
| Scaled Agile Frameworks, the Agile Manifesto, and Lean Six Sigma Ethical Concerns: Ethical Use of Knowledge In a very competitive certification market and as organisations seek to scale agile practices, many turn to structured frameworks and borrow from established methodologies like Lean Six Sigma. While using traditional practices and tools from traditional Project, Portfolio, Program Management and Lean Six Sigma, ethical issues arise when Lean Six Sigma concepts are copied, misrepresented as new Agile practices, or used without proper attribution. These concerns become more acute when such practices diverge from the values of the Manifesto for Agile Software Development. Unknown to many Agile practitioners, Agile emerged as an American response to the success of Lean Six Sigma in Japan, and whilst there is value in improving quality and reducing cost, standardisation is against the Agile core value of responding to change. Intellectual Property Concerns Adopting Lean Six Sigma tools for Agile frameworks or projects can be valuable, but appropriating these concepts without proper acknowledgment raises ethical questions around intellectual property and originality. Methodologies like Lean Six Sigma are the result of years of development and collective expertise. Using their elements without credit not only ignores this lineage but also undermines respect for the source and the broader professional community. Transparency and Honesty Organisations have an ethical duty to be transparent about the origins of their frameworks, metrics, and tools. Presenting repurposed Lean Six Sigma practices as original Agile innovations is misleading and can be perceived as dishonest. This lack of honesty can erode trust and damage the organisation’s reputation, especially if exposed by those familiar with the methodologies. Risks of Misalignment with the Agile Manifesto When organisations implement scaled Agile frameworks that deviate from the core values of the Manifesto for Agile Software Development, especially through uncredited borrowing from Lean Six Sigma, they risk replacing transparency, collaboration, and adaptability with rigid processes and metrics. This can:
Best Practices for Ethical Adoption To uphold ethical standards, organisations should:
Conclusion Respecting intellectual property and being transparent about the origins of agile practices is essential for maintaining credibility and trust. Ethical adoption not only honours the contributions of others but also strengthens the integrity of Agile transformations. Have you encountered issues of transparency or intellectual property in your organisation’s Agile journey? How were they addressed? Share your thoughts in the comments below. |
Scaled Agile Ethical Concerns: Dilution of Agile Principles
| 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:
Upholding Integrity and Authenticity To maintain ethical standards and the true spirit of Agile, organizations should:
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 Ethical Concerns - Impact on Teams and Culture
| 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:
The Path Forward: Upholding Agile Values To ensure ethical and effective Agile transformations, organizations must:
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. |
