ITNOVE
WEBCAST · 16 JUN 2026
ALEX BALLARÍN · PROFESSIONAL SCRUM TRAINER

Scrum and AI

Partners or Rivals?

How a Scrum Team's work changes when AI enters the development flow.

ITNOVE
21 · POLL
QUICK POLL

What best describes your team today?

Before this session — where is your team with AI?

ITNOVE
22 · RESULTS
POLL RESULTS

Where are we as a group?

ITNOVE
02 · OPENING
THE DEBATE

"AI killed Scrum."

Two-week Sprints were designed for a world where writing code took time. That world is gone. With AI, a feature goes from idea to working code in minutes. You don't need ceremonies for that.

SE
Senior Engineer · 4
000 likes on LinkedIn

Is this right? Let's find out.

ITNOVE
03 · AGENDA
WHAT WE WILL COVER

One question. Five answers.

01
What Scrum is actually for
8 min
02
What really changes with AI
10 min
03
The logical model as a compass
7 min
04
How Scrum adapts
12 min
05
Partners or Rivals?
10 min + Q&A

Guiding question: What really changes when AI joins the team?

ITNOVE
04 · BLOCK 1
BLOCK 1 · WHERE SCRUM BELONGS

Not every problem needs Scrum.

Stacey matrix — four domains of complexity

Scrum was designed for complex problems — where neither requirements nor solution path are clear upfront.

Scrum lives here
  • Simple: Known path → Kanban is enough.
  • Complicated: Expert path → Known methodology.
  • Chaotic: No path yet → Act first, analyse later.
  • Complex: Unknown path → You discover the answer, not plan it.
ITNOVE
05 · BLOCK 1
SCRUM AS A COMPLEX PROBLEM SOLVER

Not a delivery process. A learning machine.

Mechanical delivery

Sprints are two-week output cycles.
Stories go in, code comes out, Demo is a checkpoint.

Velocity is the north star.
"Done" means code is merged.
No question is being answered.

Result: fast output, unknown direction.

Outcome compass

Each Sprint starts with a Sprint Goal — a hypothesis.
The Review is a feedback session, not a demo.

Impact is the north star.
"Done" means something was learned.
Every Sprint answers a specific question.

Result: slower on features, faster on value.

ITNOVE
06 · BLOCK 1
THE KEY INSIGHT

AI does not remove uncertainty.

The reasons Scrum was born still hold: markets shift, users surprise us, technology behaves unexpectedly.

The biggest danger for Scrum is not Waterfall, not AI — it is Scrum reduced to a meeting cadence without empiricism.

If your Sprints are answering real questions, AI makes Scrum more powerful. If they are just output cycles, AI makes the problem bigger.

ITNOVE
07 · BLOCK 2
BLOCK 2 · WHAT CHANGES WITH AI

Three models of AI-assisted development.

VIBE CODING

Prompts → working code in hours

Ideal for exploration and rapid prototyping. The developer stays in a creative flow — no boilerplate, no context switching.

Trade-off: high potential for technical debt and undefined behaviours at the edges.

SPEC-DRIVEN DEVELOPMENT

Structured specs → precise generation

The developer writes detailed specifications; the AI generates production-quality code. Less ambiguity, less debt.

Trade-off: requires disciplined thinking upfront — harder to start, much easier to maintain.

ITNOVE
08 · BLOCK 2
THE SHIFT

The bottleneck moved.

Pipeline: four stages of product development — AI accelerates Delivery, Demand Management is the new constraint

AI has dramatically expanded the throughput of Delivery — what used to take weeks now takes hours.

The constraint is no longer writing code. It is deciding what is worth building — filtering demand, framing the problem, choosing what not to do.

ITNOVE
09 · BLOCK 2
THE REAL RISK

Feature factory — on steroids.

×17
Code generated per developer
×1.3
Releases shipped
?
Validated outcomes

Speed is not the problem. Strategic disconnection is — and AI amplifies it.

  • Stakeholders push for more. Roadmaps expand.
  • Teams execute without questioning value.
  • Outcomes do not scale with velocity.
McKinsey 2023 — AI boosts code output; validated outcomes barely move
ITNOVE
10 · BLOCK 3
BLOCK 3 · THE LOGICAL MODEL AS COMPASS

AI accelerates one link. The chain has five.

Seiden logical model — Resources → Activities → Outputs → Outcomes → Impact

The logical model (Seiden) shows what connects effort to value. AI dramatically accelerates Outputs. The problem: teams celebrate output velocity as if it were outcome velocity.

Without clear Sprint Goals and Product Goals, more output just means more noise.

ITNOVE
11 · BLOCK 3
THE LAG PROBLEM

When velocity goes up, the measurement gap widens.

Strategic lag — code shipped vs validated outcomes over time

As the pace of delivery increases, the lag between what we ship and what we measure — user behaviour change, retention, conversion — grows proportionally.

Flying at ×17 speed without outcome signals is navigating blind. The faster you go, the more you need a compass.

ITNOVE
12 · BLOCK 3
OUTCOME-ORIENTED SCRUM

Product Goal and Sprint Goal as decision filters.

Product Goal

The strategic outcome the team is chasing in this phase of the product.

Not a feature list. Not a project scope.

