Reference List

| September 10, 2009 | 0 Comments

Adler, Paul S., Avi Mandelbaum, Vien Nguyen, and Elizabeth Schwerer. 1996. Getting the most out of your product development process. Harvard Business Review, March–April, 13–151.

Adzic, Gojko. 2009.Bridging the communication gap: Specification by example and agile acceptance testing. Neuri Limited.

Allen-Meyer, Glenn. 2000a. Nameless organizational change: No-hype, low-resistance corporate transformation. Syracuse University Press.

Allen-Meyer, Glenn. 2000b. Overview: Nameless organizational change; No-hype, low-resistance corporate transformation. Previously available at http://www.nameless.org.

Allen-Meyer, Glenn. 2000c. 21st century schizoid change. OD Practitioner 32 (3): 22–26.

Ambler, Scott. 2008a. Agile adoption rate survey, February.

———. 2008b. Scott Ambler on agile’s present and future. Interview by Floyd Marinescu. InfoQ website, December 1.

———. n.d. Agile Data Home Page.

Ambler, Scott W., and Pramod J. Sadalage. 2006. Refactoring databases:
Evolutionary database design
. Addison-Wesley.

Anderson, Philip. 1999. Seven levers for guiding the evolving enterprise. In The biology of business: Decoding the natural laws of enterprise, ed. John Henry Clippinger III, 113–152. Jossey-Bass.

Appelo, Jurgen. 2008. We increment to adapt, we iterate to improve. Methods & Tools, Summer, 9–22.

Armour, Phillip G. 2006. Software: Hard data. Communications of the ACM, September, 15–17.

Avery, Christopher M. 2005. Responsible change. Cutter Consortium Agile Project Management Executive Report 6 (10): 1–28.

Avery, Christoper M., Meri Aaron Walker, and Erin O’Toole. 2001. Teamwork is an individual skill: Getting your work done when sharing responsibility. Berrett-Koehler Publishers

Babinet, Eric, and Rajani Ramanathan. 2008. Dependency management in a large agile environment. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 401–406. IEEE Computer Society.

Bain, Scott L. 2008. Emergent design: The evolutionary nature of professional software development. Addison-Wesley Professional.

Barnett, Liz. 2005. Metrics for agile development projects: Emphasize value and customer satisfaction. With Carey Schwaber and Lindsay Hogan. Forrester.

———. 2008. Incremental agile adoption. Agile Journal, February 11.

Beavers, Paul A. 2007. Managing a large “agile” software engineering organization. In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 296–303. IEEE Computer Society.

Beck, Kent. 2002. Test-driven development: By example. Addison-Wesley Professional.

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

———. 2005. Getting started with XP: Toe dipping, racing dives, and cannonballs. PDF file at Three Rivers Institute website.

Beck, Kent, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, et al. 2001. Manifesto for agile software development.

Benefield, Gabrielle. 2008. Rolling out agile in a large enterprise. In Proceedings of the 41st Annual Hawaii International Conference on System Sciences, 461–470. IEEE Computer Society.

Boehm, Barry W. 1981. Software engineering economics. Prentice Hall.

Boehm, Barry, and Richard Turner. 2005. Management challenges to implementing agile processes in traditional development organizations. IEEE Software, September/October, 30–39.

Bos, Erik, and Christ Vriens. 2004. An agile CMM. In Extreme Programming and Agile Methods: XP/Agile Universe 2004, ed. C. Zannier, H. Erdogmus, and L. Lindstrom, 129–138. Springer.

Bradner, E., G. Mark, and T.D. Hertel. 2003. Effects of team size on participation, awareness, and technology choice in geographically distributed teams. In Proceedings of the 36th Annual Hawaii International Conference on System Sciences, 271a. IEEE Computer Society.

Bridges, William. 2003. Managing transitions: Making the most of change. 2nd ed. Da Capo Press.

Brodwall, Johannes. 2008. An informative workplace. Thinking inside a bigger box, November 23.

