Article Preview
TopIntroduction
In the study of project management, it is often desired to discover why a project succeeded or failed. While the definition of project success may be disputed, it is commonly defined in the textbooks as occurring when a project produces the desired deliverables on time, on budget and with the proper quality (Brewer & Dittman, 2010; Gray & Larson, 2008; Kerzner, 2009; Schwalbe, 2007). However many times these goals are not met. The CHAOS study of the Standish Group has documented much of the issues of information systems project management (Rubenstein, 2007) in that many projects fail to deliver anything at all and many fail to achieve one or all of the goals of a successful project.
Two characteristics of projects stand out as important to be considered in the study of their success. The first characteristic is that they are designed to be change activities. Projects are commonly defined as an activity with a defined lifespan, an established objective, cross-functional involvement and novel objectives (Gray & Larson, 2008; Schwalbe, 2007). The novel objectives described in the definition indicate that projects are designed to bring something to pass that has not existed before. That new something may be an information technology artifact, a redesigned work system or the implementation of technology into a business process. In all these cases, change is involved. In information systems, we can consider the process in two phases: development of the IT artifact and then its implementation in an organization. In the first phase, the IT artifact is brought into existence, a change from conception to reality. In the second phase, business processes are changed to incorporate the IT artifact.
Second, the definition tells us that those projects, especially information technology projects, are social activities in that they usually have cross-functional involvement. It is not an individual activity but one in which groups of people interact either in harmony or in conflict. In developing an information system groups of developers and users interact to bring the IT artifact into existence. Similarly, when an artifact is implemented into an organization, the developers and users interact to create a new business system that incorporates the artifact. The resultant artifact or implementation of an artifact is rarely that which is intended by any one of the parties. Rather, it is usually the outcome of the negotiated interactions between the parties.
Thus, the study of project success or failure (outcomes) requires an approach that considers the social aspects of change. In the field of sociology, one of the major concerns has been the issue of creating a general model of change in social structures. The question is asked that if we have a social structure such as a culture, division of labor, organizations etc. how do those structures come into existence and how do they change over time? In particular, how do actors and agencies interact with the structures to produce such change and under what circumstances does it occur? This type of questions seems to be very useful for information systems research. If we consider such things as business processes (whether they involve technology artifacts or not) as social structures, then social theory, the use of theoretical frameworks to study and interpret social structures and phenomena (Wikipedia, 2009), could be one way that we can analyze project interactions to explain how the project generated the results that it did.