Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
"We're Agile, we don't do documentation"
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Birgitta Boeckeler
June 09, 2017
Technology
1.9k
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
"We're Agile, we don't do documentation"
Slides as presented at "The Lead Developer" conference 2017 in London
Birgitta Boeckeler
June 09, 2017
Transcript
43 slides
“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
More Decks by Birgitta Boeckeler
See All by Birgitta Boeckeler
Context != Context: One window, many lifecycles (AI Native DevCon, Nov 2026)
birgitta410
0
150
AI coding state of play, Agile meets Architecture, March 10 2026
birgitta410
0
140
State of Play: KI-unterstützte Programmierung (OOP 2026 Keynote)
birgitta410
0
210
[XP Keynote] AI for teams: State of play for AI assistance beyond code
birgitta410
0
210
The role of developer skills in today's AI-assisted world
birgitta410
1
440
Cultivating Architecture (2022)
birgitta410
0
590
Redefining confidence: Cognitive biases in an architect's life
birgitta410
0
370
Cultivating Architecture with Principles
birgitta410
1
490
Cultivating Architecture
birgitta410
0
2.3k
Other Decks in Technology
See All in Technology
こんなに変わった! AWSネットワークの常識
shotashiratori
11
7.7k
「任されビリティ」で引き受けて「よしなりてぃ」に頼らず任せる / Accept tasks with "makasarebility" and hand them over without relying on "yoshinarily"
pauli
1
720
属人化したISMS運用をGitHubとAIで仕組み化した1年間の記録
sioncojp
4
2.7k
Oracle Base Database Service 技術詳細
oracle4engineer
PRO
17
120k
Del vibe coding a un Desarrollo (agéntico) fiable
jcabot
0
110
Claude Securityを使ってみた / claude-security-claude-code-meetup-nagoya
tnir
0
130
落とし穴にハマってわかった 開発生産性を測るときに気をつけたいこと
munakata
2
250
Shared Signals Framework 仕様解説
oidfj
0
450
サーバーラックは作る時代! 3Dプリンターで作る10インチラックのススメ
jacopen
1
360
IP重複は"ランディングVPC"で受け止める ― PrivateLink と Transit Gatewayによるマルチテナント接続基盤の設計
hatahata021
2
200
マネジメントされる側の仕事は「文句」を言うこと
riyaamemiya
6
5.5k
_マネジメントする人される人ナイト_2026__良いチームを作っていきたい_お気持ち_.pdf
xkxaxkx
0
680
Featured
See All Featured
Noah Learner - AI + Me: how we built a GSC Bulk Export data pipeline
techseoconnect
PRO
0
490
Introduction to Domain-Driven Design and Collaborative software design
baasie
1
1.1k
Site-Speed That Sticks
csswizardry
13
1.6k
Large-scale JavaScript Application Architecture
addyosmani
516
110k
Building the Perfect Custom Keyboard
takai
2
960
Leo the Paperboy
mayatellez
11
2.5k
The Curse of the Amulet
leimatthew05
4
17k
The Impact of AI in SEO - AI Overviews June 2024 Edition
aleyda
6
1.3k
Fashionably flexible responsive web design (full day workshop)
malarkey
409
67k
What Being in a Rock Band Can Teach Us About Real World SEO
427marketing
0
1.1k
JAMstack: Web Apps at Ludicrous Speed - All Things Open 2022
reverentgeek
1
680
The SEO identity crisis: Don't let AI make you average
varn
0
630