Skip to content

Explain how agentic AI fits into the Software Development Model - #35

Merged
ibanFR merged 4 commits into
mainfrom
34-explain-agentic-ai-in-the-model
Sep 30, 2026
Merged

ibanFR merged 4 commits into
mainfrom
34-explain-agentic-ai-in-the-model

Conversation

@ibanFR

@ibanFR ibanFR commented Sep 30, 2026

Copy link
Copy Markdown
Owner

Closes #34

Stacked on #32: the explanation links to the XP research added there. Merge #32 first; this PR then retargets to main.

Adds docs/explanation/agentic-ai-in-the-software-development-model.md, its validation file, and the research behind it, docs/research/agentic-ai-in-the-software-development-model-for-explanation-doc.md.

Answer in short: agents are good at turning an agreed decision into an artefact and weak at reaching the decision.

  • In the model, the steps between components ("formulate", "automate", "write just enough code") are where agents help most.
  • The relationships from the Domain Expert and the Software Engineer into components are where the decisions get made. The collaboration there stays.
  • The Domain Expert can steer more work but also carries more review. The Software Engineer moves towards specifying and verifying.
  • The central tension is speed against shared understanding. The collaborative components keep agent speed in step with what the team understands; the automated ones keep output honest.

The doc walks the five focus areas in flow order, then the tensions across the model and the limits of the evidence. The mapping is interpretation only: workspace.dsl, CONTEXT.md and the ADRs are unchanged.

Sources: 60, 26 new and 34 reused from the XP research, average reputation 0.89. Research review and doc review both approved on the first pass; their results are recorded in the research document and the validation file.

Weak spots:

  • Readability measures about 55 against a 70–80 target. Sentences are already short; the gap comes from glossary terms that must be used exactly. Accepted.
  • The domain-modelling studies used students, not professional Domain Experts.
  • No study was found of Example Mapping or Event Storming with agents in a live team, or of a whole team using agents across the model.
  • One domain-modelling benchmark was verified from its abstract only, so the doc quotes none of its numbers.

🤖 Generated with Claude Code

Agents are strong at turning an agreed decision into an artefact and
weak at reaching the decision. In the model, that is the split between
component-to-component relationships and the relationships from the
Domain Expert and Software Engineer into components. Their
collaboration stays; the central tension is speed against shared
understanding.

The explanation walks the five focus areas in flow order, then the
tensions across the model and the limits of the evidence. It rests on
new research for Align and Understand, BDD, DDD and Lean that reuses
the XP research: 60 sources, average reputation 0.89. Both passed peer
review. Readability measures about 55 against a 70-80 target; accepted,
as the gap comes from glossary terms that must be used exactly.

The mapping is interpretation only; the model is unchanged.

Refs #34

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@ibanFR
ibanFR deleted the branch main September 30, 2026 18:42
@ibanFR ibanFR closed this Sep 30, 2026
@ibanFR ibanFR reopened this Sep 30, 2026
@ibanFR
ibanFR changed the base branch from 31-research-agentic-development-in-xp to main September 30, 2026 18:44
@ibanFR
ibanFR requested a balanced review from Copilot September 30, 2026 18:47

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Several claims lack direct citations, and the source-validation record contains unresolved inaccuracies.

Review effort: Balanced
Findings: 2 Medium severity · 8 Low severity

Open (10)
What changed in this PR

Explains how agentic AI supports—not replaces—the Software Development Model’s roles and focus areas.

Changes:

  • Adds the evidence-backed explanation.
  • Adds supporting research and citations.
  • Records documentation validation and peer-review results.
File Description
docs/​explanation/​agentic-ai-in-the-software-development-model.md Explains agentic AI’s role across the model.
docs/​explanation/​agentic-ai-in-the-software-development-model.md.validation.yaml Records validation and review outcomes.
docs/​research/​agentic-ai-in-the-software-development-model-for-explanation-doc.md Provides supporting research and source analysis.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

ibanFR and others added 2 commits September 30, 2026 19:54
Link the QCon report, the Siddeeq Gherkin study, the domain-modelling
benchmark, the 2x-mandate field study, the feedback-classification
study, the skill-formation studies and Farley's podcast, and separate
what each user-story study found instead of attributing all three
weaknesses to both.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- Describe BDD and DDD as separate paths from Align and Understand that
  each feed XP, as workspace.dsl shows.
- Attribute each Gherkin finding to its own study instead of all three.
- Cite the 2025 DORA report and the AI Capabilities Model.
- List Strategic Architecture, not the collaborative modelling
  relationship, among the collaborative components.
- Relabel the research review entry: N2 and N3 are BDD studies.
- Fix Plöd's name and bring the validation record in line with the
  measured readability score.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@ibanFR
ibanFR merged commit f34c1d6 into main Sep 30, 2026
3 checks passed
@ibanFR
ibanFR deleted the 34-explain-agentic-ai-in-the-model branch September 30, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Explain how agentic AI fits into the Software Development Model

2 participants