A hypothesis about impact: "If we improve retention in the first 7 days, we will reduce churn by X."

Every backlog item is evaluated against this filter before it is even discussed.

Sprint Goal

The specific question this Sprint will answer.

Not a Sprint backlog. Not a commitment to features.

A learning objective: "We believe that adding onboarding step Y will increase day-3 return rate."

The Daily Scrum asks: are we still on track to answer this question?

ITNOVE
13 · BLOCK 4
BLOCK 4 · HOW SCRUM ADAPTS

The empirical loop remains. The frequency and focus change.

What does NOT change

The three pillars: Transparency, Inspection, Adaptation.

The need for a clear Product Goal.

The value of a cross-functional, self-managing team.

Short cycles with real feedback.

Human judgment at the decision points.

What DOES change

Sprint length can shrink — code generation is no longer the constraint.

Daily focus shifts from progress reporting to output validation.

Refinement becomes specification work — the input to AI generation.

Review shifts from feature demo to outcome conversation.

Definition of Done must rise with output speed.

ITNOVE
14 · BLOCK 4
SPRINT LENGTH AND DEFINITION OF DONE

When code generates in hours, two weeks is too long to wait for feedback.

Shorter Sprints are not about moving faster. They are about learning faster — reducing the time between a hypothesis and its first real signal.

  • Sprint Goal: a falsifiable hypothesis, not a feature commitment.
  • Product Goal: the strategic filter — visible at every Planning, Review, and Daily.
  • Definition of Done must rise with speed: automated tests, security review, observability. The bar cannot fall because delivery got cheaper.

If your DoD is the same as before AI, you are accumulating invisible risk.

ITNOVE
15 · BLOCK 4
ADAPTED EVENTS

The events evolve. Their purpose stays the same.

Daily Scrum

Shifts from progress sync to output validation and AI decision review.

Questions that matter now: Does what was generated yesterday actually meet the Sprint Goal? What decisions did the agent make that the team needs to review or override?

Sprint Review

Shifts from feature demo to outcome conversation.

Questions that matter now: What did we learn about real user behaviour? Do the signals support or challenge the Product Goal? What should we stop building?

ITNOVE
16 · BLOCK 4
THE HYBRID SCRUM TEAM

The roles evolve. The accountability stays the same.

Product Owner

Becomes a hypothesis validator, not a feature approver.

The backlog is a set of bets, not a to-do list. The PO's job is to maximise the signal-to-noise ratio: which bets are worth running this Sprint?

The key skill: translating business outcomes into testable Sprint Goals.

Scrum Master

Becomes a facilitator of human–AI learning, not a meeting scheduler.

Helps the team build the discipline to specify well, validate rigorously, and improve the collaboration loop. Removes impediments to effective supervision of AI output.

ITNOVE
17 · BLOCK 4
THE BACKLOG EVOLVES

From user stories to value hypotheses.

Before

"As a user I want to receive a weekly digest so that I stay informed."

The story captures a request. It assumes the feature creates value.

It says nothing about what we will measure, or when we will stop if it does not work.

The output is a feature. Success = shipped.

Now

"We believe that users who receive a personalised weekly digest will return 2× more often. We will test this with 20% of users in Sprint 8."

The story captures a hypothesis. It defines the outcome and the signal.

It includes a stopping condition if the hypothesis fails.

Success = learning, not shipping.

Spec-Driven Development changes the format of the specification. The shift above changes its purpose.

ITNOVE
18 · BLOCK 4
THE NEW BOTTLENECK

When building costs almost nothing, the decision is the scarce capital.

More ideas than ever. More stakeholder requests. More technical possibilities. The ability to filter, prioritise, and say no is now the team's most valuable — and most scarce — skill.

The Product Goal is not a planning artefact. It is the filter that protects the team from going very fast in the wrong direction.

Teams that master demand management in the AI era will build ten times more value with the same people. Teams that don't will build ten times more waste.

ITNOVE
19 · BLOCK 5
PARTNERS OR RIVALS? — THE ANSWER

It was designed to learn fast.

Scrum was not designed to produce fast — AI handles production now. What Scrum provides is a framework for learning fast: clear hypotheses, short cycles, validated outcomes.

The AI-era team that wins is not the one that ships the most. It is the one that answers the right questions fastest.

ITNOVE
20 · BLOCK 5
THREE THINGS TO DO THIS WEEK

Start here.

01
Define a clear Product Goal
Before you use AI to build anything
02
Audit your Daily Scrum
Is it validating value — or reporting activity?
03
Measure outcomes
Not just velocity

If you do one thing: write a Product Goal before your next Sprint Planning — the outcome you are chasing, why it matters now, and how you will know you succeeded.

ITNOVE
23 · Q&A

Speed is not the problem. The problem is going very fast in the wrong direction.

THANK YOU · Q&A

Let's talk.

Alex Ballarín · Professional Scrum Trainer · ITNOVE

  • Scrum.org · scrum.org/user/alex-ballarin
  • Web · itnove.com
  • Newsletter · Every Thursday — strategy, product, agile and AI

Suscríbete a la newsletter

Estrategia, producto, IA y equipos ágiles. Cada jueves, 3 minutos.

Doble opt-in · sin spam · RGPD