Project Management

Home / Blogs / The Agile Enterprise /

The Agile Enterprise

"The Agile Enterprise" explores Agility at the Enterprise level, examining how Agile principles can be implemented throughout the organization beyond IT. The blog is inspired by the concept of an Agile Enterprise, introduced by the Agile Manufacturing Forum (1991) and the Manifesto for Agile Software Development (2001). Agility is examined from a Project Management perspective with a focus on areas not covered by frameworks that emerged from the work of small software development teams, such as Risk Management, Ethics, Organisational Change Management and Financial Management.

General | History | Metrics | show all posts

About this Blog

RSS

Date

newer posts

older posts

Distributed Teams & Cultural Ethics: Building Inclusive Agile Practices

Categories: Scrum, Agile, Leadership, Ethics, Diversity, Teams, Organizational Culture

Agile is now truly global. Distributed teams bring together diverse perspectives, creative problem-solving, and a richer tapestry of experience. But with this diversity comes the challenge—and opportunity—of navigating cultural differences in communication, authority, and participation.

The Diversity Dilemma: Communication and Hierarchy

Direct vs. Indirect Feedback: Some cultures value candour and challenge, while others prefer subtlety and harmony. Agile’s emphasis on open feedback (like in retrospectives) may clash with norms in more indirect cultures, making it hard for everyone to participate equally.
Authority and Hierarchy: Agile encourages flat structures and shared ownership. But for team members from cultures with strong respect for hierarchy, challenging a superior’s idea or speaking up in group settings may feel risky or inappropriate.

Ethical Issues in Global Agile Teams

Dominance of One Culture: When Agile ceremonies and practices are shaped by a single cultural lens—often Western norms—other perspectives can be overshadowed. This creates a risk of unintentionally excluding those who communicate differently or hold alternative views on leadership.
Exclusion of Quieter Voices: In remote ceremonies, those less comfortable with the dominant language or style may remain silent. Valuable insights are lost, and psychological safety suffers.

The Hot Trend: Inclusive Agile and Culturally Aware Facilitation

Forward-thinking organizations are embracing inclusive Agile practices that honour cultural differences and foster true participation. This includes:

Rotating facilitation to balance power and encourage diverse approaches
Multiple feedback channels (chat, polls, anonymous boards) to ensure everyone can contribute, regardless of language or personality
Cultural awareness training for Scrum Masters and Agile coaches
Explicitly inviting quieter voices, recognizing that silence may signal discomfort, not agreement

The Bottom Line:
Agile thrives when every voice is heard. As teams span continents and cultures, success depends on actively designing ceremonies and systems that include, rather than exclude. The future of Agile isn’t just global—it’s genuinely inclusive.
How is your team adapting Agile to fit your unique culture?

Posted on: May 11, 2026 11:13 PM | Permalink | Comments (3)

Velocity Misuse and Performance Pressure: Rethinking Agile Metrics

Categories: Metrics, Scrum, Scope Management, Agile, Benefits Realization, Complexity, Decision Making, Ethics, Teams, Organizational Culture, Estimating, Governance, Disciplined Agile, Product Management

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)

AI and Agile Decision-Making: Navigating the New Frontier

Categories: Scrum, Agile, Change Management, Leadership, Lessons Learned, Decision Making, Ethics, Teams, Organizational Culture, Governance, Artificial Intelligence, Social Impact

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)

Transparency vs. Psychological Safety in Agile: Finding the Right Balance

Categories: Scrum, Agile, Leadership, Ethics, Teams, Organizational Culture

Agile methodologies champion transparency: daily stand-ups, open retrospectives, and visible metrics are core practices that keep teams aligned and projects on track. But in the quest for openness, a delicate tension emerges—one that can affect trust, morale, and even the ethical foundation of team culture.

The Tension: Openness or Oversight?

Transparency is meant to empower. By making velocity charts, burndown graphs, and progress updates visible to all, teams can coordinate better and spot issues early. However, too much transparency can feel like surveillance rather than support. When individuals sense that every move is being tracked, psychological safety can suffer. This can lead to:

Withholding honest feedback in retrospectives for fear of blame or repercussion
Gaming metrics to avoid negative attention
Reduced experimentation and innovation as team members play it safe

Ethical Questions at Play

Are metrics a tool for support or scrutiny?
When metrics like velocity are used to help teams self-improve, they foster growth. But when they’re weaponized to judge individual performance, they erode trust.
Do retrospectives build safety or subtle pressure?
Open forums are powerful for reflection, but if team members feel coerced to agree or fear being singled out, the process can backfire.

The Shift: From Radical to Safe Transparency

The latest trend acknowledges these pitfalls. Instead of “radical transparency,” organizations are embracing safe transparency—a model in which openness is balanced with care for team well-being. This means:

Sharing information that helps, not harms
Protecting individual privacy where appropriate
Using metrics to guide, not grade
Creating retrospectives where candor is encouraged, not coerced

The Bottom Line:
Transparency is a powerful Agile value—but only when paired with psychological safety. The future isn’t less openness, but smarter openness: creating spaces where teams can share, learn, and grow without fear.
What does safe transparency look like in your team? Share your thoughts below!

Posted on: May 11, 2026 10:10 PM | Permalink | Comments (1)

Manifesto for Enterprise Agility alignment with PMI's Code of Ethics and Professional Conduct

Categories: Risk Management, Agile, Change Management, Leadership, Complexity, Consulting, Decision Making, Ethics, Organizational Culture, Governance, Social Impact, Communications Management

In one of my webinars dedicated to the Agile Enterprise,, I stated that Ethics is the foundation of Agility. This blog ia review of the recently published Manifesto for Enterprise Agility. The Agile Enterprise is not a new concept; it was coined in 1990's by the Agility Forum, a group of experts, academics, and executives that predicted the changes that the 21st Century would bring.
The new manifesto emphasizes purpose, transparency, learning, and sustainable ways of working. It can be used as ethical guardrails to make Agile commitments more explicit so Agile can’t be misused to justify “speed over integrity.”

Responsibility (own decisions, actions, consequences)

The manifesto explicitly frames disruption as requiring better decisions, adaptive plans, guardrails, and “making risk visible (and actionable).” That supports responsible stewardship of outcomes and resources, and it signals accountability rather than reckless autonomy.
Phrases like “move quickly… with incomplete data,” “cut out small decisions,” and “replace approval structures with trust” can be interpreted as bypassing due diligence. The PMI Code also carries an obligation to comply with laws, regulations, and organizational policies; the manifesto implies this via “guardrails,” but doesn’t state it.

Respect (regard for people and resources entrusted to us)

“Human centricity amidst change,” “sustainably deliver value,” “change fatigue,” and emphasis on empathy, trust, and psychological safety are directly aligned with respect for people and well-being.
The manifesto says “continuous learning” and “learning from failure,” which is positive, but it could be strengthened by stating that accountability is non-punitive while still addressing misconduct or repeated negligence. Also, “distributed talent” and ecosystem language should avoid treating partners/suppliers as interchangeable capacity.

Fairness (impartiality; avoid favoritism and competing self-interest)

“Shared enterprise outcomes over functional optimization” and “work visible” encourage objective prioritization and reduce hidden agendas. Ecosystem collaboration also supports fair dealings with stakeholders.
“Move authority to where value is created,” and dynamic funding can unintentionally increase favoritism if decision criteria aren’t transparent. The excerpt does not explicitly address conflicts of interest, procurement ethics, or equitable access to opportunities.

Honesty (truthful communications and conduct)

The manifesto repeatedly promotes visibility: “make work visible,” “progress, dependencies, and risk visible,” “govern through visibility,” and “evidence-based agility / ground-truth facts.” This is strongly consistent with honesty as PMI defines it.
The main risk is operationalizing “visibility” with metrics that get gamed; the manifesto could pre-empt that by stating metrics are used ethically (to learn, not to mislead).

Posted on: March 04, 2026 04:43 AM | Permalink | Comments (0)