Brooks, Frederick P. 1995. The mythical man-month: Essays on software engineering. 2nd ed. Addison-Wesley Professional. (Orig. pub. 1975.)

Campbell, Donald T. 1965. Variation and selective retention in socio-cultural evolution. In Social change in developing areas: A reinterpretation of evolutionary theory, ed.  Herbert R. Barringer, George I. Blanksten, and Raymond W. Mack, 19–49. Schenkman.

Cao, Lan, and Balasubramaniam Ramesh. 2008. Agile requirements engineering practices:  An empirical study. IEEE Software, January/February, 60–67.

Carmel, Erran. 1998. Global software teams: Collaborating across borders and time zones. Prentice Hall.

Carr, David K., Kelvin J. Hard, and William J. Trahant. 1996. Managing the change process: A field book for change agents, team leaders, and reengineering managers. McGraw-Hill.

Catmull, Ed. 2008. How Pixar fosters collective creativity. Harvard Business Review, September, 65–72.

Cichelli, Sharon. 2008. Globally distributed Scrum. Girl Writes Code blog entry, May 9.

Cirillo, Francesco. 2007. The pomodoro technique. PDF from website of same name.

Clark, Kim B., and Steven C. Wheelwright. 1992. Managing new product and process development:  Text and cases. The Free Press.

Cockburn, Alistair. 2000. Balancing lightness with sufficiency. Cutter IT Journal, November.

———. 2006. Agile software development: The cooperative game. 2nd ed. Addison-Wesley Professional.

———. 2008. Using both incremental and iterative development. Crosstalk, May, 27–30.

Cohn, Mike. 2004. User stories applied: For agile software development. Addison-Wesley Professional.

———. 2005. Agile estimating and planning. Addison-Wesley Professional.

Conner, Daryl R. 1993. Managing at the speed of change:  How resilient managers succeed and prosper where others fail. Random House.

Conway, Melvin E. 1968. How do committees invent? Originally published in Datamation, April 1968.

Cooper, Robert G. 2001. Winning at new products: Accelerating the process from idea to launch. 3rd ed. Basic Books.

Coyne, Kevin P., Patricia Gorman Clifford, and Renée Dye. 2007. Breakthrough thinking from inside the box. Harvard Business Review, December, 71–78.

Creasey, Tim, and Jeff Hiatt, eds. 2007. Best practices in change management. Prosci.

Crispin, Lisa, and Janet Gregory. 2009. Agile testing: A practical guide for testers and agile teams. Addison-Wesley Professional.

Crosby, Philip. 1979. Quality is free: The art of making quality certain. McGraw-Hill.

Cunningham, Ward. 1992. The WyCash portfolio management system. In Addendum to the Proceedings on Object-Oriented Programming Systems, Languages, and Applications, 29–30.

Davies, Rachel, and Liz Sedley. 2009. Agile coaching. The Pragmatic Bookshelf.

Deemer, Pete, Gabrielle Benefield, Craig Larman, and Bas Vodde. 2008. The Scrum primer. Scrum Training Institute.

DeGrace, Peter, and Leslie Hulet Stahl. 1990. Wicked problems, righteous solutions: A catalogue of modern software engineering paradigms. Prentice Hall.

DeMarco, Tom, Peter Hruschka, Tim Lister, Suzanne Robertson, James Roberts, and Steve McMenamin. 2008. Adrenaline junkies and template zombies: Understanding patterns of project behavior. Dorset House.

DeMarco, Tom, and Timothy Lister. 1999. Peopleware: Productive projects and teams. 2nd ed. Dorset House.

Deming, W. Edwards. 2000. Out of the Crisis. MIT Press.

de Pillis, Emmeline, and Kimberly Furumo. 2007. Counting the cost of virtual teams. Communications of the ACM, December, 93–95.

Derby, Esther. 2006. A manager’s guide to supporting organizational change. Crosstalk, January, 17–19.

Derby, Esther, and Diana Larsen. 2006. Agile retrospectives: Making good teams great. Pragmatic Bookshelf.

Deutschman, Alan. 2007. Inside the mind of Jeff Bezos. Fast Company, December 19.

