Anderson, David J. Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press, 2010.
Arisholm, Erik, Hans Gallis, Tore Dyba, and Dag Sjoberg. “Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise.” IEEE Transactions on Software Engineering, Feb 2007.
Beck, Kent. Extreme Programming Explained: Embrace Change. Addison-Wesley, 1999.
—. Test-Driven Development by Example. Addison-Wesley, 2003.
Beedle, Mike, et al. Agile Manifesto. n.d. http://agilemanifesto.org/.
Boyd, Colonel John. The Essence of Winning and Losing. n.d. www.danford.net/boyd/essence.htm.
British Standards Institution. “BS 7850-1: Total quality management. Guide to management principles.” l992.
Carnegie Mellon University; Software Engineering Institute. Capability Maturity Model Integration. n.d. www.sei.cmu.edu/cmmi/.
Cockburn, Alistair, and Laurie Williams. “The Costs and Benefits of Pair Programming.” Proceedings of the First International Conference on Extreme Programming and Flexible Processes in Software Engineering (XP2000), 2000.
Cohn, Mike. Agile Estimating and Planning. Prentice Hall, 2005.
De Feo, Joseph, and William Barnard. JURAN Institute’s Six Sigma Breakthrough and Beyond – Quality Performance Breakthrough Methods. Tata McGraw-Hill Publishing, 2005.
De Luca, J, P Coad, and E Lefebvre. Java Modeling In Color With UML: Enterprise Components and Process. Prentice Hall International, 1999.
DeMarco, Tom, and Timothy Lister. Waltzing With Bears: Managing Risk on Software Projects. Dorset House, 2003.
Deming, W. Edwards. Out of the Crisis. Massachusetts Institute of Technology, 1982.
—. The New Economics for Industry, Government, Education. Massachusetts Institute of Technology, 1993.
Dennis, Pascal. Lean Production Simplified. Productivity Press, 2007.
Evans, James, and William Lindsay. The Management and Control of Quality. South-Western, 2008.
Fowler, Martin, and Kent Beck. Refactoring: Improving the Design of Existing Code. Addison-Wesley Professional, 1999.
Glazer, Hillel. “Love and Marriage: CMMI and Agile Need Each Other.” CROSSTALK: The Journal of Defense Software Engineering, Jan/Feb 2010.
Glazer, Hillel, Jeff Dalton, David Anderson, Mike Konrad, and Sandy Shrum. CMMI® or Agile: Why Not Embrace Both! Software Engineering Institute, 2008.
Goldratt, Eliyahu M, and Jeff Cox. The goal: a process of ongoing improvement. 1986.
Grenning, James. “Planning Poker or How to avoid analysis paralysis while release planning.” 2002.
Imai, Masaaki. Kaizen: The Key To Japan’s Competitive Success. McGraw-Hill, 1986.
Johnson, Brian, and John Higgins. Software Lifecycle; practical strategy and design principle. Van Haren Publishing, 2007.
Johnson, Brian, and Richard Warden. Software Lifecycle Support. H.M. Stationery Office, 1993.
Kaplan, Robert, and David P. Norton. The Balanced Scorecard: Translating Strategy Into Action. Harvard Business Press, 1996.
Kirkpatrick, Doug. Beyond Empowerment: The Age of the Self-Managed Organization. 2011.
Lu, David John, and Nihon Nōritsu Kyōkai. Kanban Just-in Time at Toyota: Management Begins at the Workplace. Productivity Press, 1986.
Lui, Kim Man, Keith Chan, and John Nosek. “The Effect of Pairs in Program Design Tasks.” IEEE Transactions on Software Engineering, Feb 2008.
MacDonald, W., and S. Bendak. “Effects of workload and 8- versus 12-h workday duration on test battery performance.” International Journal of Industrial Ergonomics, 2000.
Male, Mack D. Transforming the City of Edmonton IT Branch. 2009.
http://blog.mastermaq.ca/2009/07/02/transforming-the-city-of-edmonton-it-branch/.
Maslow, Abraham. Motivation and Personality. Harper and Row Publishers, 1987.
Ohno, Taiichi. Toyota Production System: Beyond Large-Scale Production. Productivity Press, 1988.
Organisation for Economic Co-operation and Development. OECD Principles of Corporate Governance. OECD Publications Service, 2004.
Palmer, S.R, and J.M Felsing. A Practical Guide to Feature-Driven Development. Prentice Hall, 2002.
Paulk, Mark C. “Extreme Programming from a CMM Perspective.” IEEE SOFTWARE, Nov/Dec 2001.
Proctor, S. P., R. F. White, T. G. Robins, D. Echeverria, and A. Z. Rocskay. “Effect of overtime work on cognitive function in automotive workers.” Scandinavian Journal of Work, Environment and Health, 1996.
Schwaber, Ken, and Jeff Sutherland. Scrum Guide. Scrum.org, 2011.
Schwaber, Ken, and Mike Beedle. Agile software development with Scrum. Prentice Hall, 2002.
Scrum Alliance. Scrum. n.d. http://scrum.org/.
Seo, Ji-Won. Better Work Discussion Paper Series No. 2. International Labour Organisation, 2011.
Socha, David, Tyler C. Folsom, and Joe Justice. “Applying Agile Software Principles and Practices for Fast Automotive Development.” Proceedings of the FISITA 2012 World Automotive Congress, Lecture Notes in Electrical Engineering Volume 196, 2013. Springer Berlin Heidelberg, 2012. pp 1033-1045.
Sutherland, Jeffrey, and Ken Schwaber. “Business object design and implementation.” OOPSLA ‘95 workshop proceedings, 1995.
Taleb, Nassim Nicholas. The Black Swan: The Impact of the Highly Improbable. Random House, 2007.
Virtanen, Marianna, et al. “Overtime work and incident coronary heart disease: the Whitehall II prospective cohort study.” European Heart Journal, 2010.
Wake, Bill. INVEST in Good Stories, and SMART Tasks. n.d. http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/.
Williams, Laurie, and Robert Kessler. Pair Programming Illuminated. Pearson Education Inc, 2003.
Womack, James P, Daniel T Jones, and Daniel Roos. The Machine That Changed the World. Harper Perennial, 1991.