Select the search type
  • Site
  • Web
Search

Path Steps

Follow these steps in order. Each one links to an EasyDNNnews article/video and gives you a quick, practical takeaway.

You’ll learn how to frame AI as a teammate that supports Scrum events and backlog work without replacing judgment or collaboration.
Do this exercise: Write a 3-sentence “AI usage policy” for your team (what you will use AI for, what you won’t, and what must be reviewed by a human).
You’ll learn repeatable prompt patterns to generate stories with clearer intent, constraints, and acceptance criteria.
Do this exercise: Take one messy request and prompt AI to produce (a) a user story, (b) 5 acceptance criteria, and (c) 3 key questions for the PO.
You’ll learn how to generate “plan options” (not commitments) and improve shared understanding of scope and dependencies.
Do this exercise: Ask AI for 2 sprint goal options based on your top backlog items, then pick one as a team and adjust wording together.
You’ll learn facilitation prompts that help teams extract insights, turn feedback into actions, and avoid “retro theatre.”
Do this exercise: Feed AI 5 bullet facts from the sprint and ask for (a) patterns, (b) 3 improvement experiments, and (c) 1 metric per experiment.
You’ll learn how to convert your best prompts and practices into a lightweight working agreement the team can actually follow.
Do this exercise: Create a “Prompt Library” page with 5 prompts: refinement, story writing, planning, review, retro—each with input/output examples.
 

Learning Path - Free

24 Feb 2026

Step 1: What AI Can (and Can’t) Do for Scrum Teams

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.

Author: Rod Claar
0 Comments
Article rating: No rating

24 Feb 2026

Step 2: Prompts That Produce Better User Stories

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

Author: Rod Claar
0 Comments
Article rating: No rating

24 Feb 2026

Step 3: Backlog Refinement with AI (Without Losing the “Why”)

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.

Author: Rod Claar
0 Comments
Article rating: No rating

24 Feb 2026

Step 4: Sprint Planning Acceleration

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.

Author: Rod Claar
0 Comments
Article rating: No rating
RSS

Learning Path - Member

 
 
✓ Featured Content

AI for Scrum and Agile Teams
Videos

A curated playlist of specific YouTube content.

Search Results

9 Mar 2026

Step 3: TDD with AI — Keeping You in the Driver’s Seat

Author: Rod Claar  /  Categories: AI for Experienced Devs Learning Path - Members  /  Rate this article:
No rating

Step 3: TDD with AI — Keeping You in the Driver’s Seat

Objective
Use AI to accelerate Test-Driven Development (TDD) without surrendering design intent or engineering judgment.

The goal is not to let AI write your tests blindly. The goal is to use AI as a thinking partner while you remain the architect of the code.


Learning Path

1. Re-establish the TDD Loop

Before introducing AI, anchor on the classic cycle:

  1. Red – Write a failing test

  2. Green – Write the simplest code to pass

  3. Refactor – Improve design safely

AI should support this loop, not bypass it.

Key rule:

Tests define intent. AI assists implementation.


2. Use AI to Generate Test Ideas

AI is excellent at producing test scenarios you may not immediately think of.

Ask AI questions like:


 

Generate unit test scenarios for this function.
Include edge cases, boundary conditions, and failure cases.

Example function:


 

def calculate_discount(price, percentage):
return price * (percentage / 100)

Possible AI-generated scenarios:

  • Normal discount case

  • Zero discount

  • 100% discount

  • Negative percentage

  • Very large price values

  • Rounding behavior

Your job is to evaluate which tests reflect real system behavior.

AI suggests.
You decide.


3. Write the Tests Yourself

Do not copy-paste AI-generated test code.

Instead:

  1. Review the AI test ideas

  2. Select the meaningful ones

  3. Write the tests manually

This preserves:

  • understanding

  • design clarity

  • debugging ability

Example:


 

def test_zero_discount():
assert calculate_discount(100, 0) == 0


4. Compare Your Tests With AI Suggestions

After writing your tests:

Ask AI:


 

Compare these unit tests with your earlier suggestions.
What cases might still be missing?

This is where AI shines as a coverage reviewer.

You may discover:

  • missing edge cases

  • input validation gaps

  • boundary conditions


5. Implement the Code to Pass Tests

Now return to the TDD loop.

Let the tests drive implementation.

AI can help with:

  • implementation suggestions

  • refactoring

  • simplifying logic

  • identifying duplicated code

Prompt example:


 

Given these tests, suggest a simple implementation that passes them.
Do not add features not required by the tests.


6. Use AI for Safe Refactoring

Once tests pass, AI can help identify design improvements.

Ask:


 

Refactor this code while preserving behavior verified by the tests.
Focus on readability and simplicity.

Your safety net:

The test suite.

If tests pass, refactoring is safe.


Exercise

Goal

Practice using AI to expand test coverage while maintaining developer control.

Step 1 — Pick a Small Function

Choose something simple:

  • string parser

  • calculation function

  • validation logic

  • utility method


Step 2 — Ask AI for Test Cases

Example prompt:


 

Generate unit test cases for this function.
Include edge cases and failure scenarios.


Step 3 — Write Tests Yourself

Do not copy the AI output.

Instead:

  • read the suggestions

  • select meaningful ones

  • write tests manually


Step 4 — Compare Gaps

Ask AI:


 

Compare my tests with the earlier suggestions.
What important cases might still be missing?


Step 5 — Expand Coverage

Add the missing cases you agree with.

Your final test suite should reflect:

  • real requirements

  • edge conditions

  • error behavior


Key Principle

AI improves test discovery.

Developers maintain design ownership.

A useful mental model:

Role Responsibility
Developer Defines intent and architecture
Tests Protect behavior
AI Suggests cases and improvements

You stay in the driver’s seat.

Print

Number of views (28)      Comments (0)

Tags:

Search

Calendar

«March 2026»
SunMonTueWedThuFriSat
22232425262728
1234567
891011121314
15161718192021
22232425262728
2930311234

Upcoming events

Upcoming AI Training

20 May 2026

Author: Rod Claar
0 Comments
Article rating: No rating

2 Apr 2026

Author: Rod Claar
0 Comments
Article rating: No rating
RSS

Two Ways

Keep Learning — Two Ways

Choose the free track to get new lessons as they’re released, or go deeper with a structured course that puts everything into a repeatable playbook.

Free
Join updates / get new lessons

Get notified when new steps, templates, and examples are added—so you can keep improving your AI skills one sprint at a time.

Join updates
No spam. Practical lessons only. Unsubscribe any time.