Dinwiddie, George. 2007. Common areas at the heart. In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 207–211. IEEE Computer Society.

Drummond, Brian Scott, and John Francis “JF” Unson. 2008. Yahoo! distributed agile: Notes from the world over. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 315–321. IEEE Computer Society.

Duarte, Deborah L., and Nancy Tennant Snyder. 2006. Mastering virtual teams: Strategies, tools, and techniques that succeed. 3rd ed. Jossey-Bass.

Duck, Jeanie Daniel. 1993. Managing change: The art of balancing. Harvard Business Review, November–December, 109–119.

Duvall, Paul, Steve Matyas, and Andrew Glover. 2007. Continuous integration: Improving software quality and reducing risk. Addison-Wesley Professional.

Dybå, Tore, Erik Arisholm, Dag I. K. Sjøberg, Jo Erskine Hannay, and Forrest Shull. 2007.  Are two heads better than one? On the effectiveness of pair programming. IEEE Software, June, 12–15.

Edmondson, Amy, Richard Bohmer, and Gary Pisano. 2001. Speeding up team learning.  Harvard Business Review, October, 125–132.

Elssamadisy, Amr. 2007. Patterns of agile practice adoption: The technical cluster. C4Media.

Emery, Dale H. 2001. Resistance as a resource. Cutter IT Journal, October.

Eoyang, Glenda Holladay. 2001. Conditions for self-organizing in human systems. PhD diss., The Union Institute and University.

Feathers, Michael. 2004. Working effectively with legacy code. Prentice Hall PTR.

Fecarotta, Joseph. 2008. MyBoeingFleet and agile software development. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 135–139. IEEE Computer Society.

Feynman, Richard P. 1997. Surely you’re joking, Mr. Feynman! Adventures of a curious character. W. W. Norton & Co.

Fisher, Kimball. 1999. Leading self-directed work teams. McGraw-Hill.

Florida, Richard, and James Goodnight. 2005. Managing for creativity. Harvard Business Review, July, 125–131.

Fowler, Martin. 1999. Refactoring: Improving the design of existing code. With contributions by Kent Beck, John Brant, William Opdyke, and Don Roberts. Addison-Wesley Professional.

Fowler, Martin. 2006. Using an agile software process with offshore development. Martin Fowler’s personal website, July 18.

Fry, Chris, and Steve Greene. 2007. Large scale agile transformation in an on-demand world. In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 136–142. IEEE Computer Society.

Gabardini, Juan. 2008. E-mail to Scrum Development mailing list, February 23. http://
groups.yahoo.com/group/scrumdevelopment/message/25071.

Gates, Bill. 1995. E-mail to Microsoft executive staff and his direct reports, May 26. Down loaded from the US Department of Justice online case files.

George, Boby, and Laurie Williams. 2003. An initial investigation of test-driven development in industry. In SAC ’03: Proceedings of the 2003 ACM symposium on applied computing, 1135–1139. ACM.

Gilb, Tom. 1988. Principles of Software Engineering Management. Addison-Wesley Professional.

Gilb, Tom. 2005. Competitive Engineering: A handbook for systems engineering, requirements engineering, and software engineering using planguage. Butterworth-Heinemann.

Gladwell, Malcolm. 2002. The tipping point: How little things can make a big difference. Back Bay Books.

Glazer, Hillel, Jeff Dalton, David Anderson, Mike Konrad, and Sandy Shrum. 2008. CMMI or agile: Why not embrace both! Software Engineering Institute at Carnegie Mellon, November.

Goldberg, Adele, and Kenneth S. Rubin. 1995. Succeeding with objects: Decision frameworks for project management. Addison-Wesley Professional.

Goldstein, Jeffrey. 1994. The unshackled organization: Facing the challenge of unpredictability through spontaneous reorganization. Productivity Press.

Gonzales, Victor M., and Gloria Mark. 2004. Constant, constant, multi-tasking craziness: Managing multiple working sphere Managing multiple working spheres. In Proceedings of the CHI 2004 Connect Conference, 113–120. ACM.

