References

[Ambler & Sadalage] Ambler, Scott, and Pramodkumar Sadalage. 2006. Refactoring Databases: Evolutionary Database Design. Boston: Addison-Wesley Professional..

[Anderson 2003] Anderson, David. 2003. Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results. Upper Saddle River, NJ: Prentice Hall..

[Anderson 2006] Anderson, David. 2006. “HP gets 3.4x productivity gain from Agile Management techniques” (posted March 15). Agile Management blog. http://www.agilemanagement.net/Articles/Weblog/HPgets3.4xproductivitygai.html.

[Astels] Astels, David. 2003. Test Driven Development: A Practical Guide. Upper Saddle River, NJ: Prentice Hall..

[Bach 1999] Bach, James. 1999. “General Functionality and Stability Test Procedure for Microsoft Windows Logo, Desktop Applications Edition.” http://www.testingcraft.com/bach-exploratory-procedure.pdf.

[Bach 2000] Bach, Jonathan. 2000. “Session-Based Test Management.” http://www.satisfice.com/articles/sbtm.pdf.

[Beck 1999] Beck, Kent. 1999. Extreme Programming Explained, First edition. Boston: Addison-Wesley Professional..

[Beck 2002] Beck, Kent. 2002. Test Driven Development: By Example. Boston: Addison-Wesley Professional..

[Beck 2004] Beck, Kent. 2004. Extreme Programming Explained, Second edition. Boston: Addison-Wesley Professional..

[Beck & Fowler] Beck, Kent, and Martin Fowler. 2000. Planning Extreme Programming. Boston: Addison-Wesley Professional..

[Beck et al.] Beck, Kent et al. 2001. Manifesto for Agile Software Development. http://agilemanifesto.org/.

[Belshee] Belshee, Arlo. 2005. “Promiscuous Pairing and Beginner’s Mind: Embrace Inexperience.” Proceedings of the Agile Development Conference (July 24-29). Washington, DC: IEEE Computer Society, 125-131. http://dx.doi.org/10.1109/ADC.2005.37.

[Berczuk & Appleton] Berczuk, Stephen P., and Brad Appleton. 2002. Software Configuration Management Patterns: Effective Teamwork, Practical Integration. Boston: Addison-Wesley Professional..

[Boehm] Boehm, Barry. 1987. “Industrial Software Metrics Top 10 List.” IEEE Software. 4(9): 84-85..

[Brooks] Brooks, Frederick P. 1995. The Mythical Man-Month: Essays on Software Engineering, 20th Anniversary Edition. Boston: Addison-Wesley Professional..

[Cockburn] Cockburn, Alistair. 2001. Agile Software Development. Boston: Addison-Wesley Professional..

[Cockburn & Williams] Cockburn, Alistair, and Laurie Williams. 2001. “The Costs and Benefits of Pair Programming.” Extreme Programming Examined. Eds Succi, G., Marchesi, M., 223-247. Boston: Addison-Wesley. http://www.cs.utah.edu/~lwilliam/Papers/XPSardinia.PDF.

[Coffin] Coffin, Rod. 2006. “A Tale of Two Projects.” The Conference on AGILE 2006 (July 23-28). Washington, DC: IEEE Computer Society, 155-164. http://dx.doi.org/10.1109/AGILE.2006.3.

[Cohn] Cohn, Mike. 2005. Agile Estimating and Planning. Upper Saddle River, NJ: Prentice Hall..

[Constantine] Constantine, Larry. 1968. “Segmentation and Design Strategies for Modular Programming.” Eds. T. O. Barnett and L. L. Constantine. Modular Programming: Proceedings of a National Symposium. Cambridge, MA: Information & Systems Press..

[Cunningham] Cunningham, Ward. 1994. “The CHECKS Pattern Language of Information Integrity.” http://c2.com/ppr/checks.html.

[DeMarco 1995] DeMarco, Tom. 1995. Why Does Software Cost So Much?: And Other Puzzles of the Information Age. New York: Dorset House Publishing Co..

[DeMarco 2002] DeMarco, Tom. 2002. Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency. New York: Broadway Books..

[DeMarco & Lister 1999] DeMarco, Tom, and Timothy Lister. 1999. Peopleware: Productive Projects and Teams. New York: Dorset House Publishing Co..

