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? |
Agile “Transformation Theatre”: Beyond the Buzzwords
Agile transformation is everywhere. Companies proudly announce their Agile journeys, touting new ceremonies, digital tools, and a fresh lexicon. But beneath the surface, many organizations fall into the trap of what’s now being called “transformation theatre”—where the appearance of change masks business-as-usual operations.The Illusion: Agile in Name OnlySome organizations claim to have adopted Agile, but little has changed in practice:
The Ethical Concern: Branding vs. ValuesWhen Agile becomes a branding exercise, its values—collaboration, transparency, continuous improvement—are sidelined. The core question emerges:
The Hot Trend: Exposing “Fake Agile” and Reclaiming IntegrityThe Agile community is pushing back. Coaches, leaders, and practitioners are increasingly calling out “fake Agile” and insisting on:
Real Agile transformation is more than a rebrand. It demands a shift in mindset, structure, and daily habits—a commitment to values over optics. The organizations that succeed will be those who practice integrity, even when it’s hard. Have you experienced transformation theatre? What does real Agile mean to you? |
AI and Agile Decision-Making: Navigating the New Frontier
Agile ways of working are evolving rapidly, and artificial intelligence is at the centre of this transformation. Teams are increasingly turning to AI-powered tools for estimation, backlog prioritization, and even code generation. While these capabilities promise efficiency and objectivity, they also introduce new tensions and ethical questions into the decision-making process.Algorithm-Driven Decisions: Promise and PitfallsAI tools can analyse vast amounts of data at lightning speed, surfacing patterns and recommendations that might escape human notice. In Agile, this means:
The Risk of Bias and Blind TrustAI models are only as good as the data that train them—and that data can carry hidden biases. If an AI tool is used to prioritize backlog items, it may inadvertently favour certain types of work or stakeholders, reinforcing existing inequities. Furthermore, teams may:
Key Ethical Questions
Moving Forward: Human-Centered AI in AgileThe future of Agile decision-making with AI isn’t about replacing teams but augmenting them. The most effective organizations are:
AI can supercharge Agile teams, but only if its use is intentional, transparent, and ethically grounded. The best results come when humans and machines work together—combining data-driven insights with the irreplaceable nuance of human judgment. How is your team integrating AI into Agile practices? What questions are you asking about trust, accountability, and ethics? |