Gratton, Lynda. 2007. Hot spots: Why some teams, workplaces, and organizations buzz with energy—and others don’t. Berrett-Koehler Publishers.

Gratton, Lynda, Andreas Voigt, and Tamara J. Erickson. 2007. Bridging faultlines in diverse teams. MIT Sloan Management Review, Summer, 22–29.

Greene, Steve. 2007. Wall posting on the Facebook page of Adaptive Development Methodology (ADM), October 27.

———. 2008. Unleashing the fossa: Scaling agile in an ambitious culture. Session presented at Agile Leadership Summit, Orlando.

Greene, Steve, and Chris Fry. 2008. Year of living dangerously: How Salesforce.com delivered extraordinary results through a “big bang” enterprise agile revolution. Session presented at Scrum Gathering, Stockholm.

Griskevicius, V., R. B. Cialdini, and N. J. Goldstein. 2008. Applying (and resisting) peer influence. MIT Sloan Management Review, Winter, 84–88.

Grossman, Lev. 2005. How Apple does it. Time, October 24, 66–70.

Hackman, J. Richard. 2002. Leading Teams: Setting the stage for great performances. Harvard Business School Press.

Hackman, J. Richard, and Diane Coutu. 2009. Why teams don’t work. Harvard Business Review, May, 98–105.

Hiatt, Jeffrey. 2006. ADKAR: A model for change in business, government and our community. Prosci Research.

Highsmith, Jim. 2002. Agile software development ecosystems. Addison-Wesley.

———. 2005. Managing change: Three readiness tests. E-Mail Advisor, July 14. Cutter Consortium.

———. 2009. Agile project management: Creating innovative products. 2nd ed. Addison-Wesley Professional.

Hodgetts, Paul. 2004. Refactoring the development process: Experiences with the incremental adoption of agile practices. In Proceedings of the Agile Development Conference, 106–113. IEEE Computer Society.

Hofstede, Geert, and Gert-Jan Hofstede. 2005. Cultures and organizations: Software of the mind. 2nd ed. McGraw-Hill.

Hogan, Ben. 2006. Lessons learned from an extremely distributed project. In Proceedings of the Agile 2006 conference, ed. Joseph Chao, Mike Cohn, Frank Maurer, Helen Sharp, and James Shore, 321–326. IEEE Computer Society.

Honious, Jeff, and Jonathan Clark. 2006. Something to believe in. In Proceedings of the Agile 2006 conference, ed. Joseph Chao, Mike Cohn, Frank Maurer, Helen Sharp, and James Shore, 203–212. IEEE Computer Society.

Hubbard, Douglas W. 2007. How to Measure Anything:  Finding the “Invaluables” in Business. Wiley.

Iacovou, Charalambos L., and Robbie Nakatsu. 2008. A risk profile of offshore-outsourced development projects. Communications of the ACM, June, 89–94.

James, Michael. 2007. A ScrumMaster’s checklist, August 13. Michael James’ blog on Danube’s website.

Jeffries, Ron. 2004a. Big visible charts. XP, October 20.

Jeffries, Ron. 2004b. Extreme programming adventures in C#. Microsoft Press.

Johnston, Andrew. 2009. The role of the agile architect, June 20. Content from Agile Architect website.

Jones, Do-While. 1990. The breakfast food cooker.

Kaplan, Robert S., and David P. Norton. 1992. The balanced scorecard: Measures that drive performance. Harvard Business Review, January-February, 71–79.

Karten, Naomi. 1994. Managing expectations. Dorset House.

Katzenbach, Jon. R. 1997. Real change leaders: How you can create growth and high performance at your company. Three Rivers Press.

Katzenbach, Jon R., and Douglas K. Smith. 1993. The wisdom of teams: Creating the high performance organization. Collins Business.

Keith, Clinton. 2006. Agile methodology in game development: Year 3. Session presented at Game Developers Conference, San Jose.

Kelly, James, and Scott Nadler. 2007. Leading from below. MIT Sloan Management Review, March 3.

