Project Management

The Agile Enterprise

by
"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

Recent Posts

Concealing Technical Debt for Short-Term Speed: An Ethical Examination

Transparency, Truthful Reporting, and Risk Visibility: The Ethics of Agile Delivery

Navigating the New Agile Landscape: Fairness, Bias, and Ethical Technology Use. An Ethical Reflection

Accountability and Responsible Decision-Making in Agile Projects/n Ethical Reflection.

Transparency, Accountability, and Trust in Agile Decision-Making: The Ethical Imperative

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, Using PMI Standards

Date

Data Privacy in Agile Practices: Balancing Speed, Insight, and Ethics

linkedin twitter facebook Request to reuse this  
Agile thrives on fast feedback loops and rapid iteration. Teams use analytics, user tracking, and telemetry to inform decisions and deliver value quickly. But with these tools comes a critical responsibility: respecting the privacy of users whose data powers this feedback.
The Ethical Concerns: Speed vs. Consent
  • Are users truly aware of the data being collected during experiments or regular usage?
  • At what point does continuous experimentation—like feature toggling—cross the line into invading privacy?
Too often, the drive for rapid insights can overshadow clear communication and respect for user autonomy. If data collection is opaque or experimentation is intrusive, organizations risk eroding trust and violating ethical boundaries.

Privacy-by-Design: The Hot Trend in Agile
Forward-thinking teams are now integrating privacy-by-design into their Agile product cycles. This means:
  • Building transparency and consent into user flows from the start
  • Limiting data collection to what’s essential
  • Regularly auditing analytics and experimentation for privacy risks
  • Making privacy a standing topic in sprint reviews and retrospectives
By weaving privacy considerations into every sprint, teams can innovate quickly without sacrificing user trust.

The Bottom Line
Agile’s reliance on data doesn’t have to come at the cost of privacy. When privacy-by-design is part of the process—not an afterthought—teams can deliver valuable products ethically and sustainably.

How does your team balance the need for rapid feedback with a commitment to user privacy?
Posted on: May 12, 2026 08:16 PM | Permalink | Comments (2)

Team Autonomy vs. Organisational Control: The Realities of Empowerment in Agile

linkedin twitter facebook Request to reuse this  
Agile frameworks are built around the promise of self-organising teams—groups that take ownership of their work, solve problems creatively, and adapt quickly. But in practice, many organizations still struggle to let go of the reins. Leadership often exerts hidden control, and team autonomy can turn out to be more of a slogan than a reality.
The Tension: Autonomy or Accountability Without Power?
On paper, Agile gives teams the authority to decide how to do their work. Yet, leaders and managers may still:
  • Impose roadmaps, deadlines, or technical constraints
  • Override team decisions in the name of “alignment”
  • Require extensive reporting or approvals
  • Hire and fire team members
  • Control team's budget
This creates an ethical dilemma: Are teams truly empowered, or are they simply accountable for results without having real authority to shape outcomes? Superficial autonomy can lead to frustration, disengagement, and a lack of genuine innovation.

Redefining Leadership: Servant Leadership vs. Control
The hot trend in Agile is a move away from command-and-control toward servant leadership. Instead of directing or micromanaging, servant leaders:
  • Remove obstacles and support team growth
  • Foster trust and psychological safety
  • Encourage experimentation and learning
  • Act as guides rather than gatekeepers
In principle, as defined by Greenleaf in 1970, a Servant Leader emerges from the team but in practice, most of time, is appointed by (senior) management. Therefore, it is crucial that the leader, the team and last but not list their manager, understand that Agile doesn’t mean a lack of structure or accountability—instead, leadership’s role is to empower teams to own both their process and outcomes.

The Bottom Line
True team autonomy requires more than just words. Organizations must back up their Agile aspirations with real empowerment, redefining leadership as a force for support rather than control. Only then can teams deliver the creativity, resilience, and value Agile promises.

Where do you see the line between healthy leadership support and hidden control in your team or organization?
Posted on: May 12, 2026 07:11 PM | 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)

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)
ADVERTISEMENTS

"It isn't necessary to be rich and famous to be happy. It's only necessary to be rich."

- Alan Alda

ADVERTISEMENT

Sponsors







Newsletters

Sep 2: Busy is Not a Symptom of Ambition
Aug 26: Stop Writing Status Reports
Aug 19: PM Lessons From the Himalayas

See all newsletters