AI in Project Management
Domain 1 tests how AI changes project management practice: selecting AI use cases that augment planning, scheduling, risk sensing, reporting, and stakeholder communication, while keeping human accountability for baselines and approvals.
Core rules
- AI is decision support, not a transfer of accountability. The project manager still owns scope, cost, schedule, quality, and escalation.
- Strong use cases are data-rich, repetitive, measurable, and reversible: forecast variance, cluster issues, draft status reports, summarize decisions, detect requirement drift.
- Weak use cases involve unreviewable high-stakes calls, missing feedback data, or decisions that cannot be explained to stakeholders.
- Human-in-the-loop review is required where errors affect people, compliance, safety, or contractual commitments.
- Distinguish using AI in projects from managing AI projects; this domain focuses on the former, though controls overlap.
Worked example
A project manager has 18 months of issue logs and wants earlier slippage warnings. AI clusters issues and predicts delay risk. Reasoning: the data are sufficient for a decision-support signal; the manager validates drivers with leads, keeps baseline changes in change control, and monitors false negatives. The model never auto-approves schedule changes.
Traps
- Treating a forecast as a commitment.
- Automating a broken process.
- Ignoring data provenance and sample bias.
- Buying a tool before defining the decision and metric.
- Forgetting adoption costs and workflow redesign.