Kerievsky, Joshua. 2005. Industrial XP: Making XP work in large organizations. Cutter Consortium Agile Project Management Executive Report 6 (2).

Koskela, Lasse. 2007. Test driven: TDD and acceptance TDD for Java developers. Manning.

Kotter, John P. 1995. Leading change: Why transformation efforts fail. Harvard Business Review, March–April, 59–67.

———. 1996. Leading change. Harvard Business School Press.

Krebs, William, and Per Kroll, 2008. Using evaluation frameworks for quick reflections. Agile Journal, February 9.

Krug, Steve. 2005. Don’t make me think: A common sense approach to web usability. 2nd ed. New Riders Press.

LaFasto, Frank M. J., and Carl E. Larson. 2001. When teams work best: 6,000 team members and leaders tell what it takes to succeed. Sage Publications, Inc.

Larman, Craig, and Victor R. Basili. 2003. Iterative and incremental development: A brief history. IEEE Computer, June, 47–56.

Larman, Craig, and Bas Vodde. 2009. Scaling lean & agile development: Thinking and organizational tools for large-scale Scrum. Addison-Wesley Professional.

Larson, Carl E., and Frank M. J. LaFasto. 1989. Teamwork: What must go right/what can go wrong. SAGE Publications.

Lawrence, Paul R. 1969. How to deal with resistance to change. Harvard Business Review, January–February, 4–11.

Leffingwell, Dean. 2007. Scaling software agility: Best practices for large enterprises. Addison- Wesley Professional.

Liker, Jeffrey K. 2003. The Toyota way. McGraw-Hill.

Little, Todd. 2005. Context-adaptive agility: Managing complexity and uncertainty. IEEE Software, May–June, 28–35.

Luecke, Richard. 2003. Managing change and transition. Harvard Business School Press.

MacDonald, John D. 1968. The girl in the plain brown wrapper. Fawcett.

Machiavelli, Nicollò. 2005. The prince. trans. Peter Bondanella. Oxford University Press.

Mah, Michael. 2008. How agile projects measure up, and what this means to you. Cutter Consortium Agile Product & Project Management Executive Report 9 (9).

Mair, Steven. 2002. A balanced scorecard for a small software group. IEEE Software, November/December, 21–27.

Mangurian, Glenn, and Keith Lockhart. 2006. Responsibility junkie: Conductor Keith Lockhart on tradition and leadership. Harvard Business Review, October.

Mann, Chris, and Frank Maurer. 2005. A case study on the impact of Scrum on overtime and customer satisfaction. In Proceedings of the Agile Development Conference, 70–79. IEEE Computer Society.

Manns, Mary Lynn, and Linda Rising. 2004. Fearless change: Patterns for introducing new ideas. Addison-Wesley.

Marick, Brian. 2007. Everyday scripting with Ruby: For teams, testers, and you. Pragmatic Bookshelf.

Marsh, Stephen, and Stelios Pantazopoulos. 2008. Automated functional testing on the TransCanada Alberta gas accounting replacement project. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 239– 244. IEEE Computer Society.

Martin, Angela, Robert Biddle, and James Noble. 2004. The XP customer role in practice: Three studies. In Proceedings of the Agile Development Conference, 42–54. IEEE Computer Society.

Martin, Robert C. 2008. Clean code: A handbook of agile software craftsmanship. Prentice Hall.

McCarthy, Jim. 2004. Twenty-one rules of thumb for shipping great software on time. Posted as part of a David Gristwood blog entry.

McCarthy, Jim, and Michele McCarthy. 2006. Dynamics of software development. Microsoft Press.

McFarland, Keith R. 2008. Should you build strategy like you build software? MIT Sloan Management Review, Spring, 69–74.

McKinsey & Company. 2008. Creating organizational transformations: McKinsey global survey results. McKinsey Quarterly, August.

McMichael, Bill, and Marc Lombardi. 2007. ISO 9001 and agile development. In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 262–265. IEEE Computer Society.

