Footnotes
Foreword
1 www.britannica.com/EBchecked/topic/32876/architecture
2 Melvin E. Conway, “How Do Committees Invent?” Datamation 14, no. 5 (April, 1968): 28–31, www.melconway.com/research/committees.html.
3 Sam Redwine, Proceedings of the 4th International Software Process Workshop, Moretonhampstead, Devon, UK, May 11–13, 1988 (IEEE Computer Society).
Introduction
1 “Principles behind the Agile Manifesto,” www.agilemanifesto.org/principles.html, 2001.
2 Ibid.
3 Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game,” Harvard Business Review, January–February 1986.
Chapter 1
1 Ward Cunningham, “Technical Debt,” http://c2.com/cgi/wiki?TechnicalDebt.
2 Martin Fowler, Refactoring: Improving the Design of Existing Code ...
Get Managing Software Debt: Building for Inevitable Change now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
