Project leadership and a favorable development environment both are important to the successful delivery of an information system (IS). One issue that confronts organizations is where the responsibility for creating a positive environment lies. Should the project manager be responsible for building the climate to suit the needs of the project team, or should the organization provide the climate? Data from a survey of Project Management Institute members involved with IS projects indicates that the project manager's performance is a better predictor of project outcome, but preproject partnering and software implementation policies directly relate to the project manager's performance.
CronbachL.J. (1951). Coefficient alpha and the internal structure of tests.Psychometrika, 16, 297–334.
5.
FrameJ.D. (1994). The new project management: Corporate reengineering and other business realities.San Francisco: Jossey Bass.
6.
GemmillG., & WilemonD. (1994). The hidden side of leadership in technical team management.Research-Technology Management, (November-December), 237–245.
7.
GoodmanP.S., RavlinE., & SchminkeM. (1987). Understanding groups in organizations. In CummingL.L., and StawB.M. (eds.), Research in Organizational Behavior.Greenwich, CN: JAI Press, 121–173.
8.
JiangJ.J., & KleinG. (2000). Software development risks to project effectiveness.Journal of Systems and Software, 52, 3–10.
9.
JiangJ.J., KleinG., & BallounJ. (1996). Ranking of system implementation success factors.Project Management Journal, 27(4), 50–55.
10.
JiangJ.J., KleinG., & CramptonS. (1998). System development risks and project team performance.The Proceeding of 1998 DSI National Meeting, Las Vegas, Nov. 21–24, 813–815.
11.
JiangJ.J., KleinG., & MargulisS. (1998). Important behavioral skills for IS project managers: The judgments of experienced IS professionals.Project Management Journal, 29(1), 39–44.
12.
KanterR.M. (1997). The role of the technical leader.KatzR. (ed) The Human Side of Managing Technological Innovation.Oxford: University Press.
13.
KerlingerF.N. (1986). Foundations of behavioral research.New York: Holt-Rinehart and Winston.
14.
KhuranaA., & RosenthalS.R. (1997). Integrating the fuzzy front end of new product development.Sloan Management Review, 38(2), 103–120.
15.
LarsonE., & GobeliD. (1989). Significance of project management structure on development success.IEEE Transactions on Engineering Management, EM-36(2), 119–125.
16.
LarsonE.W. (1997). Partnering on projects: A study of the relationship between partnering activities and project success.IEEE Transactions on Engineering Management, EM-44(2), 188–195.
17.
LyytinenK. (1988). Expectation failure concept and system analyst's view of information systems failures: Results of an exploratory study.Information & Management, 14, 45–56.
18.
NadlerD.A., & TushmanM.L. (1990). Beyond the charismatic leader: Leadership and organizational change.California Management Review, 32(2), 77–97.
19.
PintoJ.K., & KharbandaO.P. (1995a). Successful project managers: Leading your team to success.New York: Van Nostrand Reinhold.
20.
PintoJ.K., & KharbandaO.P. (1995b). Lessons for an accidental profession.Business Horizons, (March-April), 41–50.
21.
RobertsE.B., & FusfeldA.F. (1997). Informal leadership roles in the innovation process.KatzR. (ed.), The human side of managing technological innovation.New York: Oxford University Press, 273–295.
22.
ThamhainH.J., & WilemonD.L. (1987). Building high performing engineering project teams.IEEE Transactions on Engineering Management, EM-34(3), 130–137.
23.
WheelwrightS.C., & ClarkK.B. (1992). Creating project plans to focus product development.Harvard Business Review, 70(2), 70–82.
