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.
General | History | Metrics | show all posts

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)

Gen AI Guardrails in Agile: Responsible Use for High-Performing Teams

linkedin twitter facebook Request to reuse this  
Generative AI (Gen AI) is transforming how Agile teams collaborate, deliver, and innovate. It can accelerate backlog refinement, automate documentation, and provide insights from sprint analytics. Yet, with these opportunities come new risks—especially when fast-paced, iterative work meets powerful AI tools. By applying clear guardrails, Agile teams can harness AI’s strengths ethically and safely, all while staying true to Agile principles.

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?

Posted on: May 13, 2026 12:30 AM | Permalink | Comments (2)

Servant Leadership in the Age of Artificial Intelligence

linkedin twitter facebook Request to reuse this  
Revisiting Greenleaf’s Vision from 1970 in a Machine-Augmented World
In 1970, Robert K. Greenleaf introduced servant leadership—a philosophy that put people before power. Leaders, he argued, exist to serve their teams, not control them. Fast forward to today, and organizations are navigating the rise of Artificial Intelligence (AI)—a force reshaping how we work, decide, and lead. What does servant leadership mean in a world increasingly guided by algorithms?

WHAT IS SERVANT LEADERSHIP?

Greenleaf’s model centres on the idea that leadership is about serving first. Core principles include empathy, active listening, stewardship, commitment to growth, and building community. Unlike command-and-control models, servant leadership prioritizes people over processes—a philosophy now foundational to Agile and human-cantered workplaces.

AI: OPPORTUNITY AND ETHICAL CHALLENGE

Greenleaf’s model centres on the idea that leadership is about serving first. Core principles include empathy,
AI powers automation, analytics, and decision systems across organizations. While it brings remarkable efficiency and insight, it also raises ethical questions:
  • Will human judgment be sidelined by algorithms?
  • Can we maintain empathy and fairness in machine-driven decisions?
  • How do we ensure transparency and trust when AI systems can be "black boxes"?

SERVANT LEADERSHIP MEETS AI

  1. Human-Cantered vs. Efficiency-Cantered Decisions: AI optimizes for speed and outcomes, but servant leaders weigh long-term human impact and well-being.
  2. Empathy in a Digital World: AI simulates understanding but lacks true empathy. Servant leaders must champion genuine human connection.
  3. Transparency and Trust: Servant leadership values openness, but many AI decisions are hard to explain. Leaders must advocate for clarity and ethical use of technology.
  4. Empowerment vs. Automation: AI can empower people—or displace them. Servant leaders use AI to augment, not replace, human creativity and purpose.
  5. Bias and Fairness: AI may inherit biases from data. Ethical leaders audit systems, challenge unfair outcomes, and protect the vulnerable.

THE MODERN SERVANT LEADER

In the AI era, servant leaders are:
  • Ethical navigators, aligning technology with values
  • Human advocates, balancing automation with dignity
  • Capability builders, helping teams adapt and thrive
  • Guardians of trust and psychological safety
The Bottom Line:
Greenleaf’s vision is more relevant than ever. Servant leadership balances technological innovation with ethics and empathy—reminding us that people are the purpose, not just resources. The future belongs to leaders who blend AI with humanity, ensuring technology truly serves us all.

What challenges have you encountered in balancing technology-driven decisions with human-centred leadership in your organization?
Posted on: May 12, 2026 12:42 AM | Permalink | Comments (3)

Agile Coaches and Ethical Influence: Navigating Responsibility in Transformation

linkedin twitter facebook Request to reuse this  
Agile coaches play a pivotal role in shaping not only how teams work, but also the underlying culture and values of an organization. Their influence extends beyond ceremonies and frameworks—they impact team dynamics, leadership behaviour, and even strategic direction. With this influence comes a profound ethical responsibility.

The Coach’s Dilemma: Neutrality or Advocacy?