Mediratta, Bharat. 2007. The Google way: Give engineers room. As told to Julie Bick. The New York Times, October 21.

Mello, Antonio S., and Martin E. Ruckes. 2006. Team composition. The Journal of Business 79 (3): 1019–1039.

Meszaros, Gerard. 2007. xUnit test patterns: Refactoring test code. Addison-Wesley.

Miller, Ade. 2008. Distributed agile development at Microsoft patterns & practices. Microsoft. Download from the publisher’s website.

Miller, Lynn. 2005. Case study of customer input for a successful product. In Proceedings of the Agile Development Conference, 225–234. IEEE Computer Society.

Mintzberg, Henry. 2009. Rebuilding companies as communities. Harvard Business Review, July–August, 140–143.

Moløkken-Østvold, Kjetil, and Magne Jørgensen, 2005. A comparison of software project overruns: Flexible versus sequential development methods. IEEE Transactions on Software Engineering, September, 754–766.

Moore, Pete. 2005. E=mc2: The great ideas that shaped our world. Friedman.

Moore, Richard, Kelly Reff, James Graham, and Brian Hackerson. 2007. In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 175–180. IEEE Computer Society.

Mugridge, Rick, and Ward Cunningham. 2005. Fit for developing software: Framework for integrated tests. Prentice Hall.

Nicholson, Nigel. 2003. How to motivate your problem people. Harvard Business Review, January, 56–65.

Nickols, Fred. 1997. Don’t redesign your company’s performance appraisal system, scrap it! Corporate University Review, May–June.

Nielsen, Jakob. 2008. Agile development projects and usability. Alertbox, the author’s online column, November 17.

Nonaka, Ikujiro, and Hirotaka Takeuchi. 1995. The knowledge-creating company: How Japanese companies create the dynamics of innovation. Oxford University Press.

Ohno, Taiichi. 1982. Workplace management. trans. Jon Miller. Gemba Press. Quoted in Poppendieck 2007.

Olson, Edwin E., and Glenda H. Eoyang. 2001. Facilitating organization change: Lessons from complexity science. Pfeiffer.

Paulk, Mark. 2001. Extreme programming from a CMM perspective. IEEE Software, November, 19–26.

Pichler, Roman. Forthcoming. Agile product management with Scrum: Creating products that customers love. Addison-Wesley Professional.

Poppendieck, Mary, and Tom Poppendieck. 2006. Implementing lean software development: From concept to cash. Addison-Wesley Professional.

Poppendieck, Mary. 2007. E-mail to Lean Development mailing list, October 6. .

Porter, Joshua. 2006. The freedom of fast iterations: How Netflix designs a winning web site. User Interface Engineering, November 14. .

Putnam, Doug. Team size can be the key to a successful project. An article in QSM’s Process Improvement Series.

Ramasubbu, Narayan, and Rajesh Krishna Balan. 2007. Globally distributed software development project performance: An empirical analysis. In Proceedings of the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, 125–134. ACM.

Ramingwong, Sakgasit, and A. S. M. Sajeev. 2007. Offshore outsourcing: The risk of keeping mum. Communications of the ACM, August, 101–3.

Rayhan, Syed H., and Nimat Haque. 2008. Incremental adoption of Scrum for successful delivery of an IT project in a remote setup. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 351–355. IEEE Computer Society.

Reale, Richard C. 2005. Making change stick: Twelve principles for transforming organizations. Positive Impact Associates, Inc.

Rico, David F. 2008. What is the ROI of agile vs. traditional methods? An analysis of extreme programming, test-driven development, pair programming, and Scrum (using real options). A downloadable spreadsheet from David Rico’s personal website.

Robarts, Jane M. 2008. Practical considerations for distributed agile projects. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 327–332. IEEE Computer Society.

Robbins, Stephen P. 2005. Essentials of organizational behavior. Prentice Hall.

Rossi, Ernest Lawrence. 2002. The 20-minute ultradian healing response: An interview with Ernest Lawrence Rossi. Posted in the Interviews section of the author’s personal website, June 11.

