Project Management

The Agile Enterprise

by
This blog will explore agility at the enterprise level, examining how agile principles can be implemented throughout the organization—and in departments other than IT.

About this Blog

RSS

Recent Posts

Seven at One Blow: Lessons for Agile Teams and the Pitfalls of Story Points Misunderstanding

Lessons from the Emperor’s New Clothes: Rethinking Agile Transformation

Transparency in Backlog Prioritisation for AI Features

Balancing Model Complexity vs Interpretability, Finding the Sweet Spot in Machine Learning

Fairness vs Performance Trade-Offs in Agile Delivery

Categories

Agile, Artificial Intelligence, Benefits Realization, Change Management, Communications Management, Complexity, Consulting, Decision Making, Disciplined Agile, Diversity, Earned Value Management, Estimating, Ethics, General, Governance, History, Innovation, Knowledge Management, Leadership, Lessons Learned, Metrics, Organizational Culture, Product Management, Risk Management, Scope Management, Scrum, Social Impact, Stakeholder Management, Teams, Testing/Test Management

Date

Risk Management in Agile vs. Traditional Approaches—A Code of Ethics Perspective

linkedin twitter facebook Request to reuse this  
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
  1. Continuous Risk Identification
  2. Risks are surfaced frequently—during daily stand-ups, sprint planning, reviews, and retrospectives. This ongoing dialogue ensures risks are never ignored or sidelined.
  3. Shared Ownership and Collaboration
  4. The Agile philosophy encourages the entire team to participate in risk identification and mitigation, rather than assigning sole responsibility to one individual.
  5. Iterative Response and Adaptation
  6. Risks are addressed incrementally, with strategies evolving each sprint. This enables rapid adaptation to new threats and opportunities.
  7. Transparent Communication
  8. Agile teams foster open discussions about risks, making it easier to escalate concerns and enact mitigation strategies swiftly.
Traditional Risk Management Approach
Although there is no guidance or a prescriptive approach to risk management, traditional project management methodologies follow a similar pattern:
  1. Formalised, Upfront Planning
  2. Risk identification and analysis are largely front-loaded at project initiation, with updates at major milestones.
  3. Centralised Accountability
  4. Typically, a project manager or risk officer owns the risk management plan, with responsibility concentrated rather than shared.
  5. Structured Documentation and Reporting
  6. Risks are logged, classified, and tracked in formal registers. Communication occurs through scheduled reports and review meetings.
  7. Periodic Review
  8. Risk management activities are revisited at defined intervals, which may delay the recognition and response to new risks.
PMI Code of Ethics: A Comparative Lens
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:
  • Responsibility: Agile promotes proactive responsibility from all team members. Traditional methods can sometimes lead to ethical lapses if risk management is perceived as a responsibility of the project manager only.
  • Respect: Agile fosters respect for diverse perspectives in risk discussions, while some traditional approaches may limit input because of a hierarchical and conservative organisational structure, potentially missing important viewpoints.
  • Fairness: Agile openness helps ensure that risks affecting all stakeholders are considered, aligning with PMI’s fairness principle. Centralised traditional models may unintentionally sideline minority or less vocal interests.
  • Honesty: Agile promotes a culture of transparency that encourages honest, real-time sharing of issues, while the formality of traditional methods can sometimes create pressure to delay or soften risk disclosures.
Bottom line
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?
Posted on: May 22, 2026 02:02 AM | Permalink | Comments (3)

Agile “Transformation Theatre”: Beyond the Buzzwords

linkedin twitter facebook Request to reuse this  
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 Only

Some organizations claim to have adopted Agile, but little has changed in practice:
  • Command-and-Control Structures Persist: Teams are still micromanaged, decisions flow top-down, and true empowerment is lacking.
  • Agile as Justification for Tough Decisions: Agile language is used to rationalize layoffs, increased workloads, or faster delivery demands—none of which align with Agile’s original intent of sustainable pace and team well-being.

The Ethical Concern: Branding vs. Values

When Agile becomes a branding exercise, its values—collaboration, transparency, continuous improvement—are sidelined. The core question emerges:
  • Is Agile being used as a label, or is it truly guiding decision-making and culture?
Superficial adoption can lead to cynicism, disengagement, and ultimately, failure to deliver real business or customer value.

The Hot Trend: Exposing “Fake Agile” and Reclaiming Integrity

The Agile community is pushing back. Coaches, leaders, and practitioners are increasingly calling out “fake Agile” and insisting on:
  • Authentic leadership buy-in that supports self-organization and empowerment
  • Alignment with the Agile Manifesto, not just process checklists
  • Transparent communication about what’s changing—and what isn’t
  • Continuous feedback to keep transformation efforts honest and grounded
The Bottom Line:
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?
Posted on: May 11, 2026 11:23 PM | Permalink | Comments (3)

AI and Agile Decision-Making: Navigating the New Frontier

linkedin twitter facebook Request to reuse this  
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 Pitfalls

AI tools can analyse vast amounts of data at lightning speed, surfacing patterns and recommendations that might escape human notice. In Agile, this means:
  • Automated backlog prioritization based on predictive analytics
  • Estimation models that predict effort and risk
  • Code suggestions to accelerate development
But when decisions become algorithm-driven, teams must ask: Are we outsourcing critical thinking to machines? And what happens when those algorithms are flawed?

The Risk of Bias and Blind Trust

AI 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:
  • Trust AI recommendations without question, sidelining human judgment
  • Overlook the origins of training data, potentially using ethically dubious sources

Key Ethical Questions

  • Who is accountable—the team or the tool? When an AI-generated estimate causes a project to miss its target, who takes responsibility?
  • Are AI recommendations being blindly trusted? Agile is built on collaboration and critical thinking; over-reliance on AI undermines these values.
  • Is data ethically sourced? Transparency about where and how training data is collected is crucial for building trust.

Moving Forward: Human-Centered AI in Agile

The future of Agile decision-making with AI isn’t about replacing teams but augmenting them. The most effective organizations are:
  • Treating AI as a collaborative partner, not an unquestioned authority
  • Regularly reviewing and challenging algorithmic recommendations
  • Demanding transparency from vendors about training data and model limitations
The Bottom Line:
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?
Posted on: May 11, 2026 10:21 PM | Permalink | Comments (3)
ADVERTISEMENTS

"[Musicians] talk of nothing but money and jobs. Give me businessmen every time. They really are interested in music and art."

- Jean Sibelius, explaining why he rarely invited musicians to his home.

ADVERTISEMENT

Sponsors