References

Adkins, Lyssa. 2010. Coaching Agile Teams: A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition. Addison-Wesley Professional.

Anderson, David J. 2010. Kanban. Blue Hole Press.

Appelo, Jurgen. 2011. Management 3.0: Leading Agile Developers, Developing Agile Leaders. Addison-Wesley Professional.

Beck, Kent, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, and Dave Thomas. 2001. Manifesto for Agile Software Development. www.agilemanifesto.org/.

Beck, Kent, and Cynthia Andres. 2004. Extreme Programming Explained, 2nd ed. Addison-Wesley Professional.

Boehm, Barry W. 1981. Software Engineering Economics. Prentice Hall.

Brooks, Frederick P. 1995. The Mythical Man-Month: Essays on Software Engineering, 2nd ed. Addison-Wesley Professional. (Originally published in 1975.)

Cohn, Mike. 2004. User Stories Applied: For Agile Software Development. Addison-Wesley Professional.

Cohn, Mike. 2006. Agile Estimating and Planning. Addison-Wesley Professional.

Cohn, Mike. 2009. Succeeding with Agile. Addison-Wesley Professional.

Cohn, Mike. 2010. Agile 2010 keynote presentation.

Cook, Daniel. 2008. “The Laws of Productivity: 8 productivity experiments you don’t need to repeat.” Presentation found at http://www.lostgarden.com/2008/09/rules-of-productivity-presentation.html.

Crispin, Lisa, and Janet Gregory. 2009. Agile Testing: A Practical Guide for Testers and Agile Teams. Addison-Wesley Professional.

Cunningham, Ward. 1992. “The WyCash Portfolio Management System,” OOPSLA 1992 experience report. OOPSLA ’92, Object-Oriented Programming Systems, Languages and Applications, Vancouver, BC, Canada, October 18–22.

Denne, Mark, and Jane Cleland-Huang. 2003. Software by Numbers: Low-Risk, High-Return Development. Prentice Hall.

Derby, Esther, and Diana Larsen. 2006. Agile Retrospectives: Making Good Teams Great. Pragmatic Bookshelf.

Fowler, Martin. 2009. “Technical Debt Quadrant.” Bliki entry found at http://martinfowler.com/bliki/TechnicalDebtQuadrant.html.

Fowler, Martin, Kent Beck, John Brant, William Opdyke, and Don Roberts. 1999. Refactoring: Improving the Design of Existing Code. Addison-Wesley Professional.

Goldberg, Adele, and Kenneth S. Rubin. 1995. Succeeding with Objects: Decision Frameworks for Project Management. Addison-Wesley Professional.

Grenning, James. 2002. “Planning Poker.” www.objectmentor.com/resources/articles/PlanningPoker.zip.

Highsmith, Jim. 2009. Agile Project Management: Creating Innovative Products, 2nd ed. Addison-Wesley Professional.

Hohmann, Luke. 2003. Beyond Software Architecture. Addison-Wesley Professional.

IEEE. 1990. IEEE Std 610.12-1990 (revision and designation of IEEE Std 792-1983). IEEE Standards Board of the Institute of Electrical and Electronics Engineers, New York, September 28, 1990.

Jeffries, Ron. 2001. “Essential XP: Card, Conversation, Confirmation.” http://xprogramming.com/articles/expcardconversationconfirmation/.

Katz, Ralph. 1982. “The Effects of Group Longevity on Project Communication and Performance.” Administrative Science Quarterly 27: 81–104.

Kennedy, John Fitzgerald. 1961. Special Message to the Congress on Urgent National Needs, May 22.

Kerth, Norm. 2001. Project Retrospectives: A Handbook for Team Reviews. Dorset House.

Larman, Craig, and Bas Vodde. 2009. “Lean Primer.” Downloadable from www.leanprimer.com/downloads/lean_primer.pdf.

Laufer, Alexander. 1996. Simultaneous Management: Managing Projects in a Dynamic Environment. American Management Association.

Leffingwell, Dean. 2011. Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Addison-Wesley Professional.

McConnell, Steve. 2007. “Technical Debt.” Blog entry found at http://blogs.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspx.