Sanchez, Julio Cesar, Laurie Williams, and E. Michael Maximilien. 2007. On the sustained use of a test-driven development practice at IBM. 2007. In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 5–14. IEEE Computer Society

Schatz, Bob, and Ibrahim Abdelshafi. 2005. Primavera gets agile: A successful transition to agile development. IEEE Software, May/June, 36–42.

Schatz, Bob, and Ibrahim Abdelshafi. 2006. The agile marathon. In Proceedings of the Agile 2006 conference, ed. Joseph Chao, Mike Cohn, Frank Maurer, Helen

Sharp, and James Shore, 139–146. IEEE Computer Society.

Schubring, Lori. 2006. Through the looking glass: Our long day’s journey into agile. Agile Development, Spring, 26–28.

Schwaber, Ken. 2004. Agile project management with Scrum. Microsoft Press.

———. 2006. The canary in the coal mine. Recorded video of session at Agile 2006 Conference, 1 hour, 9 min., 14 sec.; embedded on InfoQ website, November 13.

———. 2007. The enterprise and Scrum. Microsoft Press.

———. 2009. Scrum guide, March. Posted as a downloadable PDF resource on the Scrum Alliance website.

Schwaber, Ken, and Mike Beedle. 2001. Agile software development with Scrum. Prentice-Hall.

Schwartz, Tony, and Catherine McCarthy. 2007. Manage your energy, not your time. Harvard Business Review, October, 63–73.

Seffernick, Thomas R. 2007. Enabling agile in a large organization: Our journey down the yellow brick road. In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 200–206. IEEE Computer Society.

Shaw, D. M. 1960. Size of share in task and motivation in work groups. Sociometry 23: 203–208.

Sliger, Michele. 2006. Bridging the gap: Agile projects in the waterfall enterprise. Better Software, July/August, 26–31.

Sliger, Michele, and Stacia Broderick. 2008. The software project manager’s bridge to agility. Addison-Wesley Professional.

Sosa, Manuel E., Steven D. Eppinger, and Craig M. Rowles. 2007. Are your engineers talking to one another when they should? Harvard Business Review, January, 133–142.

Spann, David. 2006. Agile manager behaviors: What to look for and develop. Cutter Consortium Executive Report, September.

Stangor, Charles. 2004. Social groups in action and interaction. Psychology Press.

Steiner, I. D. 1972. Group process and productivity. Academic Press Inc.

Striebeck, Mark. 2006. Ssh! We are adding a process…. In Proceedings of the Agile 2006 conference, ed. Joseph Chao, Mike Cohn, Frank Maurer, Helen Sharp, and James Shore, 185–193. IEEE Computer Society.

———. 2007. Agile adoption at Google: Potential and challenges of a true bottom-up organization. Session presented at Agile 2007 conference, Washington, DC.

Subramaniam, Venkat, and Andy Hunt. 2006. Practices of an agile developer: Working in the real world. Pragmatic Bookshelf.

Summers, Mark. 2008. Insights into an agile adventure with offshore partners. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 333–339. IEEE Computer Society.

Sutherland, Jeff, Carsten Ruseng Jakobsen, and Kent Johnson. 2007. Scrum and CMMI Level 5: The Magic Potion for Code Warriors In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 272–278. IEEE Computer Society.

Sutherland, Jeff, Guido Schoonheim, Eelco Rustenburg, and Mauritz Rijk. 2008. Fully distributed Scrum: The secret sauce for hyperproductive offshore development teams. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 339–344. IEEE Computer Society.

Sutherland, Jeff, Anton Viktorov, and Jack Blount. 2006. Adaptive engineering of large software projects with distributed/outsourced teams. In Proceedings of the Sixth International Conference on Complex Systems, ed. Ali Minai, Dan Braha, and Yaneer Bar-Yam. New England Complex Systems Institute.

Sutherland, Jeff, Anton Viktorov, Jack Blount, and Nikolai Puntikov. 2007a. Distributed Scrum: Agile project management with outsourced development teams. In Proceedings of the 40th Annual Hawaii International Conference on System Sciences, 274a. IEEE Computer Society.