[DeMarco & Lister 2003] DeMarco, Tom, and Timothy Lister. 2003. Waltzing With Bears: Managing Risk on Software Projects. New York: Dorset House Publishing Co..

[Denne & Cleland-Huang] Denne, Mark, and Jane Cleland-Huang. 2003. Software by Numbers: Low-Risk, High-Return Development. Upper Saddle River, NJ: Prentice Hall..

[Derby & Larsen] Derby, Esther, and Diana Larsen. 2006. Agile Retrospectives: Making Good Teams Great. Raleigh and Dallas: Pragmatic Bookshelf..

[Evans] Evans, Eric. 2003. Domain-Driven Design: Tackling Complexity in the Heart of Software. Boston: Addison-Wesley Professional..

[Feathers] Feathers, Michael. 2004. Working Effectively with Legacy Code. Upper Saddle River, NJ: Prentice Hall..

[Fowler 1999] Fowler, Martin. 1999. Refactoring: Improving the Design of Existing Code//citetitle>. Boston: Addison-Wesley Professional.. .

[Fowler 2000] Fowler, Martin. 2000. “Is Design Dead?” http://www.martinfowler.com/articles/designDead.html.

[Fowler 2002a] Fowler, Martin. 2002. Patterns of Enterprise Application Architecture. Boston: Addison-Wesley Professional..

[Fowler 2002b] Fowler, Martin. 2002. “Yet Another Optimization Article.” http://www.martinfowler.com/ieeeSoftware/yetOptimization.pdf.

[Fowler 2003] Fowler, Martin. 2003. “Cannot Measure Productivity.” http://www.martinfowler.com/bliki/CannotMeasureProductivity.html.

[Fowler & Scott] Fowler, Martin, and Kendall Scott. 1999. UML Distilled: A Brief Guide to the Standard Object Modeling Language, Second Edition. Boston: Addison-Wesley Professional..

[Gamma et al.] Gamma, Erich, Richard Helm, Ralph Johnson, and John Vlissides ["Gang of Four"]. 1995. Design Patterns: Elements of Reusable Object-Oriented Software. Boston: Addison-Wesley Professional..

[Goldratt 1992] Goldratt, Eliyahu M. 1992. The Goal: A Process of Ongoing Improvement. Great Barrington, MA: North River Press..

[Goldratt 1997] Goldratt, Eliyahu M. 1997. Critical Chain: A Business Novel. Great Barrington, MA: North River Press..

[Hendrickson] Hendrickson, Elisabeth. 2006. “Rigorous Exploratory Testing” (posted April 19). http://www.testobsessed.com/2006/04/19/rigorous-exploratory-testing/.

[Highsmith] Highsmith, Jim. 2002. Agile Software Development Ecosystems. Boston: Addison-Wesley Professional..

[Hunt & Thomas] Hunt, Andrew, and David Thomas. 1999. The Pragmatic Programmer: From Journeyman to Master. Boston: Addison-Wesley Professional..

[Hunter] Hunter, Michael ["The Braidy Tester"] 2004. “Did I Remember To” (posted July 7). http:// blogs.msdn.com/micaheVarticles/175571.aspx.

[Janzen & Saiedian] Janzen, David, and Hossein Saiedian. 2005. “Test-Driven Development: Concepts, Taxonomy, and Future Direction.” IEEE Computer Society. 38(9): 43-50..

[Jeffries et al.] Jeffries, Ron, Ann Anderson, and Chet Hendrickson. 2000. Extreme Programming Installed. Boston: Addison-Wesley Professional..

[Kaner] Kaner, Cem. 1987. Testing Computer Software. Blue Ridge Summit, PA: TAB Books..

[Katzenbach & Smith] Katzenbach, Jon R., and Douglas K. Smith. 1994. The Wisdom of Teams: Creating the High-Performance Organization. New York: HarperBusiness..

[Kerievsky] Kerievsky, Joshua. 2004. Refactoring to Patterns. Boston: Addison-Wesley Professional..

[Kerth] Kerth, Norman. 2001. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House Publishing Co..

[Kohl 2005a] Kohl, Jonathan. 2005. “User Profiles and Exploratory Testing” (posted June 12). http://www.kohl.ca/blog/archives/000104.html.

