part 05 · 7 of 7 written
How software gets made.
Where the working methods came from, and how several came to mean the opposite of their source.
For a separate operational view of time, ownership and team activity, see Monitask's practical guide.
royce1970.pdf fig. 2 — "this concept is risky"
# the diagram everyone copied
# the diagram everyone copied
entries
All seven.
- 7 minThe waterfall paper that argued against waterfall
- 7 minWhere the phrase software crisis came from
- 7 minCode review before there were tools for it
- 7 minTesting, from an afterthought to a discipline
- 7 minThe mythical man-month, and what its author later revised
- 7 minFree and open source licences: what the argument was about
- 7 minWhy estimates are wrong in one direction
further context
For a primary or institutional reference, see the Manifesto for Agile Software Development.
Every claim here carries the source it came from.
The source and its year sit beside the sentence they support. A secondary account is marked as one, and where the record is unclear the entry says so rather than choosing the better story.