Sy, Desirée. 2007. Adapting usability investigations for agile user-centered design. Journal of Usability Studies 2 (3): 112–132.

Tabaka, Jean. 2006. Collaboration explained: Facilitation skills for software project leaders. Addison-Wesley Professional.

———. 2007. Twelve ways agile adoptions fail. Better Software, November, 7.

Takeuchi, Hirotaka, and Ikujiro Nonaka. 1986. The new new product development game. Harvard Business Review, January, 137–146.

Tengshe, Ash, and Scott Noble. 2007. Establishing the agile PMO: Managing variability across projects and portfolios. In Proceedings of the Agile 2007 Conference, ed. Jutta Eckstein, Frank Maurer, Rachel Davies, Grigori Melnik, and Gary Pollice, 188–193. IEEE Computer Society.

Thaler, Richard H., and Cass R. Sunstein. 2009. Nudge: Improving decisions about health,
wealth, and happiness.
Updated ed. Penguin.

Therrien, Elaine. 2008. Overcoming the challenges of building a distributed agile organization. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 368–372. IEEE Computer Society.

Thomas, Dave. 2005. Agile programming: Design to accommodate change. IEEE Software, May/June, 14–16.

Toffler, Alvin. 1970. Future shock. Random House.

Tubbs, Stewart L. 2004. A systems approach to small group interaction. 8th ed. McGraw-Hill.

Turner, Richard, and Apurva Jain. 2002. Agile meets CMMI: Culture clash or common cause? In Extreme Programming and Agile Methods: XP/Agile Universe 2002, ed. D. Wells and L. A. Williams, 153–165. Springer.

Unson, J. F. 2008. E-mail to Scrum Development mailing list, May 26.

Vax, Michael, and Stephen Michaud. 2008. Distributed agile: Growing a practice together. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 310–314. IEEE Computer Society.

Venners, Bill. 2003. Tracer bullets and prototypes: A conversation with Andy Hunt and  Dave Thomas, part VIII. Artima Developer, April 21..

VersionOne. 2008. The state of agile development: Third annual survey. Posted as a downloadable PDF in the Library of White Papers on the VersionOne website.

Wake, William C. 2003. Refactoring workbook. Addison-Wesley Professional.

Ward, Allen C. 2007. Lean product and process development. Lean Enterprise Institute.

Wenger, Etienne, Richard McDermott, and William M. Snyder. 2002. Cultivating communities of practice. Harvard Business School Press.

Williams, Laurie, Lucas Layman, and William Krebs. 2004. Extreme programming evaluation framework for object-oriented languages, version 1.4. North Carolina State University Department of Computer Science, TR-2004-18.

Williams, Laurie, Anuja Shukla, and Annie I. Anton. 2004. An initial exploration of the relationship between pair programming and Brooks’ law. In Proceedings of the Agile Development Conference, 11–20. IEEE Computer Society.

Williams, Wes, and Mike Stout. 2008. Colossal, scattered, and chaotic: Planning with a large distributed team. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 356–361. IEEE Computer Society.

Woodward, E. V., R. Bowers, V. Thio, K. Johnson, M. Srihari, and C. J. Bracht. Forthcoming. Agile methods for software practice transformation. IBM Journal of Research and Development 54 (2).

Wright, Graham. 2003. Achieving ISO 9001 certification for an XP company. In Extreme Programming and Agile Methods: XP/Agile Universe 2003, ed. F. Maurer and D. Wells, 43–50. Springer.

Yegge, Steve. 2006. Good agile, bad agile. Stevey’s Blog Rants, September 27.

Young, Cynick, and Hiroki Terashima. 2008. How did we adapt agile processes to our distributed development? Overcoming the challenges of building a distributed agile organization. In Proceedings of the Agile 2008 Conference, ed. Grigori Melnik, Philippe Kruchten, and Mary Poppendieck, 304–309. IEEE Computer Society.

Filed Under: Uncategorized

Leave a Reply