Agile coaches are expected to be neutral facilitators, guiding teams to discover solutions for themselves. But the reality is more nuanced:
  • Facilitators or Influencers? Coaches naturally bring their own beliefs, experiences, and interpretations of Agile. This can shape how teams adopt practices, set priorities, and make decisions.
  • Pushing Agendas? There’s a fine line between advocating for Agile values and imposing personal preferences or following organizational pressures.

Key Ethical Questions

  1. Are coaches maintaining neutrality, or are they pushing their own (or the organization’s) agenda?
  2. What should coaches do when they witness harmful practices, such as exclusion, burnout, or unethical management?
The answers aren’t always simple. Coaches must balance their duty to support teams with the need to challenge practices that contradict Agile principles or harm well-being.

The Hot Trend: Professional Ethics Frameworks for Agile Coaches

Recognizing these challenges, the Agile community is increasingly advocating for professional ethics frameworks tailored to coaching. These frameworks address:
  • Clarity of role and boundaries: Defining when to facilitate, when to advise, and when to speak up
  • Transparency and honesty: Being clear about intentions and potential conflicts of interest
  • Courage and care: Taking a stand against harmful practices, even when it’s uncomfortable
  • Continuous reflection: Regularly examining one’s own influence and impact
The Bottom Line:
Agile coaches are powerful agents of change. With that power comes the responsibility to act ethically supporting teams, resisting coercion, and upholding the true spirit of Agile. As the profession matures, ethics frameworks, like PMI's Code of Ethics and Professional Conduct, are essential for building trust and ensuring positive, lasting transformation.

How do you see the role of ethics in Agile coaching? What standards should guide this critical work?
Posted on: May 12, 2026 12:03 AM | Permalink | Comments (1)

Velocity Misuse and Performance Pressure: Rethinking Agile Metrics

linkedin twitter facebook Request to reuse this  
Agile introduced velocity as a simple tool: a way for teams to estimate how much work they can deliver in a sprint, supporting better planning and realistic forecasting. Yet, over time, velocity has been repurposed—and sometimes misused—as a performance metric, leading to unintended consequences for teams and organizations.

The Problem: Planning Tool or Performance Benchmark?

Velocity was never meant to be a Key Performance Indicator (KPI) or a tool for comparing teams. However, it’s common to see organizations:
  • Setting targets based on velocity numbers
  • Using velocity to compare teams or individuals
  • Tying incentives or recognition to velocity increases
This shift puts pressure on teams to "hit the numbers," which can lead to:
  • Gaming the system (inflating story points or splitting work unnaturally)
  • Burnout and stress from relentless demands
  • Dishonest reporting to avoid negative scrutiny

The Ethical Dilemma

When velocity becomes the yardstick for performance, teams face a fundamental question:
  • Are we incentivized to deliver real value—or just to hit metrics?
If the focus is on numbers, the true spirit of Agile—delivering customer value, learning from feedback, and adapting—gets lost. Teams may spend more time managing perceptions than solving real problems.

A New Direction: Value and Outcomes Over Output

The hottest trend in Agile metrics is a move away from output-based measurements like velocity toward value-driven and outcomes-based approaches. This shift means:
  • Prioritizing customer impact over story point accumulation
  • Measuring success by outcomes (e.g., user satisfaction, business goals achieved)
  • Rewarding learning and adaptation, not just speed
Organizations embracing this mindset are seeing healthier team cultures, more honest communication, and better results for stakeholders.
The Bottom Line:
Velocity is a useful planning tool—but it’s not a measure of team worth. The future of Agile metrics lies in focusing on value, outcomes, and ethical practices that support both team wellbeing and organizational goals.

How is your team measuring success? Are your metrics driving value—or just numbers?
Posted on: May 11, 2026 10:31 PM | Permalink | Comments (1)
ADVERTISEMENTS
ADVERTISEMENT

Sponsors







Newsletters

Jun 24: Acumen Is a Process, Not a Place
Jun 17: 7 Ways to Show Business Acumen Every Day
Jun 3: The Career Problem Facing New PMs

See all newsletters