Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
"We're Agile, we don't do documentation"
Search
Birgitta Boeckeler
June 09, 2017
Technology
1
1.7k
"We're Agile, we don't do documentation"
Slides as presented at "The Lead Developer" conference 2017 in London
Birgitta Boeckeler
June 09, 2017
Tweet
Share
More Decks by Birgitta Boeckeler
See All by Birgitta Boeckeler
[XP Keynote] AI for teams: State of play for AI assistance beyond code
birgitta410
0
27
The role of developer skills in today's AI-assisted world
birgitta410
0
79
Cultivating Architecture (2022)
birgitta410
0
440
Redefining confidence: Cognitive biases in an architect's life
birgitta410
0
270
Cultivating Architecture with Principles
birgitta410
1
430
Cultivating Architecture
birgitta410
0
2.2k
To pair, or not to pair
birgitta410
1
480
To pair, or not to pair
birgitta410
0
450
Born for IT? How the image of software developers came about
birgitta410
0
420
Other Decks in Technology
See All in Technology
Welcome to the LLM Club
koic
0
170
AWS Summit Japan 2025 Community Stage - App workflow automation by AWS Step Functions
matsuihidetoshi
1
260
Node-RED × MCP 勉強会 vol.1
1ftseabass
PRO
0
140
監視のこれまでとこれから/sakura monitoring seminar 2025
fujiwara3
11
3.9k
Clineを含めたAIエージェントを 大規模組織に導入し、投資対効果を考える / Introducing AI agents into your organization
i35_267
4
1.6k
Claude Code Actionを使ったコード品質改善の取り組み
potix2
PRO
6
2.2k
Node-REDのFunctionノードでMCPサーバーの実装を試してみた / Node-RED × MCP 勉強会 vol.1
you
PRO
0
110
生成AI活用の組織格差を解消する 〜ビジネス職のCursor導入が開発効率に与えた好循環〜 / Closing the Organizational Gap in AI Adoption
upamune
2
1.1k
TechLION vol.41~MySQLユーザ会のほうから来ました / techlion41_mysql
sakaik
0
180
MySQL5.6から8.4へ 戦いの記録
kyoshidaxx
1
210
Model Mondays S2E02: Model Context Protocol
nitya
0
220
プロダクトエンジニアリング組織への歩み、その現在地 / Our journey to becoming a product engineering organization
hiro_torii
0
130
Featured
See All Featured
Embracing the Ebb and Flow
colly
86
4.7k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Art, The Web, and Tiny UX
lynnandtonic
299
21k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
281
13k
The Language of Interfaces
destraynor
158
25k
Bash Introduction
62gerente
614
210k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.3k
Adopting Sorbet at Scale
ufuk
77
9.4k
Optimizing for Happiness
mojombo
379
70k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
700
Building a Scalable Design System with Sketch
lauravandoore
462
33k
How to Think Like a Performance Engineer
csswizardry
24
1.7k
Transcript
“WE’RE AGILE, WE DON’T DO DOCUMENTATION” @birgitta410 B i r
g i t t a B ö c k e l e r
None
“Documenting Software Architectures – Views and Beyond” 2nd edition, 2011;
Clements, Bachmann, Bass, Garlan, Ivers, Little, Merson, Nord, Stafford
None
None
None
None
None
None
DESCRIBING SOFTWARE
None
WHERE ARE YOU? 1:1 UML diagrams No documentation at all
“Self- documenting code” Tests are readable specification
PURPOSE of documentation?
For the sake of a PROCESS.
PURPOSE of documentation?
Create a COMMON UNDERSTANDING. 1
None
The wall of COMMON UNDERSTANDING. Containers & Tech Stack Environments
Components … … … Up for grabs!
Surface and understand COMPLEXITY. 2
… … … Data schema migrations Synching behavior … Design
of storage module
INFO GRAPHICS.
“WIDGET” KITS.
Create EMPATHY. 3
Empathy between TECH DECISION MAKERS and developers.
“Working on software without guidance, without documentation, is anxiety-producing” https://medium.com/@duretti/no-flex-zone-empathy-driven-development-aebf4d8cf7cf
Empathy with EACH OTHER.
Empathy between PRODUCT PEOPLE and developers.
Empathy with OTHER TECHNOLOGISTS.
Help our FUTURE SELVES make informed DECISIONS. 4
Architecture DECISION records. http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions “Without understanding the rationale (…), only
two choices: 1. Blindly accept the decision. 2. Blindly change it.”
LIGHTWEIGHT architecture DECISION records. https://github.com/npryce/adr-tools
Describe the PROBLEM, not just the SOLUTION.
CREATIVE problem SOLVING. 5
None
None
None
None
But how do we keep it UP TO DATE?!
@kaeff
As LITTLE as possible. Make it VISIBLE. Include in RITUALS.
Create OWNERSHIP through COLLABORATION.
Help our FUTURE SELVES make informed DECISIONS. Surface and understand
COMPLEXITY. Create COMMON UNDERSTANDING. CREATIVE problem SOLVING. Create EMPATHY.
<> Code THE TRUTH HOW-TOs HISTORY MAPS CREATIVE THINKING
“Individuals and interactions” “Business people and developers work together daily”
“Face to face communication” “Attention to technical excellence and good design” “Simplicity”
@birgitta410