MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_01C963B1.9D6CBC40" This document is a Single File Web Page, also known as a Web Archive file. If you are seeing this message, your browser or editor doesn't support Web Archive files. Please download a browser that supports Web Archive, such as Microsoft Internet Explorer. ------=_NextPart_01C963B1.9D6CBC40 Content-Location: file:///C:/515CB117/ProjectManagementOverview.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii"
Project Management Overview
Excerpt from:
Lacity, M. (editor), (2008), Major Currents=
in
Information Systems: The Management of Information Systems, Volume 4 in the=
six
volume series (series editors: Willcocks, L., and Lee, A.), Sage,
By Mary Lacity
The ability to identify, prior=
itize,
gain approval, develop, and deliver IS-enabled business projects is a key IS
capability. For nearly =
40
years, IS leaders have struggled to deliver IS-enabled business projects to=
the
organization on time, on budget, and with the promised business functionali=
ty. Academics have long studied the ca=
uses
of IS project failures (Ginzberg, 1981; Lyytinen and Hirschheim, 1987; Keme=
rer,
1987; Sauer 1993). We have kn=
own
for a long time that IS project failures primarily result from poor managem=
ent
and not from poor technology. We have known for a long time that throwing
additional resources at a late project will not necessarily speed delivery
because of increased overhead (Brooks, 1975).
In Keil et al. (2003) "Why Software Projects Escalate: =
The
Importance of Project Management Constructs," the authors rigorous=
ly
test the factors associated with project escalation. The authors tested
multiple theories (self justification theory, prospect theory and agency
theory). The authors found th=
at monitoring/controlling,
project planning, and project specification constructs best predicted proje=
ct
outcomes based on responses from 579 IS auditors. Project size was also found to be =
an
important construct, but it was confounded with the other project management
constructs.
More recently, Nelson (2007)
examined 36 causes of failure among 99 projects. He identified 10 best practices to=
avoid
failure. His research is cons=
istent
with the findings from the widely cited Standish
Group Chaos Report (2003).&nbs=
p;
The Standish Group's research comprises 12 years of research on =
over
50,000 completed IS projects. In
general, the 12 years of data show an increased rate of IS project success.=
For example, in 1994, only 16 perc=
ent of
IS projects were delivered on time, on budget, and with promised functional=
ity
compared to 29 percent in 2004. As
expected, the percentage of project failures (cancelled projects or projects
finished but never used) decreased from 31 percent in 1994 to 18 percent in
2004. However, the percentage=
of
“challenged” projects has remained steady at about 53 percent.<=
span
style=3D'mso-spacerun:yes'> Challenged projects are IS project=
s that
are delivered over-budget, over-time or missing functionality.
Critical Success Factors. Many researchers have identified t=
he
critical factors associated with IS project success. Five of these critical succe=
ss
factors are discussed below.
1. User Involvement. Business users must be actively involved during all phases of the
project. Much research =
has
been done on the depth of user participation, the nature of user participat=
ion,
and degree of influence users had on project outcome (Lynch, T., and Gregor,
2004; Hirschheim, 1985; Hirschheim and Klein, 1994; Mumford, 1981). For example, a study of 612 findin=
gs on
published research from 1980 to 2004 on the determinants of IS success found
that user participation positively affects three measures of IS success: Us=
er
satisfaction, Perceived Usefulness, and System Quality (Sabherwal et al. 20=
06).
2. Executive management support. Executive management support of the=
IS
project is vital to success.
Executive managers play many roles, the most important of which are =
to
serve as project sponsors and project champions (Beath, 1996; Edwards, 1996=
). Project Sponsors have “the funds and authority to accomplish =
their
goals” (Beath, 1996, p. 355).&nb=
sp;
Project Champions are managers who “actively and vigorously promote their personal vision for using IT,
pushing the project over or around approval and implementation hurdles. They
often risk their reputations in order to ensure the innovation’s
success” (Beath, 1996, p. 355). The Sabherwal et al. (2006) study
also found that top management support positively affected three measures o=
f IS
success (1) user satisfaction, (2) perceived usefulness, and (3) system use=
.
3.
Optimizing scope. One of the biggest threats to delivering IS
projects on time and on budget is the phenomenon known as “scope
creep.” Scope creep mea=
ns
that the initial project scope has increased to include new products, servi=
ces,
or features. Scope creep occu=
rs
because the initial project scope may have been under-specified, users
participating on the project may request more features, or changes to the
business or technology during project development might trigger more requir=
ements.
Four of the best studies on project escalation have been done by Keil
(1995), Keil and Montealegre (2000), and Keil et al. (2000a; 2000b). These authors examined the project,
psychological, social, and organizational factors that lead to project esca=
lation. Their work provides a deep underst=
anding
of IS projects beyond the critical success factors. For example, some senior managers
provide too much executive mana=
gement
support by continuing to fund and protect projects with outrageous scope cr=
eep.
Another interesting insight comes from the 2002 Standish Group report.
The report found that 45 percent of IS features are never used! The delivery of so many unused fea=
tures
is troubling, particularly in light of the “80/20 rule” which
states that 80 percent of requirements cost 20 percent of total costs and t=
he
last 20 percent of requirements can cost 80 percent of total costs. Thus IS managers should freeze the=
scope
of projects rather than seek to deliver 100% of requested functions. Brown and Vessey (2003) call=
this
a “satisficing mindset.” By optimizing scope, projects should be
delivered at cost.
4. Divide a large project into several smaller projects. =
For over 25 years, IT researchers h=
ave
recognized the relationship between project size, risk, and outcome (Gopal =
et
al. 2003; McFarlan 1981; Wallace et al. 2004). In general, prior research has fou=
nd
that larger-sized projects are riskier and have lower success rates than
smaller-sized projects (Jones 1994).
For example, Carroll (2005) found that small projects (less than six
months) had a success rate of 50 percent, medium-sized projects (six to nine
months) had a 40 percent success rate, and none of the projects in the samp=
le
(n =3D 22) over nine months were successful.
Aladwani (2002) in a study of 42 IT projects found that project size
negatively affects project planning, which negatively impacts project
success. Practitioners and
researchers suggest transforming a large project into smaller projects thro=
ugh
agile processes, prototyping, or pilot testing to reduce risk and increase
success (Naumann and Jenkins, 1982; Janson and Smith, 1985; Jones 1994;
Standish Group International 2003; Willcocks et al. 1997).
5. Project management expertise. Havi=
ng
experienced project managers is a critical IS capability to ensure project
success. A recent study spons=
ored
by the Society of Information Management Advocacy program found that project
management skills were the most vital skills to develop and keep in-house
(Zwieg et al. 2006). Increasi=
ngly,
organizations are building project management expertise through project
management certification. The=
most
popular certification is the PMP (Project Management Professional) from the
Project Management Institute (PMI)[1].
Program
and Portfolio Management. =
In addition to managing individual IS projects, IS and bus=
iness
leaders must also manage across mul=
tiple IS
projects. The ability to
prioritize, approve, schedule, and source multiple IS projects is called
program management. As far ba=
ck as
McFarlan (1981), academics have been studying the best practices associated
with program management.
Organizations frequently have a Program Management Office (PMO) to manage t=
he
set of ongoing projects. In
addition, IS leaders must integrate the completed projects into the existing
portfolio of IS applications.
Portfolio management is the management of the entire portfolio of
existing applications, applications currently under development, and applic=
ations
that need to be developed in the future.&n=
bsp;
One of the best research articles on this topic is by Weill and Aral
(2006). The authors examined =
the
portfolios of 147 organizations over a five year period. The authors found that certain mix=
es of
applications (infrastructure, transactional, informational, and strategic) =
are
associated with different business outcomes in terms of profitability, mark=
et
value, innovation, and lower cost of goods sold.
Change Management. = span> Whereas project management is concerned about managing the design, development, and delivery of an IS project, change management is about managing the people affected by change caused by the new IS project. Preparing the organization for the cha= nge is accomplished mostly through training and incentives. Hatzakis et al. (2005) offer an excellent framework of change management based on social capital theory. The authors develop a comprehensive framework of change management based on social capital theory.= Based on a survey and interviews within an organization, the authors found that social relationships between business and IS colleagues must be fostered not only during a systems development project, but before, during,= and after. Roberts et al. (2003) provides an excellent example of best practices for change management.
References to the Entire Volume, Including Project Management:
Agarwal, R., and Prasad, J. (1=
997)
“The Role of Innovation Characteristics and Perceived Voluntariness in
the Acceptance of Information Technologies,” Decision Sciences, Vol. 28, 3,=
pp. 557-582.
Agarwal, R., and Prasad, J. (1=
998)
“The Antecedents and Consequents of User Perceptions in Information
Technology Adoption,” Decision
Support Systems, Vol. 22,
1, pp. 15-29.
Agarwal, R., and Prasad, J. (2=
000)
“A Field Study of the Adoption of Software Process Innovations by
Information Systems Professionals,” IEEE
Transactions on Engineering Management, Vol. 47, 3, pp. 295-308.
Ajzen,
Aladwani, A. (2002) “IT
Project Uncertainty, Planning, and Success,” Information Technology & People, Vol., 15, 3, pp. 210-237.
Alavi, M., and Leidner, D.
(2001) "Knowledge Manage=
ment
and Knowledge Management Systems: Conceptual Foundations and Research
Issues," MIS Quarterly, Vo=
l. 25,
1, March p. 107-137.
Ang, S., and Cummings, L. (1997) "Strategic Response to Institutio=
nal
Influences on IS Outsourcing," Organization
Science, Vol. 8, 3, May-June
pp. 235-256.
Ang, S., and Straub, D. (1998)
“Production and Transaction Economies and Information Systems
Outsourcing–A Study of the
Ang, S., and Slaughter, S. (20=
01)
“Work Outcomes and Job Design for Contract Versus Permanent Informati=
on
Systems Professionals on Software Development Teams,” MIS Quarterly, Vol. 25, 3,
September pp. 321-350.
Anonymous (2007) The State of the CIO Survey: 2007 =
by CIO Magazine.
Applegate, L., and
Applegate, L., and Montealegre=
, R.
(1991) “Eastman Kodak Organization: Managing IS Through Strategic
Alliances,”
Aubert, B., Dussault, S., Patr=
y, M.,
and Rivard, S. (1999) “Managing Risk in IT Outsourcing,” Proceedings of the 32nd Ann=
ual
Bandura, A. (1986) Social foundations of thought and acti=
on: A social
cognitive theory, Englewood Prentice Hall, Cliffs, NJ.
Barney, J. (1989) "Asset =
Stock
Accumulation and Sustainability of Competitive Advantage: A Comment," =
Management Science, Vol. 35, 12,
December pp. 1511-1514.
Barney, J. (1999) “How a
Firm’s Capabilities Affect Boundary Decisions,” Sloan Management Review, Vol. 40, =
3,
Spring pp. 137-145.
Beath, C. (1996) “The Pr=
oject
Champion,” in Information
Management: The Organizational Dimension, Earl, M. (ed.), University
Beath, C., and Walker, G. (199=
8)
“Outsourcing of Application Software: A Knowledge Management
Perspective,” Proceedings of =
the 31st
Annual International Conference on Systems Sciences,
Becerra-Fernandez,
Blau, P. (1964) Exchange and Power in Social Life, Wiley,
Brooks, F., (1975) The Mythical Man Month: Essays in Soft=
ware
Engineering, Addison-Wesley,
Brown, C. (1997) “Examin=
ing
the Emergence of Hybrid IS Governance Solutions,” Information Systems Research, Vol. 8, 1, March pp. 69-95.
Brown, C., and Vessey, I. (200=
3)
"Managing the Next Wave of
Brynjolfsson,
E., and Hilt, L. (1996) “Productivity, Business Profitability and
Consumer Surplus: Three Differenent Measures of IT Value,” MIS Quarterly, June, pp. 121-142.
Carroll, J. (2005) “The =
John
Carroll Research Survey Results,” Project
Management Institute, available on: http://www.pmi.org/Prod2/groups/pub=
lic/documents/info/pp_carroll.pdf.
Cash, J., and Konsynski, B. (1=
995)
“IS Redraws Competitive Boundaries,” Harvard Business Review, Vol. 63, 2, pp. 134-142.
Chau, P. (1996) “An Empi=
rical
Assessment of a Modified Technology Acceptance Model,” Journal of Management Information Syst=
ems,
Vol. 13, 2, pp. 185-204.
Chaudhury, A.,
Cheon, M., Grover, V., and Ten=
g, J.
(1995) “Theoretical Perspectives on the Outsourcing of Information Systems,” Journal of Information Technology,=
Vol.
10, 19 pp. 209-210.
Choudhury, V., and Sabherwal, =
R.
(2003) “Portfolios of Control in Outsourced Software Development
Projects,” Information Systems
Research, Vol.14, 3,
September pp. 291-314.
Clemons, E., and Row, M. (1988)
“McKesson Drug Company: A Case Study of Economost—A Strategic
Information System,” Journal =
of Management
Information Systems, Vol. 5, 1,
pp. 36-50.
Clemons, E., and Row, M. (1991)
“Sustaining IT Advantage: The Role of Structural Differences,” =
MIS Quarterly, Vol. 15, 3, pp. 275-292.
Compeau, D., and Higgins, C. (=
1995)
“Computer Self-Efficacy: Development of a Measure and Initial
Test,” MIS Quarterly, Vol=
. 19,
2, pp. 189-211.
Compeau, D., Higgins, C., and =
Huff,
S. (1999) “Social Cognitive Theory and Individual Reactions to Comput=
er
Technology: A Longitudinal Study,” MIS
Quarterly, Vol. 23, 2,
Copeland, D., and McKenney, J.
(1988) “Airline Reservation Systems, Lessons from History,” MIS Quarterly, Vol. 12, 3, pp. 353-370.
Cullen, S., Seddon, P., and
Willcocks, L. (2005) “Managing Outsourcing: The Life Cycle
Imperative,” MIS Quarterly
Executive, March Vol. 4, 1, pp. 229-246.
Davis, F.D. (1993) “User
Acceptance of Information Technology: System Characteristics, User Percepti=
ons,
and Behavioral Impacts,” Jour=
nal of
Man-Machine Studies, Vol. 38, 3,
pp. 475-487.
Davis, F.D., Bagozzi, P., and
Warshaw, P. (1989) “User Acceptance of Computer Technology: A Compari=
son
of Two Models,” Management Sc=
ience,
Vol 35, 8, pp. 982-1001.
Dearden,
J. (1987) “The Withering Away of the IS Organization,” Sloan Management Review, Summer
Dehning, B., and Stratopoulos,=
T.
(2003) “Determinants of Sustainable Competitive Advantage Due to
IT-enabled Strategy,” Journal=
of
Strategic Information Systems, Vol. 12, 1, pp. 7-28.
Devaraj, S., and Kohli, R. (20=
02) The IT Payoff: Measuring the Business =
Value
of IT Investments, Financial Times Prentice Hall,
Dibbern, J., Goles, T., Hirsch=
heim,
R., and Bandula J.(2004) "Information Systems Outsourcing: A Survey and
Analysis of the Literature," D=
atabase
for Advances in Information Systems,
Vol. 34, 4, Fall pp. 6-102.
DiMaggio, P. and Powell, W. (1=
983)
“The Iron Cage Revisited: Industrial Isomorphism and Collective
Rationality in Organizational Fields,” American Sociological Review, Vol. 48, 2, pp. 147-160.
Dos
Dos
Dretske, F. (1981) Knowledge and the Flow of Information<=
/i>,
MIT Press,
Earl, M. (1996) “The Chi=
ef
Information Officer: Past, Present, and Future,” in Information Management: The Organizational Dimension, Earl, M.
(ed.),
Earl, M. (2001) "Knowledge
Management Strategies: Toward a Taxonomy," Journal
of Management Information Systems, Vol. 18, 1, Summer pp. 215-233.
Earl, M., and Feeny, D. (1994)
“Is your CIO Adding Value?” Sloan
Management Review, Vol. 35, 3, Spring&=
nbsp;
pp. 11-20.
Edwards, B. (1996) “The
Project Sponsor,” in Informat=
ion
Management: The Organizational Dimension, Earl, M. (editor),
Eisenhardt, K. (1989) "Ag=
ency
Theory: An Assessment and Review," The
Ekeh, P. (1974) Social Exchange Theory: The Two Traditions,
Enns=
, H.,
Huff, S., and Golden, B. (2003) “CIO influence behaviors: The impact =
of
technical background,” Information & Management=
span>, Vol.=
40,
5, May pp. 467.
Feeny, D. and Willcocks, L. (1=
998)
“Core IS Capabilities for exploiting Information Technology,” Sloan Management Review, Vol. 39, 3, Spring, pp. 9-21.
Feeny, D., and Ives, B. (1990)
“In Search of Sustainability: Reaping Long-term Advantage from Invest=
ments
in Information Technology,” J=
ournal
of MIS, Vol. 7, 1, pp. 27=
-46.
Feeny, D., Edwards, B., and Si=
mpson,
K. (1992) “Understanding the CEO/CIO Relationship,” MIS Quarterly, Vol. 16, 4, Decembe=
r pp. 435-446.
Fichman, R. (1992)
“Information Technology Diffusion: A Review of Empirical Research, in=
Thirteenth International Conference on
Information Systems, Dallas, TX,
pp. 195-206.
Fichman, R. (2004) “Going
Beyond the Dominant Paradigm for Information Technology Innovation Research:
Emerging Concepts and Methods,” Journal
of the AIS, Vol. 5, 8, pp.
314-355.
Fichman, R., and Kemerer, C. (=
1999)
“The Illusory Diffusion of Innovation: An Examination of Assimilation
Gaps,” Information Systems
Research, Vol. 10, 3, pp.
255-275.
Field,
T. (2002) “The State of the CIO--Building Executive Relationships,” CIO Magazine, March 12, available =
on
www.cio.com/article/30891/THE_=
STATE_OF_THE_CIO_Building_Executive_Relationsh=
ips.
Fishbein, M., and Ajzen, I. (1=
975) Belief, Attitude, Intention, and Behav=
ior,
Ginzberg, M. (1981) “Ear=
ly
Diagnosis of MIS Implementation Failure: Promising Results and Unanswered
Questions,” Management Scienc=
e,
Vol. 27, 4, April pp. 459-478=
.
Gopal, A., Sivaramakrishnan, K=
.,
Krishnan, M., and Mukhopadhyay, T. (2003) "Contracts in Offshore Softw=
are
Development: An Empirical Analysis," Management
Science, Vol. 49, 12, December
pp. 1671-1683.
Grover, V. (1993) “An
Empirically Derived Model for the Adoption of Customer-based
Interorganizational Systems,” Decision
Sciences, Vol. 24, 3, pp.
603-640.
Grover, V. , Cheon, M., and Te=
ng, J.
(1996) “The Effect of S=
ervice
Quality and Partnership on the Outsourcing of Information Systems
Functions," Journal of Managem=
ent
Information Systems, Vol. 12, 4, Spring pp. 89-119.
Grover, V., and
Grover, V., and
Grover, V., and Teng, J. (1992)
“An Examination of DBMS Adoption and Success in American
Organizations,” Information &=
amp;
Management, Vol. 23, 5, p=
p.
239-248.
Grover, V., Fiedler, K., and T=
eng,
J. (1997) “Empirical Evidence on Swanson's Tri-Core Model of Informat=
ion
Systems Innovation,” Informat=
ion
Systems Research Vol. 8, 3, pp.
273-287.
Hall, J., and Liedtka, S. (200=
5) "Financial Performance, CEO
Compensation, and Large-Scale Information Technology Outsourcing
Decisions," Journal of Managem=
ent
Information Systems, Vol, 22, 1, Summer pp. 193–222.
Hirs=
chheim,
R. (1985) “User Experience with and Assessment of Participative Syste=
ms
Design,” MIS Quarterly, V=
ol. 9,
4, pp. 295-304.
Hirs=
chheim,
R., and Klein, H. (1994) “Realizing Emancipatory Principles in
Information Systems Development: The Case for ETHICS,” MIS
Quarterly, Vo=
l. 18,
1, March pp. 83-109.
Homans, G. (1961) Social Behavior: It’s Elementary
Forms, Harcourt Brace Javanovich,
Hu, Q., Saunders, C., and Gebe=
lt, M.
(1997) “Research Report: Diffusion of Information Systems Outsourcing=
: A Reevaluation
of Influence Sources,” Inform=
ation
Systems Research, Vol. 8, 3, pp. 288-301.
Huber, R. (1993) “How
Continental Bank Outsourced its Crown Jewels,” Harvard Business Review, Vol. 71, 1, pp. 121-129.
Huff, S., Maher, P., and Munro
(2006) “Information Technology and Board of Directors: Is There an IT
Attention Deficit?”MIS Quarte=
rly
Executive, June Vol. 5, 2=
, pp.
55-68.
Iacovou, C., Benbasat,
Igbaria, M.(1993) “User
Acceptance and Microcomputer Technology: An Empirical Test,” Omega Vol. 21, 1, pp. 73-90.
Ives, B., and Olson, M. (1981)
“Manager or Technician? The Nature of the Information Systems
Manager’s Job,” MIS Qua=
rterly,
Vol. 5, 4, December pp. 49-63=
.
Janson, M., and Smith, D. (198=
5)
“Prototyping for Systems Development: A Critical Appraisal,” MIS Quarterly, Vol. 9, 4, pp. 305-316.
Jarvenpaa, S., and Ives, B. (1=
991)
“Executive Involvement in IT Management,” MIS Quarterly, Vol. 15,
pp. 205-224.
Jesitus, J. (1997) “Brok=
en
Promises? FoxMeyer’s Project was a Disaster. Was the company too
aggressive or was it Misled?” Industry
Week, November 3, pp. 31-37.
Jones, C. (1994) Assessment and Control of Software Ris=
ks,
Prentice-Hall,
Kaarst-Brown, M. (2005)
“Understanding An Organization’s View of the CIO: The Role of
Assumptions About IT,” MIS
Quarterly Executive, Vol. 4, 2, June&n=
bsp;
pp. 287-301
Kaplan, R., and Norton, D. (19=
92)
“The Balanced Scorecard—Measures that Drive Performance,”=
Harvard Business Review,
January/February pp. 71-79.
Karahanna,
E., and Watson, R. (2006) “Information Systems Leadership,” IEEE Transactions on Engineering Management, Vol. 53, 2, May pg. 171.
Karahanna, E., Straub, D.W., a=
nd
Chervany, N.L. (1999) “Information Technology Adoption across Time: A
Cross-Sectional Comparison of Pre-Adoption and Post-Adoption Beliefs,”=
; MIS Quarterly, Vol. 23, 2, pp. 183-213.
Keil M (1995) "Pulling the
plug: Software project management and the problem of project escalation,&qu=
ot; MIS Quarterly,” Vol. 19, 4,
December pp. 421-447.
Keil, M., and Montealegre, R. =
(2000)
"Cutting Your Losses: Extricating Your Organization When A Big Project
Goes Awry," Sloan Management R=
eview,
Vol 41, 3, Spring pp. 55-68.<=
span
style=3D'mso-tab-count:1'>
(a) Keil, M., Mann, J., and Ra=
i, A.
(2000) “Why Software Projects Escalate: An Empirical Analysis and Tes=
t of
Four Theoretical Models,” MIS
Quarterly, Vol. 24, 4, December,
pp. 631-664.
(b) Keil, M., Tan, B., Wei, K., Saarinen, T., Tuunainen, V., and Wassenaar,=
A.
(2000) “A Cross-Cultural St=
udy on
Escalation of Commitment Behavior in Software Projects,”
MIS Quarterly, Vol. 24, 2, June, pp. 299-325.
Kemerer, C. (1987) “An
Empirical Validation of Software Cost Estimation Models,” Communications of the ACM, Vol. 30=
, 5,
May pp. 416-429.
Kern, T., Willcocks, L., and V=
an
Heck, E. (2002) “The Winners Curse in IT Outsourcing: Strategies for
Avoiding Relational Trauma,”
Kettinger, W., Grover, V., Guh=
a, S.,
and Seagers, A. (1994) “Strategic Information Systems Revisited: A St=
udy
in Sustainability and Performance,” MIS
Quarterly, Vol. 18, 1, pp.
31-58.
Kwon, T., and Zmud, R. (1987)
“Unifying the Fragmented Models of Information Systems
Implementation,” in Critical =
Issues
in Information Systems Research, Boland, R. and Hirschheim, R. (eds.),
Lacity, M. and Rottman, J. (20=
08) Offshore Outsourcing of IT Work, <=
st1:place
w:st=3D"on">
Lacity, M., and Hirschheim, R.
(1993) Information Systems Outsourc=
ing:
Myths, Metaphors and Realities, Wiley,
Lacity, M., and Willcocks, L. =
(1996)
"Interpreting Information Technology Sourcing Decisions from a Transac=
tion
Cost Perspective: Findings and Critique," Accounting, Management, and Information Technologies, Vol. 5, N=
o.
3/4, pp. 203-244.
Lacity, M., Willcocks, L., and
Feeny, D. (1995) "Information Technology Outsourcing: Maximizing
Flexibility and Control, Harvard Bu=
siness
Review, May-June, pp. 84-93.
Lacity, M., Willcocks, L., and
Feeny, D. (1996) "The Value of Selective IT Sourcing," Sloan Management Review, Spring
Lai, V., and Guynes, J. (1994)
“A Model of ISDN (Integrated Services Digital Network) Adoption in
Lee, J., Miranda, S., and Kim,=
Y.
(2004) "IT Outsourcing Strategies: Universalistic, Contingency, and
Configurational Explanations of Success," Information Systems Research, Vol. 15, 2, June pp. 110-131.
Leidner, D., and Mackay, J. (2=
007)
“How Incoming CIOs Transition into their New Jobs,” MIS Quarterly Executive, March Vol. 6, 1, pp. 17-28.
Leidner, D., Beatty, R., Macka=
y, J.
(2003) “How CIO’s Manage IT during Economic Decline: Surviving =
and
Thriving Amid Uncertainty,” M=
IS
Quarterly Executive, March 2003, Vol. 2, 1, March pp. 1-14.
Levina, N., and Ross, J.(2003)
“From the Vendor’s Perspective: Exploring the Value Proposition=
in
Information Technology Outsourcing,” MIS
Quarterly, Vol. 27, 3, September
pp. 331-364.
Levinson, M. (2004) “CIO=
and
CEO: How to Work with Your Boss,” CIO
Magazine, Oct 1.
Loh, L., and Venkatraman, N. (=
1992)
“Diffusion of Information Technology Outsourcing: Influence Sources a=
nd
the Kodak Effect,” Information
Systems Research, Vol. 3, 4,
pp. 334-358.
Loh, L., and Venkatraman, N. (=
1992)
“Determinants of IT Outsourcing: A Cross-Sectional Analysis,” Journal of Management Information Syst=
ems,
Vol, 9, 1, pp. 7-24.
Luftman, J., Kempaiah (2006) R=
., and
Nash, E., "Key Issues for IS Executives," MIS Quarterly Executive, Vol. 5, 2, pp. 81-99.
Lynch, T., and Gregor, S. (200=
4)
“User participation in decision support systems development: Influenc=
ing
system outcomes,” European Jo=
urnal
of Information Systems, V=
ol 13
4; p. 286
Lyytinen, K., and Hirschheim, =
R.
(1987) “Information Systems Failures: A Survey and Classification of =
the
Empirical Literature,” in Oxf=
ord
Surveys in Information Technology, Zorkoczy, P. (ed), Oxford University
Press, Oxford, pp. 257-309.
Markus, L. (2001) "Toward= a Theory of Knowledge Reuse: Types of Knowledge Reuse Situations and Factors = in Reuse Success," Journal of Management Information Syst= ems, Vol. 18, 1, Summer pp.57-94.<= o:p>
McFarlan, F.W. (1981)
“Portfolio Approach to Information Systems,” Harvard Business Review, Vol. 59, 5, September-October, pp. 142-150.
McFarlan, F.W. (1984)
“Information Technology Changes the Way you Compete,” Harvard Business Review, Vol. 63,
3, pp. 98-104.
Melville, N., Kraemer, K.,
Gurbaxani, V. (2004) "Information Technology and Organizational
Performance: An Integrative Model of IT Business Value," MIS Quarterly, Vol. 28, 2, June
Miles, R., Snow, C., Meyer, A.,
Coleman, H. (1978) “Organizational Strategy, Structure, and
Process,” The
Miles, R., and Snow, C. (1978)=
Organizational strategy, structure, and
process,
Mizruchi, M., and Fein, L. (19=
99)
“The Social Construction of Organizational Knowledge: A Study of the =
Uses
of Coercive, Mimetic, and Normative Isomorphism,” Administrative Science Quarterly, Vol. 44, 4, pp. 653-683.
Morris, P. (2000) “Resea=
rching
the Unanswered Questions of Project Management,” INDECO Management So=
lutions
Report.
Mumford, E. (1981)
“Participative Systems Design: Structure and Methods,” Systems, Objectives, Solutions, Vo=
l. 1,
1, pp. 5-19.
Naumann, J., and Jenkins, A. (=
1982)
“Prototyping: The New Paradigm for Systems Development,” MIS Quarterly, Vol. 6, 3, pp. 29-44.
Nash, J., (1950) “Equili=
brium
Points in N-Person Games,” Pr=
oceedings
of the National
Nash, J. (1951)
“Non-Cooperative Games,” Annals
of Mathematics, Vol. 54, 2, pp. 286-295.
Nelson, R. (2005) "Project
Retrospectives: Evaluating Success, Failure and Everything in Between," MIS Quarterly Executive, V=
ol. 4,
3, September pp. 361-372.
Nelson, R. (2007) “IT Pr=
oject
Management: Infamous Failures, Classic Mistakes, and Best Practices,”=
MIS Quarterly Executive, Vol 6, 2,=
June,
pp. 67-78.
Nelson, P.,
Neo, B., Khoo, P., and Ang, S.
(1994) “The Adoption of TradeNet by the Trading Community: An Empiric=
al
Analysis,” in Fifteenth
International Conference on Information Systems,
Nolan,
R., (1976)“Business Nee=
ds a
New Breed of EDP Manager,” Ha=
rvard
Business Review, March-April
pp. 123-133.
Nolan, R., and McFarlan, F.W. =
(2005)
“Information Technology and the Board of Directors,” Harvard Business Review, October p. 96-106.
Nonaka,
Oshri,
Parry,
E. (2004) “Survey Shows More CIOS reporting to CEOs,”
Searchcio.com, September 23, available on
http://searchcio.techtarget.com/originalContent/0,289142,sid19_gci1008202,0=
0.html.
Peppard,
J., Ward, J., and Daniel, E. (20070 “Managing the Realization of Busi=
ness
Benefits from IT Investments,” MIS
Quarterly Executive, Vol. 6, 1, March&=
nbsp;
pp. 1-11.
Pfeffer, J. (1981)Power in Organizations, Pitman
Publishing,
Pfeffer, J. (1994) Managing With Power: Politics and Infl=
uence
in Organizations, Business
Pfeffer, J., and Salancik (197=
8) The External Control of Organizations:=
A
Resource Dependence Perspective, Harper & Row,
Plant, R., Willcocks, L., and =
Olsen,
N. (2003) "Measuring e-business performance: Towards a Revised Balanced
Scorecard Approach," in Inform=
ation
Systems and E-Business Management, Springer-Verlag, 2 pp. 265-281.
Plouffe, C., Hulland, J., and
Vandenbosch, M. (2001), “Research Report: Richness versus Parsimony in
modeling Technology Adoption Decisions-Understanding Merchant Adoption of a
Smart Card-based Payment System,” Information
Systems Research, Vol., 12, 2, pp. 208-222.
Polanyi, M. (1962) “Tacit
Knowing: Its Bearing on Some Problems of Philosophy,” Review of Modern Physics, Vol. 34,=
4, October,
pp. 601-616.
Polanyi, M. (1958) Personal Knowledge: Towards a Post-Cri=
tical
Philosophy, The University of
Poppo, L. and Zenger, T. (1998)
“Testing Alternative Theories of the Firm: Transaction Cost, Knowledge-based,=
and
Measurement Explanations for Make-or-buy Decisions in Information
Services,” Strategic Manageme=
nt
Journal, Vol., 19, pp. 85=
3-877.
Porter, M. (1985) Competitive Advantage: Creating and
Sustaining Superior Performance, Free Press,
Porter, M., and Millar, V. (19=
85)
“How Information Gives You a Competitive Advantage,” Harvard Business Review, Vol. 63,
4, pp. 149-160.
Premkumar, G., Ramamurthy, K.,=
and
Nilakanta, S. (1994) “Implementation of Electronic Data Interchange: =
An
Innovation Diffusion Perspective,” Journal
of Management Information Systems Vol. 11, 2, pp. 157-186.
Prusak, L. (2001) “Where Did Knowledge Management =
Come
From?” IBM Systems Journal, Vol. 40, 4, pp.1002-1007.
Quinn, J., and Baily, M. (1994)
“Information Technology: Increasing Productivity in Services,” =
Rai, A., and Howard, G. (1993)
“An Organizational Context for CASE Innovation,” Information Resources Management Journ=
al, Vol.
6, 3, pp. 21-34.
Rai, A., and Howard, G. (1994)
“Propagating CASE usage for Software Development: An Empirical
Investigation of Key Organizational Correlates,” OMEGA, Vol. 22, 2, pp.
133-147.
Ramamurthy, K., and Premkumar,=
G.
(1995) “Determinants and Outcomes of Electronic Data Interchange
Diffusion,” IEEE Transactions=
on
Engineering Management, Vol. 42, 4, pp. 332-351.
Ravichandran, T. (2000)
“Swiftness and Intensity of Administrative Innovation Adoption: An
Empirical Study of TQM in Information Systems,” Decision Sciences, Vol. 31, 3,=
pp. 691-724.
Roach,
S. (1986) Macro-economic Realities =
of the
Information Economy, National A=
cademy
of Sciences,
Roberts, B., Jarvenpaa, S., Ba=
xley,
C. (2003) "Evolving at the Speed of Change: Mastering Change Readiness=
,"
MIS Quarterly Executive, Vol. 2=
, 2,
September pp. 58-73.
Rockart, J. (1979) “Chief
Executives Define their Own Data Needs,” Harvard Business Review, March-April, pp. 81-92.
Rockart, J., Ball, L., and Bul=
len,
C. (1982) “Future Role if the Information Systems Executive,” MIS Quarterly, pp.1-14.
Ross, J. (2003) "Creating=
a
Strategic IT Architecture Competency: Learning in Stages," MIS Quarterly Executive, Vol. 2, 1,
March, pp. 31-43.
Ross, J., and Beath, C. (2006)
“Sustainable IT Outsourcing Success: Let Enterprise Architecture be y=
our
Guide,” MIS Quarterly Executi=
ve, Vol.
5, 4, December pp. 187-192.
Rottman, J., and Lacity, M. (2=
006)
"Proven Practices for Effectively Offshoring IT Work," Sloan Management Review, Vol. 47, =
3,
Spring, pp. 56-63.
Sabherwal, R., Jeyaraj, A., and
Chowa, C. (2006) “Information Systems Success: Individual and Organiz=
ational
Determinants,” Management Sci=
ence,
Vol. 52, 12, December pp.
1894-1864.
Sambamurthy, V., and Zmud, R. =
(1999)
“Arrangements for Information Technology Governance: A Theory of Mult=
iple
Contingencies,” MIS Quarterly=
, Vol.
23, 2, pp. 261-291.
Sauer, C. (1993) Why Information Systems Fail, Alfr=
ed
Waller Ltd.,
Schwarz, A., and Hirschheim, R.
(2003) “An Extended Platform Logic Perspective of IT Governance: Mana=
ging
Perceptions and Activities of IT,” Journal
of Strategic Information Systems, Vol. 12, 2, July, pp. 129-166.
Scott, J. (1999) “The Fo=
xMeyer
Drugs Bankruptcy: Was it a failure of ERP?” Assoc. IS 5th
Searle, John (1997) The Construction of Social Reality, The
Free Press,
Sethi, V. and King, W. (1994)<=
span
style=3D'mso-spacerun:yes'> “Development of Measures to =
Assess
the Extent to Which an Information Technology Application Provides Competit=
ive
Advantage,” Management Scienc=
e,
Vol. 40, 12, pp. 1601-1628.
Standish Group International (=
2003) Standish Group Chaos Report, CHAOS
Chronicles V3.0,
available on
http://www.standishgroup.com/chaos/toc.php.
Stephens, C., Ledbetter, W., M=
itra,
A., and Ford, F. (1992) “Executive or Functional Manager? The Nature =
of
the CIO’s Job,” MIS
Quarterly, Vol. 16, 4, December
pp. 449-468.
Straub, D., Limayem, M., and
Karahanna-Evaristo, E. (1995) “Measuring System Usage: Implications f=
or
IS Theory Testing,” Management
Science, Vol. 41, 8, pp.
1328-1342.
Straub, D., Keil, M., and Bren=
ner,
W. (1997) “Testing the Technology Acceptance Model across Cultures: A
Three Country Study,” Informa=
tion
& Management, Vol., 33, 1, pp. 1-11.
Swanson, E.B. (1994)
“Information Systems Innovation among Organizations,” Management Science Vol. 40, 9, pp. 1069-1092.
Swap et. al. (2001) "Usin=
g Mentoring
and Storytelling to Transfer Knowledge in the Workplace," Journal
of Management Information Systems, Vol. 18, 1, Summer pp. 95-114.
Szajna, B. (1996) "Empiri=
cal
Evaluation of the Revised Technology Acceptance Model," Management Science, Vol., 42, 1, pp. 85-92.
Taylor, S., and Todd, P. (1995=
) “Understanding Information
Technology Usage: A Test of Competing Models,” Information Systems Research, Vol. 6, 2, 1995, pp. 144-176.
Teng, J., Cheon, M., and Grove=
r, V.
(1995) "Decisions to Outsource IS Functions: Testing a Strategy-Theore=
tic
Discrepancy Model," Decision
Sciences, Vol. 26, 1, January/February=
pp. 75-103.
Teng, J.., Grover, V., and Gut=
tler,
W. (2002) “Information Technology Innovations: General Diffusion Patt=
erns
and its Relationships to Innovation Characteristics,” IEEE Transactions on Engineering Manag=
ement,
Vol. 49, 1, pp. 13-27.
Thong, J., and
Venkatesh, V., Morris, M., Dav=
is,
G., and Davis, F., (2003) “User Acceptance of Information Technology:
Toward an Unified View,” MIS
Quarterly, Vol. 27, 3, pp.
425-478.
Venkatraman, N. (1997) “=
Beyond
Outsourcing: Managing IT Resources as a
Wallace, L., Keil, M., and Rai=
, A.
(2004) “How Software Project Risk Affects Project Performance: An
Investigation of the Dimensions of Risk and an Exploratory Model,” Decision
Sciences, Vol. 35, 2, Spring&nb=
sp;
pp. 289-121.
Ward, J., Taylor, P., and Bond=
, P.
(2006) "Evaluation and
Realisation of IS/IT Benefits: An empirical investigation of Current
Practice," European Journal of
Information Systems, Vol 4, 4,
pp. 214-225.
Weill, P., and Aral, S. (2006)=
“Generating Premium Returns on Your IT Investments,” Sloan Management Review, Vol. 47, =
2,
Winter, pp. 39-48.
Weill, P., and Ross, J. (2004)=
IT
Governance: How Top Performers Manage IT Decisions for Superior Results,
Weill, P., and Ross, J. (2005)=
“A Matrixed Approach to Desi=
gning
IT Governance,” Sloan Managem=
ent
Review, Winter Vol. 46, 2, pp. 26-34.
Whang, S., (1992) “Contracting for Software
Development,” Management Scie=
nce,
Vol 38, 3, pp. 307-324.
Willcocks, L., and Lacity, M.
(2006) Global Sourcing of Business and IT Services, Palgrave, United
Kingdom.
Willcocks, L., and Lester, S. =
(eds)
(1999), Beyond the IT Productivity
Paradox, Wiley,
Willcocks, L., Feeny, D., and =
Islei,
G. (eds) (1997) , Managing IT as a
Strategic Resource, McGraw Hill,
Williamson, O., (1991) “Comparative Economic
Organization: The Analysis of
Discrete Structural Alternatives,” Administrative
Science Quarterly, Vol. 36, 2, June&nb=
sp;
pp. 269-296.
Williamson, O. (1979)
“Transaction Cost Economics: The Governance of Contractual
Relations,” Journal of Law and
Economics, Vol. 22, 2, October
pp. 233-261.
Zmud, R., and Apple, L. (1992)=
“Measuring Technology Incorp=
oration/Infusion,”
Journal of Product Innovation Manag=
ement,
Vol. 9, 2, pp. 148-155.
Zwieg, P., Kaiser, K. M., Beat=
h, C.,
Bullen, C., Gallagher, K., Goles, T., Howland, J., Simon, J. Abbott, P.,
Abraham, T., Carmel, E., Evaristo, R., Hawk, S., Lacity, M., Gallivan, M.,
Kelly, S., Mooney, J., Ranganathan, C., Rottman, J., Ryan, T., Wion, =
R.,
(2006) “ The Information
Technology Workforce Trends and Implications 2005-2008,” MIS Quarterly Executive, Vol. 5, 2=
, pp. 47-54.
[1] The PMI has more than 150,000 members in over 150 countries and is the world’s foremost advocate for the project management profession. To be certified PMP, candidates must have a baccalaureate degree and 4500 hours of project management experience in at least 5 project management process groups. (Or 7500 hours of pro= ject management experience if the candidate does not have a baccalaureate degree.) In addition, candida= tes must have 35 contact hours of Project Management Education and pass a 200 i= tem examination. After obtaining certification, PMPs must satisfy additional requirements to retain their certification.