Bibliography
Disclaimer: The links listed in this bibliography page worked at the time they were added. The Internet is a dynamic place, and pages move or disappear. If you find any link that has become stale, I appreciate your reporting it through the:
Disclosure: Some of the links listed in this bibliography page contain my referral ID with Amazon, which provides me with a small commission for each sale, should you decide to buy the related book.
Thank you for your support!
A
ADDISON-2002Addison, T. and Vallab, S. (2002). Controlling software project risks: An empirical study of methods used by experienced project managers. SAICSIT 02: Proceedings of the 2002 annual research conference of the South African institute of computer scientists and information technologists on Enablement through technology – South African Institute for Computer Scientists and Information Technologists, 2002.
ALEXANDER-1977Alexander, C. (1977): A Pattern Language: Towns, Buildings, Construction. Oxford University Press.
ALEXANDER-1979Alexander, C. (1979): The Timeless Way of Building. Oxford University Press.
ANDERSON-2003Anderson, D. J. (2003): Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results. Prentice Hall.
ANDERSON-2008Anderson, D. J. (2008): Why We Lost Focus on Development Practices (Blog post).
ANDERSON-2010Anderson, D. J. (2010): Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press.
ANDERSON-2012Anderson, D. J. (2012): Lessons in Agile Management: On the Road to Kanban . Blue Hole Press.
ARGYRIS-1977 Argyris, C. (1977): Double Loop Learning in Organizations, Harvard Business Review, September, 1977.
ARGYRIS-1978 Argyris, C. and Schon D. A. (1978): Organizational Learning: A Theory of Action Perspective (Addison-Wesley Series on Organization Development.). Addison-Wesley.
ARGYRIS-1991 Argyris, C. (1991): Teaching Smart People How to Learn, Harvard Business Review, May-June, 1991, pp. 99-109.
B
BABATUNDE-1994 Babatunde, A. O. and Harmon, R. (1994): Process Dynamics, Modeling, and Control. Oxford University Press.
BARTRAM-2006Bartram, P (2006): Forecasting the End of Budgets. Director, Aug2006, Vol. 60 Issue 1, p30.
BECK-2001 Beck, K. et al. (2001): Manifesto for Agile Software Development. Snowbird, Utah, 2001.
BECKER-2010Becker, S. et al (2010): The Evolution of a Management Accounting Idea: The Case of Beyond Budgeting. Institute of Management Accounting and Control (IMC) WHU – Otto Beisheim School of Management, Vallendar, Germany.
BEEDLE-2000 Beedle, M et al. (2000): SCRUM: An extension pattern language for hyperproductive software development.
BOEHM-1981 Boehm, B. W. (1981): Software Engineering Economics. Prentice Hall.
BOEHM-1991 Boehm, B. (1991). Software risk management: Principles and practices.. IEEE Software, V8N1PP32-41.
BRAGG-2007Bragg S. M.: Throughput Accounting: A Guide to Constraint Management. Wiley.
C
CAIN-1996a Cain, B. C. and Coplien, J. O. (1996): A Role-Based Empirical Process Modeling Environment.
CAIN-1996b Cain, B. C. et al. (1996): Social patterns in productive software development organizations.
CHARETTE-1989 Charette, R. N. (1989): Software Engineering Risk Analysis and Management (Mcgraw Hill Software Engineering Series). McGraw-Hill.
CHARLTON-2011Charlton, I (2011): Theory of Constraints in Software Development.
COCKBURN-2005 Cockburn, A. et al. (2005): The declaration of interdependence for modern management or DOI.
COHN-2005 Cohn, M (2005): Agile Estimating and Planning. Prentice-Hall.
COPLIEN-1994 Coplien, J. O. (1994): Borland Software Craftsmanship: A New Look at Process, Quality and Productivity. Proceedings of the 5th Annual Borland International Conference, Orlando, Florida, 5 June 1994.
COPLIEN-1995 Coplien, J. O. (1995):“A Generative Development-Process Pattern Language” in Pattern Languages of Program Design. Addison-Wesley Professional.
COPLIEN-1996 Coplien, J. O. and Harrison, N.B. (1996): Patterns of Productive Software Organizations. Bell Labs Technical Journal, Summer 1996. Lucent Technologies Inc.
COPLIEN-2004 Coplien, J. O. and Harrison, N. B. (2004): Organizational Patterns of Agile Software Development. Prentice Hall.
COPLIEN-2007 Coplien, J. O. (2007): Organizational Patterns: A Key for Agile Software Development. INCOSE, May 28, 2007.
COPLIEN-2008 Coplien, J. O. (2008): Scrum Patterns Summary: The Patterns without which Scrum is unlikely to work.
CORBETT-1998Corbett, T. (1998): Throughput Accounting. North River Press
COSTAGLIOLA-2006 Costagliola, G. et al (2006): Effort estimation modeling techniques: a case study for web applications. Proceedings of the 6th international conference on Web engineering, Palo Alto, CA, USA
COX-2010Cox, J. and Schleier, J. (2010): Theory of Constraints Handbook. McGraw-Hill Professional.
D
DAUM-2003Daum, J. (2003); Interview with Lennart Francke: Managing without budgets at Svenska Handelsbanken. The new New Economy Analyst Report, Feb 24, 2003.
DEKKERS-2001Dekkers, C. and Gunter, I. (2000): Using “Backfiring” to Accurately Size Software: more Wishful Thinking Than Science?. IT Metrics Strategies, November 2000 Vol VI No. 11, Cutter Consortium.
DEMARCO-2003DeMarco, T. and Lister, T. (2003): Waltzing With Bears: Managing Risk on Software Projects. Dorset House.
DEMING-1982Deming, W. E. (1982): Out of the Crisis. MIT.
DEMING-1993Deming, W. E. (1993): The New Economics for Industry, Government, Education. MIT, Center for Advanced Engineering.
DENNING-2008 Denning, P. J., Gunderson, C., and Hayes-Roth, R. (2008): The Profession of IT: Evolutionary System Development. CACM, December 2008, V51 N12 PP29-31.
DENNE-2004Denne, M. and Cleland-Huang, J. (2004): Software by Numbers: Low-Risk, High-Return Development. Prentice Hall.
DERBY-2006 Derby, E. and Larsen, D. (2006): Agile Retrospectives: Making Good Teams Great. Pragmatic Bookshelf.
DETTMER-2007Dettmer, H. W. (2007): The Logical Thinking Process: A Systems Approach to Complex Problem Solving. ASQ Quality Press.
DUBAKOV-2011 Dubakov, M (September 27, 2011): The Future of Agile Software Development.
DUBNER-2006Dubner, S. J. and Levitt, S. D. (May 7, 2006): A Star is Made. The New York Times.
E
F
FALLAH-2010 Fallah, M., et. al. (2010). Critical Chain Project Scheduling: Utilizing Uncertainty for Buffer Sizing. International Journal of Research and Review in Applied Sciences, June 2010, pp. 280–289.
FISHER-1992 Fisher, L. M. (1992): The Borland Barbarian’s New Weapon. The New York Times.
FUTRELL-2002 Futrell, R. T. et al. (2002): Quality Software Project Management. Prentice Hall.
G
GABRIEL-1996Gabriel, R. (1996): Gabriel, R. P. (1996): Patterns of Software: Tales from the Software Community .Oxford University Press, 1996.
GEEKIE-2006Geekie, A. (2006): Buffer Sizing for the Critical Chain Project Management Method. Master’s thesis, Department of Engineering and Technology Management, Faculty of Engineering, University of Pretoria.
GOLDRATT-1990aGoldratt, E. (1990): The Haystack Syndrome: Sifting Information Out of the Data Ocean. North River Press.
GOLDRATT-1990bGoldratt, E. (1990): What is this Thing Called Theory of Constraints. North River Press.
GOLDRATT-1994Goldratt, E. (1994): It’s Not Luck. North River Press.
GOLDRATT-1992Goldratt, E. (1992): The Goal: A Process of Ongoing Improvement. North River Press.
GOLDRATT-1997Goldratt, E. (1997): Critical Chain. North River Press.
GOVINDARAJ-2011Govindaraj, S. (2011): Using Class of Service to Manage Product Risk.. Silver Stripe Software.
GRAHAM-2006Graham, P. (June, 2006): The Power of the Marginal.
GRIFFITHS-2007Griffiths, M. (2007): Developments in Agile Project Management. PMI Global Conference Proceedings, Atlanta, Georgia. G
H
HARRISON-2000Harrison, N. et al. (2000): Pattern Languages of Program Design 4. Addison Wesley Publishing Company.
HIBBS-2009Hibbs, C. et al. (2009): The Art of Lean Software Development. O’Reilly Media.
HOPE-2003Hope, J and Fraser, R. (2003): Who Needs Budgets?, Harvard Business Review, February, 2003.
HUMPHREY-1995Humphrey, W. S. (1995): A Discipline for Software Engineering. SEI Series in Software Engineering. Addison-Wesley.
I
IKONEN-2011IIkonen, M. et al. (2011): On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation. Department of Computer Science, University of Helsinki, Finland.
ISHIKAWA-1990Ishikawa, K. (1990): Introduction to Quality Control. Productivity Press.
J
JOHNSON-2004 Johnson E. (pseudonym) (2004): Function Points: Numerology for Software Devlopers in Hacknot: Essays on Software Development.
JONES-1995 Jones, C. (1995): Backfiring: Converting Lines-of-Code to Function Points. IEEE Software, November 1995 (vol. 28 no. 11).
JONES-1996 Jones, C. (1996): Applied Software Measurement: Assuring Productivity and Quality. McGraw-Hill.
JONES-2000 Jones, C. (2007): Software Assessments, Benchmarks, and Best Practices. Addison-Wesley Professional.
JONES-2007 Jones, C. (2007): Estimating Software Costs: Bringing Realism to Estimating. McGraw-Hill Osborne Media.
K
KERTH-2001 Kerth, N. L. (2001): Project Retrospectives: A Handbook for Team Reviews. Dorset House.
KNIBERG-2010Kniberg, H. and
Skarin, M. (2010): Kanban and Scrum – making the most of both. Lulu.com.
KITCHENHAM-1997 Kitchenham, B. (1997): Counterpoint: The Problem with Function Points. IEEE Software, March 1997, pp 29-31.
KROEBER-1948Kroeber, A. L. (1948): Anthropology: Culture, Patterns and Process. Harcourt, Brace and World.
L
LADAS-2008Ladas, C. (2008): Scrumban – Essays on Kanban Systems for Lean Software Development. Modus Cooperandi Press.
LAIRD-2006Laird L. M. and Brennan M. C. (2006): Software Measurement and Estimation: A Practical Approach (Quantitative Software Engineering Series). Wiley-IEEE Computer Society.
LAVAZZA-2008 Lavazza L. A., et al. (2008): Model-based Functional Size Measurement. Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement, Kaiserslautern, Germany.
LEACH-2004Leach, L. P. (2004):
Critical Chain Project Management, Second Edition. Artech House.
LEVESQUE-2008 Levesque G. et al. (2008): Estimating Software Size with UML Models. Proceedings of the 2008 C3S2E conference, Montreal, Quebec, Canada.
M
MARTIN-2012Martin R (2012): Why I Decided to Rethink Hiring Smart People, Harvard Business Review Blog, October, 2012.
MCCARTHY-2012McCarthy, J. and McCarthy M. (2012): Elements of the Core.
MILLS-1972Mills, Harlan D. (1972): Mathematical Foundations of Structured Programming. IBM Corporation Technical Report No. FSC 72-6012, IBM Federal Systems Division, Gaithersburg, Maryland.
MORENO-1934Moreno, J. L. (1934): Who shall survive?: foundations of sociometry, group psychotherapy, and sociodrma. Washington, D. C.: Nervous and Mental Disease Publishing Co., 1934. Who Shall Survive? Foundations of Sociometry, Group Psychotherapy and Sociodrama (1953 reprint)
MOROWSKI-2008 Morowski, P. (2008): The Borland Agile Journey – An Executive Perspective on Enterprise Transformation. Agile Journal, August 2008.
N
NERUR-2007 Nerur, S. and Balijepally, V. (2007): Theoretical Reflections on Agile Development Methodologies The traditional goal of optimization and control is making way for learning and optimization. CACM, March 2007, V50 N30 PP79-83.
NOLAN-1990Nolan, T. W. and Provost, L. P. (1990): Understanding Variation, Quality Progress.
NOREEN-1995Noreen, E. W. et al.: Theory of Constraints and Its Implications for Management Accounting. North River Press.
O
OESTERGREN-2008Oestergren, K and Stensaker, I (2008): Management control without budgets: A field study of “beyond budgeting” in practice. NHH Norwegian School of Economics and Business Administration.
OHNO-1988Ohno, T. (1988): Toyota Production System: Beyond Large-Scale Production. Productivity Press.
P
PATTON-2009 Patton, J. (2000): Kanban Development Oversimplified (Online article).
POPPENDIECK-2003Poppendieck, M. and Poppendieck, T. (2003): Lean Software Development: An Agile Toolkit Addison-Wesley Professional.
POPPENDIECK-2007Poppendieck, M. and Poppendieck, T. (2007): Implementing Lean Software Development: From Concept to Cash. Addison-Wesley.
Q
R
REIFER-2000 Reifer, D. (2000): Web Development: Estimating Quick-to-Market Software. IEEE Software, November/December 2000, pp 57-64.
REINERTSEN-2009Reinertsen, D. J. (2009): The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing.
RICKETTS-2007Ricketts, J. A. (2007): Reaching The Goal: How Managers Improve a Services Business Using Goldratt’s Theory of Constraints. IBM Press.
S
SCHEINKOPF-1999 Scheinkopf, L. (1990): Thinking for a Change: Putting the TOC Thinking Processes to Use (The CRC Press Series on Constraints Management). St. Lucie Press.
SCHRAGENHEIM-1999Schragenheim, E. (1999): Management Dilemmas: The Theory of Constraints Approach to Problem Identification and Solutions (The CRC Press Series on Constraints Management). St. Lucie Press.
SCHWABER-2001 Schwaber K. (2001): Agile Software Development with Scrum. Prentice Hall
SCHWABER-2011 Schwaber, K (2011-04-07): Scrum Fails? Ken Schwaber’s Blog: Telling It Like It Is.
SHEWHART-1986 Shewart, W. A. (1986): Statistical Method from the Viewpoint of Quality Control (Dover Books on Mathematics) (originally published in 1939). Dover Publications.
SHUSTEK-2008 Shustek, L. (2008): Donald Knuth: A life’s work interrupted, Communications of the ACM, vol. 51, issue 8: ACM, New York, NY, USA, pp. 31-35, 08/2008.
SMITE-2010 Smite, D. et al. (2010): Agility Across Time and Space: Implementing Agile Methods in Global Software Projects. Springer. Note: In this book, The Chronologist contributed Chapter 4: “Tailoring Agility: Promiscuous Pair Story Authoring and Value Calculation.”
SMITH-1999Smith, D: The Measurement Nightmare: How the Theory of Constraints Can Resolve Conflicting Strategies, Policies, and Measures (APICS Constraints Management). CRC Press.
SPOLSKY-2007 Spolsky J. (2007): Evidence Based Scheduling.
SULLIVAN-2012Sullivan, T. T. et al. (2012): The TOCICO Dictionary, Second Edition, 2012.
SUTHERLAND-2001 Sutherland, J. (2001): Inventing and Reinventing SCRUM in Five Companies. PatientKeeper, Inc.
SUTHERLAND-2003 Sutherland, J. (2003): Scrum: Another way to think about scaling a project.
SUTHERLAND-2005 Sutherland, J. et al. (2005): Future of Scrum: Parallel Pipelining of Sprints in Complex Projects. Agile 2005, July 24-29, 2005, Mariott Denver City Center.
SUTHERLAND-2006 Sutherland, J. et al. (2006): Adaptive Engineering of Large Software Projects with Distributed/Outsourced Teams. 6th International Conference on Complex Systems (ICCS), June 25-30, 2006; Boston, MA.
SUTHERLAND-2007 Sutherland, J. et al. (2007): Distributed Scrum: Agile Project Management with Outsourced Development Teams. 40th Annual Hawaii International Conference on System Sciences (HICSS’07).
SUTHERLAND-2007b Sutherland, J. (2007): Origins of Scrum. Blog post.
SUTHERLAND-2008 Sutherland, J. et al. (2008): Fully Distributed Scrum: The Secret Sauce for Hyperproductive Offshored Development Teams. 6th International Conference on Complex Systems (ICCS), June 25-30, 2006; Boston, MA.
SUTHERLAND-2008a Sutherland J. (2008): Pretty Good Scrum: Secret Sauce for Distributed Teams.
SUTHERLAND-2009 Sutherland, J. (2009): Shock Therapy Self Orgnization in Scrum.
SUTHERLAND-2009b Sutherland, J. (2009): Agile Architecture: Red Pill or Blue Pill.
SUTHERLAND-2010 Sutherland J. (2010): Agile Contracts: Money for Nothing and Your Change for Free.
SUTHERLAND-2010a Sutherland, J. (2010): The Roots of Scrum, How the Japanese Lean Experience Changed Global Software Developmment. ACCU conference 2010. A video of an earlier similar presentation is here: The Roots of Scrum – InfoQ Presentation.
SUTHERLAND-2011 Sutherland, J. and Schwaber, K. (2011): The Scrum Papers: Nut, Bolt, and Origins of an Agile Framework. Draft, January 29, 2011, Scrum, Inc.
SUTHERLAND-2012 Sutherland, J. and Schwaber, K. (2012): The Scrum Papers: Nut, Bolt, and Origins of an Agile Framework. Version 1.1, April 2, 2012, Scrum, Inc.
T
TAKEUCHI-1986Takeuhci, I. and Nonaka, I. (1986): New New Product Development Game. Harvard Business Review Article.
TUCKMAN-1965Tuckman, B. W. (1965): Developmental Sequences in Small Groups.Psychological Bulletin, Vol 63(6), Jun 1965, 384-399.
U
V
W
WEBER-1992 Weber, J. (1992): Kahn the Barbarian. Los Angeles Times.
WEGNER-1997 Wegner, P. (1997): Why interaction is more powerful than algorithms.
WEGNER-1999 WEGNER-1999 Wegner P. and Goldin D (1999): Interaction, Computability, and Church’s Thesis. Draft, Brown University.
WEGNER-2006 Wegner P. and Goldin D (2006): Principles of Problem Solving. CACM, July 2006, V49 N7 PP27-29.
WOEPPEL-2005Woeppel, M. (2005): Projects in Less Time: A Synopsis of Critical Chain. Booksurge Publishing.
WOMACK-2003Womack, J. P. and Jones, D. T. (2003): Lean Thinking: Banish Waste and Create Wealth in Your Corporation, Revised and Updated. Free Press; 2nd edition.
X
Y
Z
ZIV-1996Ziv, H. et al (1996): The Uncertainty Principle in Software Engineering. 19th International Conference on Software Engineering.