Executives aren't asking "are we busy?" They're not asking "are we shipping features?" They're asking one question: Are we predictable? Do the sprint commitments we make to the business actually hold up?

Most agile teams can't answer that. Not because the data doesn't exist — it does, sitting in Jira, Azure DevOps, or a spreadsheet right now. Because nobody has built the engine to surface it.

In Episode 12, Rick introduces PACE — the Predictability and Capacity Engine — the third AI agent in his production system series. PACE tells you the truth about your agile teams: not just what they delivered, but whether they're getting more or less disciplined over time, and exactly why.

The Metric Problem: Velocity, burn down, and story points are lagging indicators. They show what happened. They don't tell you why stories slipped, whether you're improving or degrading, or what to do about it. Velocity going up might just mean you're getting faster at rolling unfinished work to the next sprint.

The Distinction That Changes Everything: Is the problem capacity (team size, sprint commitment) or readiness (stories entering sprint without clear requirements, designs, or resolved dependencies)? You cannot fix a readiness problem by adding people. PACE separates them — every sprint, every team, over time.

Two Metrics That Actually Matter:

📊 Slide Rate — % of committed stories that don't finish in their sprint. Target: under 10%. Warning: above 20%.

📊 Readiness Debt — % of stories entering sprint unready. This is a leading indicator. 40% readiness debt will cause slide. Not if. How much.

The Real Client Story: Large financial services company. 43 sprints. 48,621 Jira issues analyzed. Surface metrics looked healthy — velocity up, cost per story point down. PACE found the team wasn't getting worse at execution. They were getting worse at readiness — and it was accelerating. Slide rate climbed from 11.8% to 18% to 28% for the new team. The instinct was to ask "how do we increase velocity?" PACE revealed the real question: "Why are we accepting unready work?"

Four PACE Deliverables:

• Color-coded sprint dashboard (green/yellow/red by slide rate and readiness thresholds)
• Best and worst sprint identification (best = proof the team CAN be predictable; worst = investigation targets)
• Trend narrative ("slide rate increased from 10% to 25% — this is a process problem, not a people problem")
• Targeted action recommendations based on what the data actually shows

Rick's Signature Metric: Cost Per Story Point Not just "did velocity increase?" but "did we get more done per dollar?" When you add 40 people, PACE shows whether you actually got more efficient — and what additional work was accomplished. Metrics that were previously impossible to calculate.

The Discipline Paradox: Discipline feels like friction. Readiness checks, pushing back on unready stories — it feels like slowing down. But discipline is what makes teams fast. When stories enter ready, they complete on time. When sprints finish clean, velocity stabilizes. When commitments hold up, stakeholders trust you. PACE measures that discipline.

Portfolio Scale: Run PACE across 10, 20, or 100 teams. Compare Team A (8% slide) to Team B (30% slide) on similar work. Spread what works. Organizational learning at portfolio scale — from data that already exists in your sprint tools.

PACE + ARIA: ARIA (Episode 10) = project-level health. PACE = team execution discipline. Together they answer: "Is this project healthy?" and "Is this team predictable?" PACE's forward-looking health check flags current sprint issues before the sprint closes — no more waiting until it's too late.

Next Episode: Gatekeeper — the portfolio intelligence agent that decides which projects should even start. Most organizations say yes to too many things. When everything is a priority, nothing is. Gatekeeper forces the hard conversations before commitment, not after.

Remember: Discipline isn't friction. It's what makes you fast.

You gave a number in a hallway once. Maybe a conference room. Maybe a Zoom call with the CFO. You didn't have the requirements. You didn't have the team's input. But you gave a number — and from that moment forward, it wasn't an estimate anymore. It was a commitment.

Bad estimates don't happen because PMs are bad at math. They happen because we're asked to make precision commitments at the exact moment we know the least. And then we spend the rest of the project defending a number we never should have been asked to give.

In Episode 11, Rick introduces Atlas — the AI estimation agent built and deployed in production to solve the estimation problem at its root.

What Atlas does:

• Maintains a versioned practice library — every service type your org delivers, with roles, rates, phases, modules, and three-scenario effort estimates per component
• Guides PMs through a structured estimation conversation, module by module, grounded in your delivery history
• Produces three-scenario PERT estimates (optimistic, most likely, pessimistic) with fully formula-driven Excel workbooks — not a single number, a defensible range

Two modes. One engine. Standard workflow: you know the project shape, Atlas builds from the practice library. Discovery mode: you hand Atlas an RFP or requirements document and she analyzes it, suggests component counts, and asks you to validate before a single hour is estimated.

The 500-requirements demo: Real Salesforce implementation. Atlas ran 500 requirements through discovery mode, returned component counts (4 data objects, 11 workflows, 20 scripts, 13 reports, 23 custom fields), generated a structured assumptions document for architect review, and produced a third-revision estimate — in about one hour total. PERT output: 1.1Mto5.7M range, $1.8M expected value. What used to take days of line-by-line senior-architect review.

