By Markus Kopko, PgMP®, PMP®, PMI-CPMAI™
April 9, 2026
For the past two years, AI in project management meant one thing to most practitioners: a better assistant. Summarize this meeting. Draft that status report. Generate a risk list. These are NLP (natural language processing) tasks, and they are useful. But they represent only one of the seven AI patterns that apply to project work (see article 4, The 7 Patterns Every Project Manager Should Know in the series). The next shift is different in kind, not degree.
Agentic AI describes systems that do not wait for prompts. They plan, execute multi-step workflows, adapt when conditions change, and take actions within defined boundaries. MIT Sloan and Boston Consulting Group reported in their 2025 global survey that agentic AI reached 35% organizational adoption in just two years, faster than traditional AI (72% over eight years) or generative AI (70% over three years). McKinsey’s 2025 State of AI survey found 23% of organizations are already scaling agentic systems, with another 39% experimenting. Technology is moving faster than most program management offices have governance structures to accommodate.
For program managers, this is not a technology curiosity. It is a structural change in how programs are coordinated, monitored, and governed.
What Makes an Agent Different from a Tool
The distinction matters. A tool responds to a prompt and produces an output. An agent receives a goal and determines the steps to achieve it. A tool requires the project manager to decompose the work. An agent decomposes the work itself.
In practice, this means an AI agent assigned to monitor program health does not wait for a weekly status request. It continuously reviews schedule data across projects, compares resource allocations against plan, identifies dependencies at risk, and surfaces a synthesized program health assessment when conditions cross defined thresholds. The program manager reviews the assessment and decides. The agent did the coordination work that previously consumed hours of analyst time.
This is not science fiction. PwC’s May 2025 AI Agent Survey found that 79% of organizations report some level of AI agent adoption. Of those, 66% report measurable productivity gains. The KPMG AI Quarterly Pulse Survey tracked agent deployment surging from 11% to over 26% of organizations in 2025. The adoption curve is steeper than any prior enterprise technology wave.
Three Program Management Use Cases
AI agents apply to program management in three areas where coordination complexity is highest.
1) Cross-Project Dependency Monitoring
Programs fail at interfaces. The integration point between Project A’s data migration and Project B’s application deployment is where schedules collide. An AI agent monitors these interfaces continuously: tracking deliverable status across projects, flagging when one project’s delay creates a downstream risk for another, and generating impact assessments before the program manager’s next review cycle.
The agent does not resolve the conflict. It detects it earlier than a human coordinator reviewing spreadsheets on a weekly cadence.
2) Resource Allocation Across the Program
Resource contention across program components is the most common source of schedule variance in multi-project environments. An optimization agent evaluates current allocations, compares them against project priorities and skill requirements, and generates reallocation scenarios when conflicts emerge.
The program manager still makes the allocation decision. The agent reduces the analysis cycle from days to minutes and ensures that no conflict goes undetected because someone forgot to check a shared resource’s calendar.
3) Stakeholder Communication Synthesis
Program managers spend a disproportionate amount of time aggregating status information from component projects into a coherent program narrative. An NLP agent collects status updates from project managers, identifies variances from the program baseline, detects sentiment shifts in stakeholder communications, and generates a draft program report that the program manager reviews and refines.
This is not replacing the program manager’s judgment on what to communicate and how. It is eliminating the hours spent collecting, collating, and reformatting data from multiple sources before that judgment can be applied.
The Governance Problem Agents Create
Every benefit of AI agents comes with a governance cost. When AI was limited to generating text on demand, oversight was straightforward: review the output before using it. When AI agents take actions autonomously within workflows, the oversight model must change.
Three governance questions become urgent for program management:
First, decision boundaries. Which decisions can an agent make independently, and which require human approval? A scheduling agent that adjusts task sequences within a project may operate with broad autonomy. An agent that reallocates budget across program components requires explicit approval. The boundary must be defined before deployment, not discovered after a misallocation.
Second, accountability. When an agent takes an action that produces a negative outcome, who is accountable? The PMBOK® Guide, Eighth Edition, answers this through its principle of leading accountably: the program manager. AI agents do not change who is responsible. They change what the person responsible must oversee. Accountability does not transfer to the tool.
Third, auditability. Every agent action must be traceable. If a dependency monitoring agent surfaces a risk that leads to a schedule change, the rationale chain must be reconstructable: What data did the agent evaluate? What threshold triggered the alert? What alternatives were considered? Without this traceability, program reviews become exercises in trusting a black box.
MIT Sloan’s 2025 research found that among organizations with extensive agentic AI adoption, 45% expect reductions in middle management layers. That is a structural reorganization, not a productivity gain. For program management offices, this is not a hypothetical threat. It is a planning consideration. PMOs that establish governance-led AI adoption before agents become the default will define the function. Those that do not will find the function defined for them.
The near-term evolution adds another layer of complexity. The future is not a single agent assisting a program manager. It is multiple specialized agents coordinating with each other: a scheduling agent, a resource agent, a risk agent, and a communications agent, each operating within its defined scope but exchanging information and triggering actions across the program.
KPMG’s research identified system complexity as the number one deployment challenge for organizations scaling agentic AI. Multi-agent orchestration, reliability, and traceability now surpass all other obstacles. For program managers, this is a familiar pattern: managing complex interdependencies is what program management is. The difference is that some of those interdependencies are now between autonomous systems, not between project teams.
As a member of the Core Development Team for the PMI Standard on AI in Project, Program, and Portfolio Management, I see this convergence directly. The governance structures that make multi-agent coordination reliable are the same structures that make program management effective—providing clear decision rights, defined escalation paths, strong accountability frameworks, and consistent performance monitoring. The discipline remains the same, only the scale changes.
Where to Start
Program managers do not need to deploy multi-agent systems tomorrow. The practical starting point is a single agent addressing the highest-friction coordination task in your program: status aggregation, dependency tracking, resource conflict detection, or benefits realization tracking across program phases.
The governance framework from Article 1 in this series, AI Governance for Project Teams, applies directly: set the rules before deploying the capability. The human-in-the-loop principle from Article 2 applies with added urgency: agents that act autonomously require more oversight structure, not less.
Start with one agent. Define scope. Set boundaries. Audit the output. Expand from evidence, not enthusiasm.
Key Takeaways
- AI agents plan, execute, and adapt. They do not wait for prompts. This is a structural shift from AI as assistant to AI as coordination partner.
- Agentic AI reached 35% organizational adoption in two years (MIT Sloan/BCG, 2025), faster than any prior AI wave.
- Agents are most valuable where coordination complexity is highest: multi-vendor programs, distributed teams, rolling wave planning across parallel work streams.
- Every agent capability requires a governance decision: what can it decide independently, who is accountable, and how its actions are auditable.
- The PMBOK® Guide, Eighth Edition, principle of leading accountably applies with added force: AI agents do not transfer accountability. They change what the accountable person must oversee.
- Start with one agent on one high-friction task. Define scope, set boundaries, auditthe output. Expand from evidence, not enthusiasm.
This article is part of a series leading up to the IIL webcast “5 Steps to Integrate AI into Your PPM Practices: A Tactical Blueprint” on June 24, 2026. Register at: https://www.iil.com/your-ai-advantage-practice-habit-strategy/
Markus Kopko, PgMP
Markus Kopko is a strategic project and AI transformation expert with over 25 years of experience in project, program, and portfolio management. He contributes to the Core Development Team of the PMI Standard on AI in Project, Program, and Portfolio Management and served on the PMI Review Team for the PMBOK® Guide, 7th Edition. Markus holds PMP®, PgMP®, and PMI-CPMAI™ certifications and is a trainer and content creator for IIL. He delivers the course “Generative AI for Project Management” on IIL’s learning platform.
PMP®, PgMP®, and PMBOK® are registered marks of the Project Management Institute, Inc. PMI-CPMAI™ is a trademark of the Project Management Institute, Inc.