[Kohl 2005b] Kohl, Jonathan. 2005. “Exploratory Testing on Agile Teams.” InformIT, Nov 18. http://www.informit.com/articles/article.aspx?p=405514.

[Kohn] Kohn, Alfie. 1999. Punished By Rewards: The Trouble with Gold Stars, Incentive Plans, A’s, Praise, and Other Bribes. Boston: Mariner Books..

[Lacey] Lacey, Mitch. 2006. “Adventures in Promiscuous Pairing: Seeking Beginner’s Mind.” Proceedings of the Conference on AGILE 2006 (July 23-28). Washington, DC: IEEE Computer Society, 263-269. http://dx.doi.org/10.1109/AGILE.2006.7.

[Little] Little, Todd. 2006. “Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty.” IEEE Software. 23(3): 48-54. http://www.toddlittleweb.com/Papers/Little%20Cone%20of%20Uncertainty.pdf.

[Mah] Mah, Michael. 2006. “Agile Productivity Metrics” Keynote Address, Better Software Conference & EXPO, Las Vegas, June 2006. http://www.sqe.com/Events/Archive/bsc2006/keynotes.html.

[Maister et al] Maister, David, Charles Green, Robert Galford. 2000. The Trusted Advisor. New York: Free Press..

[Manns & Rising] Manns, Mary Lynn, and Linda Rising. 2004. Fearless Change: Patterns for Introducing New Ideas. Boston: Addison-Wesley..

[Marick] Marick, Brian. A Survey of Exploratory Testing. http://www.testingcraft.com/exploratory.html.

[Martin 2002] Martin, Robert C. 2002. Agile Software Development, Principles, Patterns, and Practices. Upper Saddle River, NJ: Prentice Hall..

[Martin 2005] Martin, Robert C. 2005. “Clean Code: Args—A Command-line Argument Parser.” Published on the Object Mentor, Inc. web site (Nov 26). http://www.objectmentor.com/resources/articles/Clean_Code_Args.pdf.

[Mason] Mason, Mike. 2006. Pragmatic Version Control: Using Subversion (The Pragmatic Starter Kit Series), Second Edition. Raleigh and Dallas: Pragmatic Bookshelf..

[McConnell 1996] McConnell, Steve. 1996. Rapid Development: Taming Wild Software Schedules. Redmond, WA: Microsoft Press..

[McConnell 2005] McConnell, Steve. 2006. Software Estimation: Demystifying the Black Art. Redmond, WA: Microsoft Press..

[Meyer] Meyer, Bertrand. 2000. Object-Oriented Software Construction, Second Edition. Upper Saddle River, NJ: Prentice Hall..

[Miller] Miller, Charles. 2003. “Stand-Up Meeting Antipatterns” (posted November 19). The Fishbowl blog. http://fishbowl.pastiche.org/2003/11/19/standup_meeting_antipatterns.

[Montagna] Montagna, Frank C. 1996. “The Effective Postfire Critique.” Fire Engineering magazine, July 1. http://www.chiefmontagna.com/Articles/pdf/critique.pdf.

[Mugridge & Cunningham] Mugridge, Rick, and Ward Cunningham. 2005. Fit for Developing Software: Framework for Integrated Tests. Upper Saddle River, NJ: Prentice Hall..

[Nielsen] Nielsen, Jakob. 1999. Designing Web Usability: The Practice of Simplicity. Berkeley, CA: Peachpit Press..

[Overby] Overby, Stephanie. 2003. “The Hidden Costs of Offshore Outsourcing – Offshore Outsourcing the Money.” CIO. magazine, Sept 1. http://www.cio.com/archive/090103/money.html.

[Poppendieck & Poppendieck] Poppendieck, Mary, and Tom Poppendieck. 2003. Lean Software Development: An Agile Toolkit for Software Development Managers. Boston: Addison-Wesley Professional..

[Pugh] Pugh, Ken. 2005. Prefactoring. Sebastopol, CA: O’Reilly Media, Inc..

[Rainsberger] Rainsberger, J. B. 2004. Junit Recipes: Practical Methods for Programmer Testing. Greenwich, CT: Manning Publications, Co..

[Rooney] Rooney, Dave. 2006. “The Disengaged Customer” (posted Jan 20). The Agile Artisan blog. http://agileartisan.blogspot.com/2006/01/disengaged-customer-introduction.html.

