GBMC Spring 2026 Newsletter

Artificial Intelligence is no longer an abstract or future concept for project management. It is already shaping how projects are planned, monitored, reported, and delivered—sometimes intentionally, sometimes quietly in the background, and often without a shared understanding of its implications.

Across many organizations, AI has entered project environments through scheduling tools, reporting dashboards, backlog assistants, meeting summaries, and forecasting algorithms. Yet despite this growing presence, one fundamental question remains unresolved:

How do we use AI to improve project outcomes without weakening judgment, ownership and learning?

AI is no longer just a tool
A noticeable shift in recent project environments is how teams relate to AI.
It is increasingly treated less like a standalone tool and more like a virtual team member.
Teams ask AI to summarize meetings, highlight delivery risks, suggest backlog refinements, or analyze historical performance. These uses often save time and improve visibility. For example, instead of manually reviewing dozens of status reports, a project manager may rely on AI to surface emerging risks or trends.

The danger arises when these outputs are accepted without challenge.
AI can explain what seems to be happening—but not why it matters, what should be done, or what trade-offs are acceptable. Accountability cannot be delegated.

Speed is not the same as certainty
One recurring pattern in real projects is the false confidence created by AI-generated outputs.
Forecasts, risk scores, and recommendations often appear precise, which can mask underlying uncertainty.

Consider a team that uses AI to predict a delivery date based on past velocity. The number looks convincing. Yet the model may not account for upcoming architectural changes, dependency risks, or team turnover. When such predictions are treated as commitments rather than hypotheses, disappointment is almost guaranteed.

AI increases speed. It does not eliminate uncertainty.

Prompting exposes the quality of thinking
As AI becomes more common, prompting has quietly emerged as a core project management skill. A vague request such as “analyze project risks” usually produces generic results. A structured prompt—defining scope, assumptions, constraints, stakeholders, and decision intent—leads to far more useful insight.
In practice, weak AI outputs often reveal weak problem framing.

Good prompts are not clever tricks; they are evidence of disciplined thinking.

Context is the real differentiator
Another frequent complaint is that AI outputs feel irrelevant or superficial. In most cases, the issue is not the model but the lack of project context.

AI cannot add value if it has no access to real artefacts such as:
• backlogs and work plans
• risk registers and assumptions
• delivery metrics and dependencies
• meeting decisions and follow-up actions
Once grounded in real project data, AI can begin to highlight patterns that humans may overlook—recurring bottlenecks, overloaded roles, or unrealistic sequencing. Context, not sophistication, is the true multiplier.

Where AI undermines Scrum
Scrum environments reveal both the promise and the risk of AI very clearly. When used thoughtfully, AI can support backlog refinement, preparation for sprint events, and insight generation from metrics. When used poorly, it damages the core learning loops of Scrum.

Common anti-patterns observed include:
• auto-generated user stories that dilute Product Owner intent
• AI-based forecasts treated as commitments
• retrospectives replaced by summaries rather than dialogue
• metrics used to control teams instead of enabling inspection
Scrum depends on transparency, conversation, and adaptation. These cannot be automated away without hollowing out the framework itself.

A governance question, not a technology question
As AI becomes embedded in project environments, the real issue shifts from technology to governance. Who validates AI outputs? What data is used? How are assumptions challenged?
Where does responsibility sit?

Organizations that treat AI adoption as a tooling exercise often struggle. Those that treat it as a change in decision-making discipline tend to progress more sustainably.

A final reminder
Perhaps the most important insight from real-world experience is a simple one: AI increases the speed of learning, not certainty.
Used well, AI helps teams see earlier, learn faster, and adapt sooner.
Used poorly, it creates false precision, delayed surprises, and weakened accountability.
The question is no longer whether AI will be part of project management.
It is how consciously we choose to integrate it into the way teams think, decide, and learn.