Chapter 11 • IT Project Management 431Bibliography
Brewer, Jeffrey L., and Kevin C. Dittman. 2010. Methods of IT
project management. Upper Saddle River, NJ: Prentice
Hall.
Brown, Carol V., and Iris Vessey. 2003. “Managing the next wave
of enterprise systems: Leveraging lessons from ERP.” MIS
Quarterly Executive2, 1 (March): 65–77.
Clark, Charles E., Nancy C. Cavanaugh, Carol V. Brown, and
V. Sambamurthy. 1997. “Building change-readiness capa-
bilities in the IS organization: Insights from the Bell
Atlantic experience.” MIS Quarterly 21 (December):
425–456.
Denis, Bob, Maureen Vavra, and John Dick. 2004. “Budgeting,”
inCIO Wisdom. Upper Saddle River, NJ: Pearson Prentice
Hall, Chapter 13.
Frame, J. Davidson. 1994. The new project management. San
Francisco, CA: Jossey-Bass.
Fuller, Mark A., Joseph S. Valacich, and Joey F. George. 2008.
Information systems project management: A process and
Team approach. Upper Saddle River, NJ: Prentice Hall.
Hamilton, Stewart. 2000. “Information and the management of
risk,” in Donald A. Marchand (ed.), Competing with
Information. England: John Wiley & Sons, Ltd., 195–207.
Kappelman, Leon A., Robert McKeeman, and Lixuan Zhang.
- “Early warning signs of IT project failure: The dominant
dozen.” Information Systems Management23, 4 (Fall): 31–36.
Keil, Mark, and Daniel Robey. 1999. “Turning around troubled
software projects: An exploratory study of the deescalation of
commitment to failing courses of action.” Journal of
Management Information Systems15 (Spring): 63–87.
Kostner, Jacyln. 1996. Virtual leadership—secrets from the round
table for the multi-site manager. New York: Warner Books, Inc.
Kotter, John P. 1995. “Leading change: Why transformation
efforts fail.” Harvard Business Review(March–April): 59–67.
Lapointe, Liette, and Suzanne Rivard. 2005. “A multilevel model
of resistance to information technology implementation.” MIS
Quarterly29, 3 (September): 461–491.
Lewin, Kurt. 1947. “Frontiers in group dynamics.” Human
Relations1: 5–41.
Lindstrom, Lowell, and Ron Jeffries. 2003. “Extreme program-
ming and agile software development methodologies,” in
Carol V. Brown and Heikki Topi (eds.), IS Management
Handbook, 8th ed. New York: Auerbach, Chapter 41.
Markus, M. Lynne. 1983. “Power, politics, and MIS implementa-
tion.” Communications of the ACM26 (June): 430–444.
Meredith, Jack R., and Samuel J. Mantel, Jr. 1989. Project man-
agement: A managerial approach, 2nd ed. New York: John
Wiley & Sons.
Mohtashami, Mojgan, Thomas Marlowe, Vassilka Kirova, and
Fadi P. Deek. 2006. “Risk management for collaborative soft-
ware development.” Information Systems Management23, 4
(Fall): 20–30.
Montealegre, Ramiro, and Mark Keil. 2000. “De-escalating
information technology projects: Lessons from the Denver
International Airport.” MIS Quarterly 24 (September):
417–447.
Nelson, R. Ryan. 2005. “Project retrospectives: Evaluating proj-
ect success, failure, and everything in between.” MIS
Quarterly Executive4, 3 (September): 361–372.
Nelson, R. Ryan. 2007. “IT project management: Infamous fail-
ures, classic mistakes, and best practices.” MIS Quarterly
Executive6, 2 (June): 67–78.
Nelson, R. Ryan, and Karen J. Jansen. 2009. “Mapping and man-
aging momentum in IT projects.” MIS Quarterly Executive8,
3 (September): 141–148.
Orlikowski, Wanda J., and J. Debra Hofman. 1997. “An improvisa-
tional model for change management: The case of groupware
technologies.” Sloan Management Review38 (Winter): 11–22.
Poria, Bharat C. 2004. “Strategic outsourcing,” in CIO Wisdom.
Upper Saddle River, NJ: Pearson Prentice Hall, Chapter 9.
Project Management Institute (PMI). 2004. A guide to the Project
Management Body of Knowledge(PMBOK Guide), 3rd ed.
Newton Square, PA: Project Management Institute.
Ranganathan, C., Poornima Krishnan, and Ron Glickman. 2007.
“Crafting and executing an offshore IT sourcing strategy:
Globshop’s experience.” Journal of Information Technology
22, 4 (December): 440–450.
Roberts, Betsy, Sirkka Jarvenpaa, and Cherie Baxley. 2003.
“Evolving at the speed of change: Mastering change readi-
ness.” MIS Quarterly Executive2, 2 (June): 58–73.
Roman, Daniel D. 1986. Managing projects: A systems
approach. New York: Elsevier.
Russell, Lou. 2000. “Managing the end for new beginnings: Post-
project review for year 2000.” Cutter IT Journal13 (July):
28–39.
Russell, Lou. 2007. 10 steps to successful project management.
Alexandria, VA: ASTD Press.
Ryan, Hugh W. 2003. “Managing development in the era of com-
plex systems,” in Carol V. Brown and Heikki Topi (eds.), IS
Management Handbook, 8th ed. New York: Auerbach,
Chapter 44.
Sauer, Chris, and Leslie Willcocks. 2007. “Unreasonable expec-
tations–NHS IT, Greek choruses and the games institutions
play around mega-programmes.” Journal of Information
Technology22, 3 (September): 195–201.
Schwalbe, Kathy. 2004. Information technology project manage-
ment, 3rd ed. Canada: Thomson Learning.
Standish Group. 2009. http://www.standishgroup.com, last accessed
June 26, 2010.
Vavra, Maureen, and Dean Lane. 2004. “Strategic planning,” in
CIO Wisdom. Upper Saddle River, NJ: Pearson Prentice Hall,
Chapter 11.
Wheatley, Margaret, and Myron Kellner-Rogers. 1996. A Simpler
Wa y. San Francisco, CA: Berrett-Koehler.
Willcocks, Leslie, and Catherine Griffiths. 2010. “The critical
role of middle management in outsourcing.” MIS Quarterly
Executive9, 3 (September): 177–193.