[Schwaber & Beedle] Schwaber, Ken, and Mike Beedle. 2001. Agile Software Development with SCRUM. Upper Saddle River, NJ: Prentice Hall..

[Shore 2004a] Shore, Jim. 2004. “Continuous Design.” IEEE Software 21(1):20-22. http://www.martinfowler.com/ieeeSoftware/continuousDesign.pdf.

[Shore 2004b] Shore, Jim. 2004. “Fail Fast.” IEEE Software 21(5):21-25. http://www.martinfowler.com/ieeeSoftware/failFast.pdf.

[Shore 2005a] Shore, Jim. 2005. “Agile Requirements” (posted Nov 30). http://www.jamesshore.com/Blog/Agile-Requirements.html.

[Shore 2005b] Shore, Jim. 2005. Agile development resources. http://c2.com/cgi/wiki?JimShore.

[Sink] Sink, Eric. 2004. “Source Control HOWTO” (posted Aug 27). Eric Weblog. http://www.ericsink.com/scm/source_control.html.

[Smith] Smith, Steven M. 1997. “The Satir Change Model” (posted Oct 4). Steven M. Smith & Associates, LLC. http://www.stevenmsmith.com/my-articles/article/the-satir-change-model.html.

[Standish] Standish Group. 1994. “The CHAOS Report.” The Standish Group International, Inc. http://www.standishgroup.com/sample_research/chaos_1994_1.php.

[Stapleton] Stapleton, Jennifer. 1997. DSDM: A Framework for Business Centered Development. Boston: Addison-Wesley Professional..

[Subramaniam & Hunt] Subramaniam, Venkat, and Andy Hunt. 2006. Practices of an Agile Developer: Working in the Real World. Raleigh and Dallas: Pragmatic Bookshelf..

[Teasley et al.] Teasley, Stephanie, Lisa Covi, M. S. Krishnan, Judith Olson. 2002. “Rapid Software Development Through Team Collocation.” IEEE Trans. Softw. Eng. 28(7):671-83. http://dx.doi.org/10.1109/TSE.2002.1019481.

[Tinkham & Kaner] Tinkham, Andy, and Cem Kaner. 2003. “Exploring Exploratory Testing.” Presented at SQE’s Software Testing, Analysis & Review Conference, Orlando, FL, July 2003. http://www.testingeducation.org/a/explore.pdf.

[Tuckman] Tuckman, B. W. 1965. “Developmental sequences in small groups.” Psychological Bulletin 63:384-99. http://dennislearningcenter.osu.edu/references/GROUP%20DEV%20ARTICLE.doc.

[Ury] Ury, William. 2007. The Power of a Positive No: How to Say No and Still Get to Yes. New York: Bantam Books..

[Van Schooenderwoert] Van Schooenderwoert, Nancy. 2006. “Embedded Agile Project by the Numbers with Newbies.” The Conference on AGILE 2006 (July 23-28). Washington, DC: IEEE Computer Society, 351-366. http://dx.doi.org/10.1109/AGILE.2006.24.

[Wiegers 1999] Wiegers, Karl E. 1999. Software Requirements. Redmond, WA: Microsoft Press..

[Wiegers 2001] Wiegers, Karl E. 2001. Peer Reviews in Software: A Practical Guide. Boston: Addison-Wesley Professional..

[Williams] Williams, Laurie. 2002. Pair Programming Illuminated. Boston: Addison-Wesley Professional..

[Wirfs-Brock & McKean] Wirfs-Brock, Rebecca, and Alan McKean. 2002. Object Design: Roles, Responsibilities, and Collaborations. Boston: Addison-Wesley Professional..

[Yap] Yap, Monica. 2005. “Follow the Sun: Distributed Extreme Programming Development.” The Conference on AGILE 2006 (July 23-28). Washington, DC: IEEE Computer Society, 218-224. http://dx.doi.org/10.1109/ADC.2005.26.

[Yip] Yip, Jason. 2006. “It’s Not Just Standing Up: Patterns of Daily Stand-up Meetings.” http://www.martinfowler.com/articles/itsNotJustStandingUp.html.

[Yourdon] Yourdon, Edward. 1999. Death March: The Complete Software Developer’s Guide to Surviving ‘Mission Impossible’ Projects. Upper Saddle River, NJ: Prentice Hall..