Future Of Software Development
Martin Fowler · article · 2026-07-07 source ↗ Reader 🖥️
Thoughtworks convened invitation-only 'Future of Software Development' Open Space retreats in 2026 to examine how AI and LLMs will reshape the profession, and Fowler deliberately captured the discussions as unattributed fragments rather than one coherent narrative — the fragmentary form itself signalling that the profession's future is too unsettled to reduce to a single thesis.
mixed · expository — An index/roundup post rather than an argument: it frames an event (two Thoughtworks retreats) and deliberately declines to synthesize, pointing instead to a set of fragment posts and external write-ups.
Structure
| Part | Role |
|---|---|
| Event framing (what, when, where, who) | Establishes the setting: a February 2026 Thoughtworks retreat in Deer Valley, Utah, nodding to the Agile Manifesto's 25th anniversary but framed as forward-looking about AI and LLMs |
| Format and participation note | Describes the method (an intense day-and-a-half Open Space conference) and the curated audience (~50 Thoughtworkers, pundits, and clients active in LLM-driven change) |
| The refusal to synthesize | States Fowler's editorial choice not to write a coherent narrative, publishing scattered insights as fragment posts instead |
| Chatham House Rule caveat | Governs attribution: most comments are unattributed unless a speaker gave permission |
Key terms
- Open Space
A self-organizing conference format in which participants propose and run the sessions, producing many parallel, agenda-free threads (Harrison Owen's method, which Fowler documents in a separate bliki entry) - Chatham House Rule
A confidentiality convention under which attendees may use what was said but may not reveal who said it, unless the speaker gives permission — invoked here to keep comments unattributed - fragments
Fowler's practice of publishing short, standalone insight posts over time rather than assembling them into one long, coherent article
Propositions
- explicitIn February 2026, Thoughtworks hosted an invitation-only 'Future of Software Development' Open Space retreat in Deer Valley, Utah, to examine how the rise of AI and LLMs will affect the software profession.conf: high
- explicitThe Utah retreat was sited in the mountains and timed as a nod to the 25th anniversary of the Manifesto for Agile Software Development, yet was framed as forward-looking rather than commemorative.conf: high
- explicitA second 'Future of Software Development' retreat was held in Europe in mid-2026, extending the same inquiry beyond the initial Utah gathering.conf: medium
- explicitParticipation was deliberately curated — about 50 Thoughtworkers, software pundits, and clients, all selected for being active in the LLM-fuelled changes to the profession.conf: high
- explicitThe retreat was held under the Chatham House Rule, so the insights Fowler shares are largely unattributed unless a speaker granted specific permission.conf: high
- explicitRather than write a coherent narrative of what was discussed and learned, Fowler deliberately published the takeaways as scattered fragment posts.conf: high
- implicitThe fragmentary, un-synthesized form of the write-up reflects a judgment that the future of software development in the agentic age is too unsettled and multi-threaded to be reduced to a single coherent thesis.conf: medium
Arguments
Publishing the retreat's takeaways as unattributed fragments, rather than a single synthesized narrative, is the appropriate way to document it. strength: medium
Explicit premises:
- The event was an intense day-and-a-half Open Space covering many parallel, participant-driven sessions.
- The retreat was held under the Chatham House Rule, which restricts attribution.
- Fowler states he 'haven't attempted to make a coherent narrative' and posted insights as fragments instead.
Implicit premises:
- A single coherent narrative would impose a false unity on a genuinely multi-threaded and unsettled discussion.
- Fragments preserve the plurality of perspectives better than a synthesized account would.
Inferences:
- Therefore fragments better represent the actual state of the conversation than a forced synthesis.
Narratives
- Thoughtworks gathered about 50 invited participants in the mountains of Deer Valley, Utah in February 2026 — a quarter-century after the Agile Manifesto was written nearby — not to celebrate the past but to look forward at how AI and LLMs will change software development.
→ Frames the retreat as a symbolic hinge between eras: the Agile generation convening to confront the next paradigm.
Questions addressed
- ⭕ How will the rise of AI and LLMs affect the software profession?
The post deliberately does not answer this; it points readers to scattered fragment posts and external participants' write-ups instead of offering a consolidated conclusion. - ✅ How should a rich, multi-threaded, confidential discussion be documented publicly?
As unattributed fragments published over time, respecting the Chatham House Rule and preserving the plurality of the discussion rather than forcing it into one narrative.
Gaps
- incompleteAs an index, the post provides no synthesis or throughline of what the retreat collectively concluded; a reader cannot learn the substance of the discussions from this page alone and must chase each individual fragment and external write-up.
Read next: Read Fowler's individual fragment posts, plus participant accounts such as Annie Vella's 'Finding Comfort in the Uncertainty', the Rachel Laycock New Stack interview, and the Thoughtworks report. - incompleteBecause the retreat was held under the Chatham House Rule, the insights are unattributed, so a reader cannot trace claims to their sources or weigh them against the speakers' contexts and track records.
Read next: Seek on-record accounts from named participants who wrote their own posts or granted permission to be quoted. - incompleteParticipants were all selected for being 'active in the LLM-fuelled changes,' so the retreat's perspective is pre-filtered toward AI-engaged practitioners; skeptical, displaced, or AI-critical voices are structurally underrepresented.
Read next: Read AI-skeptic and labor-impact perspectives to counterbalance the sampling. - incompleteThe post frames the event as forward-looking while siting it as a nod to the Agile Manifesto's 25th anniversary, but never develops what the Agile movement's 25-year trajectory might teach about the coming AI transition — the retrospective framing is invoked and then dropped.
Read next: Compare the Agile Manifesto's 25-year arc (semantic diffusion, the 'agile industrial complex') with the current predictions about AI's effect on the profession.