Most AI agent projects fail not because of bad code or weak models — they fail because teams aim at the wrong part of the workflow. AI strategist Nate B. Jones argues that real work is only about 2.5% high-judgment "core" decisions, while the other 97.5% is mechanical edge work: data prep, QA, synthesis, handoffs, and packaging. Teams that try to automate the core first stall out fast. Teams that start with the edges — the boring stuff surrounding the valuable work — ship results in days, build organizational trust, and create a proven path toward eventually tackling the core. It's the same principle behind Agile: start small, deliver value fast, and expand from a foundation of demonstrated success. The fix isn't better AI. It's smarter strategy about where you start.

AI is a productivity amplifier—not a Product Owner, not a Scrum Master, and not a Developer.

Used correctly, it accelerates learning, drafting, summarizing, and exploring options. Used poorly, it replaces thinking with automation theater.

This step helps your team position AI as a supporting teammate, not a decision-maker.

AI can help—but only if the prompt is structured.

This step introduces repeatable prompt patterns that improve:

• Intent clarity

• Constraints visibility

• Acceptance criteria quality

• PO alignment

The Core Risk

When teams use AI in refinement, a common failure mode appears:

• Stories get cleaner

• Acceptance criteria get longer

• Technical detail increases

• Business intent becomes less visible

Scrum optimizes for value delivery, not documentation density.

AI must support the “why” behind the work.

The Key Principle

AI should propose:

• Possible Sprint Goals

• Possible scope groupings

• Possible dependency flags

The team still decides:

• What to commit to

• What fits capacity

• What aligns to product strategy

AI drafts.
The team commits.