This inductive case study research examines the sales cycle of eight information systems (IS) providers situated in Australia, Hong Kong, Europe, and the United States. The study found that the IS sales cycle provides a restrictive covenant for ensuing projects with contractual constraints, having consequences for fundamental project factors such as benefits, scope, and cost. The process also impedes solution design, schedule, extent of customizations, and training. There are many implications for improvements to practice, in particular there should be more focus placed upon business benefits and increased awareness of life cycle cost during the sales process.
AhlemannF. (2009). Towards a conceptual reference model for project management information systems. International Journal of Project Management27, 19–30.
2.
AlhorrH., NiedermanF., ParkY., & TolmieC. R. (2012). Global: What have we learned in the past decade?Journal of Global Information Management, 20(1), 18–56.
3.
AndersenS. E. (2010). Are we getting any better? Comparing project management in the years 2000 and 2008. Project Management Journal, 41, 4–16.
4.
BassellierG., BenbasatI., & RecihB. H. (2003). The influence of business managers' IT competence on championing IT. Information Systems Research, 14(4), 317–336.
5.
BroadbentM., & WeillP. (1997). Management by maxim: How business and IT managers can create IT Infrastructures. Sloan Management Review, 38(3), 77–92.
6.
BurnR. B. (1994). Introduction to research methods.Melbourne, Australia: Longman Cheshire.
7.
CaoQ., & HoffmanJ. J. (2011). A case study approach for developing a project performance evaluation system. International Journal of Project Management, 29, 155–164.
8.
ChenW. T., ChangP., & HuangY. (2010). Assessing the overall performance of value engineering workshops for construction projects. International Journal of Project Management, 28, 514–527.
9.
Cooke-DaviesT. (2002). The “real” success factors in projects. International Journal of Project Management, 20, 185–190.
10.
CresswellJ. W. (1994). Research design: Qualitative and quantitative approaches.Thousand Oaks, CA: Sage Publications.
11.
DavenportT. H. (1998). Putting the enterprise into the enterprise system. Harvard Business Review, 76(4), 121–131.
12.
EisenhardtK. M. (1989). Building theories from case study research. Academy of Management Review, 14(4), 532–550.
13.
FulfordR., & LoveP. E. D. (2004). Propagation of an alternative enterprise service application adoption model. Industrial Management & Data Systems Journal, 104(6), 450–456.
14.
GlaserB. (1992). Basics of grounded theory analysis.Mill Valley, CA: Sociology Press.
15.
GosainS. (2004). Enterprise information systems as objects and carriers of institutional forces: The new iron cage?Journal of the Association for Information Systems, 5(4), 151–182.
16.
GrantG. G. (2003). Strategic alignment and enterprise systems implementation: The case of Metalco. Journal of Information Technology, 18(3), 159–175.
17.
GustinC. M., DaughertyP. J., & EllingerA. E. (1997). Supplier selection decisions in systems/software purchases. International Journal Purchase Management, 4(Fall), 1–46.
18.
HobdayM. (1998). Product complexity, innovation and industrial organization. Research Policy, 26, 689–710.
19.
JimenezG., & PascualL.B.(2008). Multicriteria cash-flow modelling and project value-multiples for two-stage project valuation. International Journal of Project Management, 26, 185–194.
20.
JohnsonG., ScholesK., & WhittingtonR. (2008). Exploring corporate strategy: Texts and cases (8th ed.). Harlow, United Kingdom: Prentice Hall.
21.
KallinikosJ. (2004). Deconstructing information packages: Organizational and behavioural implications of ERP systems. Information Technology and People, 17(1), 8–30.
22.
KingJ. L., & SchremsE. L. (1978). Cost-benefit analysis in information systems development and operation. ACM Computer Survey, 10(1), 19–34.
23.
LorenzoO., & KawalekP. (2005). Embedding the enterprise systems into the enterprise: A model of corporate diffusion. Communications of the AIS, 15, 609–641.
24.
LuarnP., LinT. M. Y., & LoP. K. Y. (2005). Non-enforceable implementation of enterprise mobilization: An exploratory study of the critical success factors. Industrial Management + Data Systems, 105(6), 786–814.
25.
MarkusM. L., & TanisC. (2000). The enterprise system experience: From adoption to success. In ZmudR.W. (Ed.), Framing the domains of IT research: Glimpsing the future through the past (pp. 173–207). Cincinnati, OH: Pinnaflex Publishing.
26.
McKayJ., & MarshallP. (2004). Strategic management of e-business.Brisbane, Australia: Wiley.
27.
McMurrayA. J., PaceW. R., & ScottD. (2004). Research: A commonsense approach.Sydney, Australia: Thomson Social Science Press.
28.
MelinU. (2003, June). The ERP system as a part of an organization's administrative paradox. Paper presented at the 11th European Conference on Information Systems, Naples, Italy.
29.
MilesM. B., & HubermanA. M. (1994). Qualitative data analysis (2nd ed.). Thousand Oaks, CA: Sage Publications Ltd.
30.
MirandaE., & AbranA. (2008). Protecting software development projects against underestimation. Project Management Journal, 39, 75–85.
31.
MortonN. A., & HuQ. (2004, August). The relationship between organizational structure and enterprise resource planning systems: A structural contingency theory approach. Paper presented at the 10th Americas Conference on Information Systems, New York, NY.
32.
MurphyK. E., & SimonS.J. (2002). Intangible benefits valuation in ERP projects. Information Systems Journal, 12, 301–320.
33.
ParéG. (2004). Investigating information systems with positivist case study research. Communications of the Association for Information Systems, 13, 233–264.
34.
ParkerM. M., BensonR. J., & TrainorH. E. (1988). Information economics: Linking business performance to information technology.Englewood Cliffs, NJ: Prentice-Hall.
35.
PatanakulP., & ShenharA. J. (2012). What project strategy really is: The fundamental building block in strategic project management. Project Management Journal, 43(1), 4–20.
36.
PeslakA. R. (2012). An analysis of critical information technology issues facing organizations. Industrial Management & Data Systems, 112(50), 808–827.
37.
PostonR., & GrabskiS. (2000, December). The impact of enterprise resource planning systems on firm performance. Paper presented at the 21st International Conference on Information Systems, Brisbane, Queensland, Australia.
38.
Project Management Institute. (2013). A guide to the project management body of knowledge (PMBOK® guide)—Fifth edition. Newtown Square, PA: Author.
39.
PunchK. (1998). Introduction to social research: Quantative and qualitative approaches.London, England: Sage.
40.
RemenyiD. (2001). Business models for e-business.Henley-on-Thames, England: Henley College of Management.
41.
RemenyiD., Sherwood-SmithM., & WhiteT. (1997). Achieving maximum value from information systems: A process approach.New York, NY: John Wiley & Sons.
42.
SauerC., & ReichB. H. (2007). Rethinking IT project management: Evidence of a new mindset and its implications. International Journal of Project Management, 27(2), 182–193.
43.
StewartR. A. (2008). A framework for the life cycle management of information technology projects: Project IT. International Journal of Project Management, 26, 203–212.
44.
StrassmannP. A. (1995). The politics of information management.New Canaan, CT: Information Economics Press.
45.
ThomasG., & FernándezW. D. (2008). Success in IT projects: A matter of definition?International Journal of Project Management, 26(7), 733–742.
46.
ToorS. R., & OgunlanaS. O. (2010). Beyond the “iron triangle: ” Stakeholder perception of key performance indicators (KPIs) for large-scale public sector development projects. International Journal of Project Management, 28, 228–236.
47.
TysselandB. E. (2008). Life cycle cost based procurement decisions: A case study of Norwegian defence procurement projects. International Journal of Project Management, 26, 366–375.
48.
VenkataramanR., & PintoJ. (2008). Cost and value management in projects.Hoboken, NJ: John Wiley and Sons.
49.
WattD. J., KayisB., & WilleyK. (2009). Identifying key factors in the evaluation of tenders for projects and services. International Journal of Project Management, 27, 250–260.
50.
WattD. J., KayisA., & WilleyA. K. (2010). The relative importance of tender evaluation and contractor selection criteria. International Journal of Project Management, 28, 51–60.
51.
WardJ., HemingwayC., & DanielE. (2005). A framework for addressing the organisational issues of enterprise systems implementations. Journal of Strategic Information Systems, 14, 97–119.
52.
WhittakerL., & BeswickC. (2008). When a sure thing goes awry: Implementing an enterprise system at IST Ltd. Management Dynamics, 17(2), 27–39.
53.
WillcocksL. P., & SykesR. (2003). The role of the CIO and IT functions in ERP. In ShanksG., SeddonP., & WillcocksL. (Eds.), Second-wave enterprise resource planning systems.Cambridge, England: Cambridge University Press.
54.
WikströmK., HellströmM., ArttoK., KujalaJ., & KujalaS. (2009). Services in project-based firms: Four types of business logic. International Journal of Project Management, 27, 113–122.
55.
WikströmK., KarlosA., KujalaJ., & SöderlundJ. (2010). Business models in project business. International Journal of Project Management, 28, 832–841.
56.
WilliamsT., & SamsetK. (2010). Issues in front-end decision making on projects. Project Management Journal, 41, 38–49.
57.
WuF., LiH. Z., ChuL. K., SculliD., & GaoK. (2009). An approach to the valuation and decision of ERP investment projects based on real options. Annals of Operations Research, 168(1), 181–203.
58.
YinR. K. (2003a). Applications of case study research (2nd ed.). Thousand Oaks, CA: Sage Publications Ltd.
59.
YinR. K. (2003b). Case study research design and methods (3rd ed.). Thousand Oaks, CA: Sage Publications.
