“I Come to Bury Agile, Not to Praise It” Effective Software Development in the 21st Century Alistair Cockburn http://Alistair.Cockburn.us I come to bury Agile, not to praise it; The evil methods do lives after them, The good is oft interred with their bones, So let it be with Agile.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Effective Software Development in the 21st Century
Software development is aCooperative Game
DevelopmentGames have positions, moves, strategies
Product Line Management
1 - 6
Number of people coordinatedAdapt to your situation
2 people atwhiteboard
(Courtesy of Thoughtworks, inc.)
Face-to-face is the most effective - Try Video
2 people on phone
2 peopleon chat
Richness of communication channel
12 people:= $100,000 / yr penalty
12 people = $300,000 / yr penalty
PatDistance is expensive
“Managing the Flow of Technology” “Distance Matters”
Use Lean Processes
I wish they’d decidewhat stylethey want!
I wish they’d think a bit more carefullybefore coding!
I wish they’d decideon the UI designalready!
Every line of code is a decision
I wish they’d decide what functions they want!
TestersSoftware development looks like manufacturing if the unit of inventory is the unvalidated decision!
Decisions about function and style
Decisions about systemcorrectness
Decisions about programstructure
Detailed decisionsabout functionand data
BusinessAnalystsSoftware development has correction loops
100 lines of codeshow up for testing
TestersFrom Lean Manufacturing:aim for continuous flow
# of design decisions
How long this line of code/ screen / use case / decisionsits in the testing queue
Decisions being validated or broken
Lots of Programmers
Enough Users & Sponsors
A few Business Analysts
Enough Users & Sponsors
Not enough Programmers
Many Business Analysts
Users & Sponsorsabsent
Database designersFrom Lean Manufacturing: watch your queues
Design is Knowledge Acquisition
Knowledge comes atthe “moment of truth”: final integration.
Delivers nearly no knowledge
(or risk reduction)Waterfall is a late-learning strategy
Growth of knowledge with big-bang integration
indifferent (with respectto knowledge)
(risk reduction)We can pay to learn early in the project
Growth of knowledge with early, continuous integration
Business value growing
Knowledge growing(risk reduction)
on-time (or early)
Delay to get more
or betterTrim the Tail: Choose to deliver by valueordate