Why three scenarios beat one number: A single estimate creates false precision. Three scenarios communicate uncertainty honestly, give clients room to understand what drives the number, and set up scope conversations that are evidence-based — not subjective. "We estimated 11 workflows, there are 17" is a defensible conversation.

The RFP scenario: Client needed componentized pricing in their specific format by Friday. Atlas took the RFP, the existing estimate, and the client's format — and produced a structured response with assumptions, PERT parameters, and best/most likely/worst case. Wednesday to Friday. Done.

The Atlas-ARIA closed loop: Atlas builds the estimate at the start. ARIA protects it during execution. When the project closes, actuals update the practice library AND feed ARIA's risk database. Both systems get smarter. Organizational learning encoded into systems that don't forget.

The transformation: Estimation from 4 hours to 10 minutes. From PM-to-PM variance to organizational consistency. From hedging to authority. From "I think it's around this" to "here's what it costs, here's why, here's the math."

Next episode: PACE — the Predictability and Capacity Engine. Portfolio-level agile predictability, sprint commitment discipline, and readiness debt.

#ProjectManagement #AI #Estimation #PERT #PMO #ArtificialIntelligence #PMP #Agile #PortfolioManagement #AIDrivenPM #Atlas #ScopeControl

For nine episodes, we taught you how to use AI. Now we're showing you what we built with it.

Episode 10 marks a major series pivot. Rick A. Morris introduces ARIA—the Advanced Risk Intelligence Agent—a production system running on real client projects right now. Not a proof of concept. Not a demo. Live.

The 2008 Vision: In 2008, Rick wrote two books describing the future of PM: organizational memory systems that captured lessons learned from every project and automatically applied them to new ones. Mathematical risk profiles based on actual history. A database that weighted patterns by severity and repeatability.

What killed it: The manual effort. When the person maintaining the system left, the knowledge left with them.

What changed in 2024: Large language models finally caught up to the idea.

The Problem with Current Risk Management:

• Risk register templates unchanged for 20 years
• Probability/impact scores based on gut feel
• Lessons learned filed away and forgotten
• "We've been doing this for decades. It's absolutely insane."

Why ARIA Is Different from ChatGPT: ChatGPT gives you generic PMBOK-based risk lists. ARIA knows YOUR organization's history:

• That your vendor management breaks down on projects over $2M
• That your design phase runs 30% long with remote teams
• That your change control only works with a specific executive sponsor

The Math: PERT Methodology Developed by the US Navy for the Polaris missile program. Three scenarios: Optimistic, Most Likely, Pessimistic (pulled from your historical database). Expected Value = (O + 4M + P) ÷ 6. Statistically sound. Not a guess.

ARIA's Six Modes:

1. Lessons Learned Ingestion - Fuel for everything
2. Risk Assessment - Full Excel workbook in minutes
3. Risk Coach - Targeted guidance in the moment
4. Project Closeout - Structured interview, closed loop
5. Project Health Check - 8-dimension color-coded assessment
6. Maintenance - Database quality management

Live Demo Results: Dynamics 365 implementation, 2.1M(cut222.7M), fixed price, thin requirements, like-for-like ERP replication.

ARIA's immediate flag: "These characteristics align almost exactly with the single highest-severity record in the entire database."

10 minutes later: Excel workbook with 129 business days contingency, $1.43M (68% of contract), confidence band of 91-167 days, full PERT calculations, complete risk register with mitigation strategies, and an executive narrative—presentation ready.

The Credibility Difference: "I think we need a buffer" vs. "This project shares characteristics with 12 historical engagements. Those engagements slipped an average of 68 business days. Here's the data."

The Closing Truth: ARIA is your organization's memory. She doesn't forget. She doesn't retire. Every project that closes makes every future risk assessment smarter. This is the closed loop PMBOK has always described but we've never had the tools to execute—until now.

Episode Timestamps:

• [00] Series pivot: from theory to production systems
• [02] The 2008 vision and why it failed
• [05] The problem with current risk management
• [08] Why ARIA is different from generic AI
• [09] PERT methodology explained
• [11] ARIA's six modes walkthrough
• [14] Live risk assessment demo: Dynamics 365 manufacturing implementation
• [20] Excel output walkthrough: executive summary, PERT calculations, risk register
• [22] What this means for PM credibility and the profession

Resources: PMThatWorks.com | YouTube - AI Driven PM

Next Episode: Atlas—the estimation engine. Front-end estimates built with the same rigor as ARIA's risk management. Practice libraries, PERT modeling, production-ready workbooks.

Subscribe if you're ready to see what AI-powered PM actually looks like in production.

Remember: AI shouldn't replace project managers. It should amplify us.

#ProjectManagement #AI #RiskManagement #PERT #PMO #AgentBuilding #ArtificialIntelligence #ARIA