Project Management

Please login or join to subscribe to this thread

What steps would you recommend to balance the benefits of AI with the need to preserve meaningful human roles in Agile environments?

linkedin twitter facebook   Agile   Ethics   Risk Management  
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia

Agile methodologies have changed, some would say revolutionized, the way product teams collaborate, adapt, and deliver value. At the heart of Agile software development, and in recent years of Agile project delivery, is the belief in empowered individuals, cross-functional teams, and a culture of continuous improvement. However, as Artificial Intelligence (AI) permeates Agile environments—automating roles, analysing workflows, and even facilitating Scrum ceremonies—it may fundamentally alter the human experience in work environments. This blog post explores the nuanced impact of AI on human roles and team dynamics within Agile delivery environments, drawing on principles from the PMI Code of Ethics and Professional Conduct, insights from thought leaders like Ron Jeffries, research articles published on ResearchGate.net, and risk management standards to frame risk management in the evolving landscape of Agile product and project delivery.

h3Dehumanization of Agile Roles Due to AI Automation/h3

The Manifesto for Agile Software Development recommends “individuals and interactions over processes and tools.” Yet, as AI systems take on tasks such as Product Backlog prioritization, Sprint planning, and performance tracking, there’s a risk that team members become seen as interchangeable resources rather than unique contributors. Ron Jeffries, one of the original signatories of the Agile Manifesto, warns against reducing people to “cogs in a machine.” The PMI Code of Ethics emphasizes respect, fairness, and honesty—qualities that can be undermined if automation strips away human judgment and empathy from Agile roles.

Dehumanization occurs when the unique contributions, intuition, and creativity of team members are overshadowed by algorithmic decision-making. Paul Kidd, the author of the first book that introduced the term Agile in relation to product development, notes that organizations must guard against “the tyranny of systems that erode the value of human insight.”

Blog post: Human Impact and Team Dynamics in the Age of AI-Driven Agile

ProjectManagement.com - The Agile Enterprise
Sort By:
avatar
Robert Snyder Founder & President| Innovation Elegance, LLC Chicago, Il, United States
The Agile Manifesto cites, "Working software is the primary measure of progress."

The manifesto does not comment on "humanization."
Humanization might qualify as an appendage to the agile community.
Humanization and empathy were (are) not in scope of the manifesto, and now some of us (not everyone, clearly) are trying to play catch-up to that omission.

Humanization = humans have a seat at the table.
De-humanization = humans do not have a seat at the table.

Would the agile community want to "unlearn" what it so formally defined as its primary measure of progress?
If so, what should be agile's primary measure of progress?

Stelian, your title uses the phrase, "meaningful human roles."
...
2 replies by Stelian ROMAN
Jul 20, 2026 6:39 PM
Stelian ROMAN
...
The so called 'Agile Manifesto' should be correctly referred as Manifesto for Agile SOFTWARE DEVELOPMENT". Most principles are specific to software development, and activity done by, most of the time, weird people. True software development is an art and like most good artists, software developers are not renowned for their social skills.
Jul 20, 2026 6:43 PM
Stelian ROMAN
...
An empirical observation in the project world: most people talking about Agile have no idea that Agille is more than 4 paragraphs. Individuals and interactions morphed in frameworks and Jira.
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia
Jul 20, 2026 12:39 PM
Replying to Robert Snyder
...
The Agile Manifesto cites, "Working software is the primary measure of progress."

The manifesto does not comment on "humanization."
Humanization might qualify as an appendage to the agile community.
Humanization and empathy were (are) not in scope of the manifesto, and now some of us (not everyone, clearly) are trying to play catch-up to that omission.

Humanization = humans have a seat at the table.
De-humanization = humans do not have a seat at the table.

Would the agile community want to "unlearn" what it so formally defined as its primary measure of progress?
If so, what should be agile's primary measure of progress?

Stelian, your title uses the phrase, "meaningful human roles."
The so called 'Agile Manifesto' should be correctly referred as Manifesto for Agile SOFTWARE DEVELOPMENT". Most principles are specific to software development, and activity done by, most of the time, weird people. True software development is an art and like most good artists, software developers are not renowned for their social skills.
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia
Jul 20, 2026 12:39 PM
Replying to Robert Snyder
...
The Agile Manifesto cites, "Working software is the primary measure of progress."

The manifesto does not comment on "humanization."
Humanization might qualify as an appendage to the agile community.
Humanization and empathy were (are) not in scope of the manifesto, and now some of us (not everyone, clearly) are trying to play catch-up to that omission.

Humanization = humans have a seat at the table.
De-humanization = humans do not have a seat at the table.

Would the agile community want to "unlearn" what it so formally defined as its primary measure of progress?
If so, what should be agile's primary measure of progress?

Stelian, your title uses the phrase, "meaningful human roles."
An empirical observation in the project world: most people talking about Agile have no idea that Agille is more than 4 paragraphs. Individuals and interactions morphed in frameworks and Jira.
avatar
Robert Snyder Founder & President| Innovation Elegance, LLC Chicago, Il, United States
Thank you, Stelian. I think a Venn Diagram that proposes the intersection of Ambiguity, Agile, AI, and Dehumanization would be an interesting four circles. My only confidence about such a diagram is that there is significant overlap with ambiguity and agile.
avatar
Satyananda Sahu Senior Engineering Manager| Immediate Joiner - Unemployed, Seeking Opportunity Bengaluru, Karnataka, India
In the era of AI, teams increasingly expect to leverage its capabilities while balancing the benefits with the need to preserve meaningful human roles in Agile environments. Leaders should emphasize humanity and human connection, ensuring that AI is used as an assistant rather than a replacement.

Of course, there is a cost to adopting AI. That cost should be managed within the project budget, not by replacing human resources, but by aligning expenses with organizational benefits. Another approach could involve cost optimization, for example, adjusting increments or temporarily pausing salary hikes, rather than reducing headcount and stopping hiring.

Human resources should not feel threatened by AI. Instead, they should view it as a supportive tool or an assistant that makes work easier, enhances productivity and improves work life balance.

Please login or join to reply

Content ID:
ADVERTISEMENTS

The smallest feline is a masterpiece.

- Leonardo da Vinci

ADVERTISEMENT

Sponsors







Newsletters

Jul 8: Stop Negotiating, Start Reframing
Jun 24: Acumen Is a Process, Not a Place
Jun 17: 7 Ways to Show Business Acumen Every Day

See all newsletters