Mar, Kane. 2006. “Technical Debt and the Death of Design: Part 1.” Blog entry found at http://kanemar.com/2006/07/23/technical-debt-and-the-death-of-design-part-1/.

Martin, Robert C. 2008. Clean Code: A Handbook of Agile Software Craftsmanship. Prentice Hall.

Page, Scott. 2007. The Difference: How the Power of Diversity Creates Better Groups, Firms, Schools, and Societies. Princeton University Press.

Patton, Jeff. 2008. Example of incremental releasing. Personal communication.

Patton, Jeff. 2009. “Telling Better User Stories: Mapping the Path to Success.” Better Software, November/December, 24–29.

Pelrine, Joseph. 2011. “Is Software Development Complex.” Guest blog entry found at http://cognitive-edge.com/blog/entry/4597/is-software-development-complex.

Pichler, Roman. 2010. Agile Product Management with Scrum: Creating Products That Customers Love. Addison-Wesley Professional.

PMI. 2008. A Guide to the Project Management Body of Knowledge (PMBOK^® Guide), 4th ed. Project Management Institute, Inc.

Poppendieck, Mary, and Tom Poppendieck. 2003. Lean Software Development: An Agile Toolkit. Addison-Wesley Professional.

Putnam, Doug. 1996. “Team Size Can Be the Key to a Successful Project.” An article in QSM’s Process Improvement Series. www.qsm.com/process_01.html.

Putnam, Lawrence H., and Ware Myers. 1998. “Familiar Metrics Management: Small Is Beautiful—Once Again.” IT Metrics Strategies IV:8: 12–16. Cutter Information Corp.

Reinertsen, Donald G. 2009a. “Types of Processes.” Guest blog entry found at www.netobjectives.com/blogs/Types-of-Processes.

Reinertsen, Donald G. 2009b. The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing.

Ries, Eric. 2011. The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Business.

Schwaber, Ken. 1995. “Scrum Development Process.” In OOPSLA Business Object Design and Implementation Workshop, ed. J. Sutherland et al. Springer.

Schwaber, Ken. 2004. Agile Software Development with Scrum. Microsoft Press.

Schwaber, Ken, and Mike Beedle. 2001. Agile Software Development with Scrum. Prentice Hall.

Schwaber, Ken, and Jeff Sutherland. 2011. “The Scrum Guide.” Downloadable at www.scrum.org.

SEI. 2010. “CMMI for Development, Version 1.3.” Software Engineering Institute, Carnegie Mellon University. Downloadable at www.sei.cmu.edu/library/abstracts/reports/10tr033.cfm.

SEI. 2011. Second International Workshop on Managing Technical Debt, May 23. Colocated with ICSE 2011, Waikiki, Honolulu, Hawaii. Downloadable at www.sei.cmu.edu/community/td2011/.

Smith, Preston G., and Donald G. Reinertsen. 1998. Developing Products in Half the Time: New Rules, New Tools. Van Nostrand Reinhold.

Snowden, David J., and Mary E. Boone. 2007. “A Leader’s Framework for Decision Making.” Harvard Business Review, November.

Staats, Bradley R. 2011. Unpacking Team Familiarity: The Effects of Geographic Location and Hierarchical Role. University of North Carolina at Chapel Hill.

Takeuchi, Hirotaka, and Ikujiro Nonaka. 1986. “The New New Product Development Game.” Harvard Business Review, January, 137–146.

Tuckman, Bruce W. 1965. “Developmental Sequence in Small Groups.” Psychological Bulletin 63: 384–399. The article was reprinted in Group Facilitation: A Research and Applications Journal, no. 3, Spring 2001.

VersionOne. 2011. “The State of Agile Development: Sixth Annual Survey.” Posted as a downloadable PDF in the Library of White Papers on www.versionone.com.

Wake, William C. 2003. “INVEST in Good Stories, and SMART Tasks.” www.xp123.com.

Wheelwright, Steven C., and Kim B. Clark. 1992. Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency, and Quality. The Free Press.

Wiseman, John “Lofty.” 2010. SAS Survival Guide: For Any Climate, in Any Situation, rev. ed. Collins Reference.