Building Effective Project Teams

Most IS managers know that managing a project to its successful completion is not an easy task. Conflicts among team members often delay a project's schedule and can ruin the team's morale. Although most managers usually follow the traditional, authoritative style of management to control their team members, this style is no longer considered as effective as the more contemporary, collaborative approach. This article describes how IS managers can manage their projects more effectively by creating collaborative project teams.     

Building Effective Project Teams

Most IS managers know that managing a project to its successful completion is not an easy task. Conflicts among team members often delay a project's schedule and can ruin the team's morale. Although most managers usually follow the traditional, authoritative style of management to control their team members, this style is no longer considered as effective as the more contemporary, collaborative approach. This article describes how IS managers can manage their projects more effectively by creating collaborative project teams.     

Exploiting organizational knowledge in developing IS project cost and schedule estimates: An empirical study

Project management is vital to the effective application of organizational resources to competing demands within and across projects. The effective application of project management, however, is predicated upon accurate estimates of the project budget and schedule. This study assesses primary and supporting activities that exploit knowledge within an organization's memory to develop project schedule durations and budgets. The study further assesses the subsequent impact of predictability on project success. Two hundred and sixteen survey responses from IT professionals with project management responsibilities were analyzed. Results found use of the primary activities of using parametric estimating techniques (use of formal models), bottom-up estimating techniques (formulating estimates at the task level), and the support activities of team reliance, realistic targets, and professional experience all impact the predictability of estimates for project cost and duration. Predictability in turn was found to directly impact project success with regards to meeting cost and duration objectives. While use of analogous estimating techniques (using similar previous projects) was not found to be useful for project managers with more experience, it was used by project managers with less experience in determining predictability.     

Implementation of best manufacturing practices using logic models and system dynamics: project design and project assessment views

In today’s global competitive environment, the need for continuous improvement is a matter of considerable importance within manufacturing enterprises. To this end, project managers, and managers in general, design and assess different projects with the purpose of achieving efficient processes, reducing costs and waste, increasing product and service quality, developing new products and services, enhancing customer relationship management, optimising enterprise resources, and so on. However, it is well-known that managing enterprise resources in order to accomplish effective completion of projects is a complex task to carry out. Furthermore, it has been recognised that the way staff actually understands the purpose of a project, the way they perform different project activities, and how they are able to influence project design and assessment are key factors for influencing the success of a project. This paper presents a systemic methodology to design and assess projects more effectively and efficiently based on program logic models and system dynamics with the aim of facilitating a clear understanding of the needs, purposes, goals, activities and tasks of a project among its stakeholders towards achieving success.     

Factors that motivate software engineering teams: A four country empirical study

Motivation, although difficult to quantify, is considered to be the single largest factor in developer productivity; there are also suggestions that low motivation is an important factor in software development project failure. We investigate factors that motivate software engineering teams using survey data collected from software engineering practitioners based in Australia, Chile, USA and Vietnam. We also investigate the relationship between team motivation and project outcome, identifying whether the country in which software engineering practitioners are based affects this relationship. Analysis of 333 questionnaires indicates that failed projects are associated with low team motivation. We found a set of six common team motivational factors that appear to be culturally independent (project manager has good communication with project staff, project risks reassessed, controlled and managed during the project, customer has confidence in the project manager and the development team, the working environment is good, the team works well together, and the software engineer had a pleasant experience). We also found unique groupings of team motivational factors for each of the countries investigated. This indicates that there are cultural differences that project managers need to consider when working in a global environment.     

A model of information systems development project performance

abstract. Performance in information systems development (ISD) projects can be critical to business success. But, while project performance has been the subject of much debate, there has been little empirical research into its determinants. A survey of IS projects in the UK and New Zealand is analysed to test hypotheses concerning performance in terms of both project completion and budget (time-cost) variances. Subsequently, a secondary analysis of the findings is used to build a more complete empirical model of project performance. The paper helps to develop the theory of IS development project performance and also has significant implications for practice. Discussion of the findings highlights the importance of project team dynamics, risk management, senior management support for strategic projects and user participation in ensuring successful IS project performance.     

The optimization of success probability for software projects using genetic algorithms

The software development process is usually affected by many risk factors that may cause the loss of control and failure, thus which need to be identified and mitigated by project managers. Software development companies are currently improving their process by adopting internationally accepted practices, with the aim of avoiding risks and demonstrating the quality of their work.This paper aims to develop a method to identify which risk factors are more influential in determining project outcome. This method must also propose a cost effective investment of project resources to improve the probability of project success.To achieve these aims, we use the probability of success relative to cost to calculate the efficiency of the probable project outcome. The definition of efficiency used in this paper was proposed by researchers in the field of education. We then use this efficiency as the fitness function in an optimization technique based on genetic algorithms. This method maximizes the success probability output of a prediction model relative to cost.The optimization method was tested with several software risk prediction models that have been developed based on the literature and using data from a survey which collected information from in-house and outsourced software development projects in the Chilean software industry. These models predict the probability of success of a project based on the activities undertaken by the project manager and development team. The results show that the proposed method is very useful to identify those activities needing greater allocation of resources, and which of these will have a higher impact on the projects success probability.Therefore using the measure of efficiency has allowed a modular approach to identify those activities in software development on which to focus the project's limited resources to improve its probability of success. The genetic algorithm and the measure of efficiency presented in this paper permit model independence, in both prediction of success and cost evaluation.     

Mediators between coordination and IS project performance

Successful IS projects result from coordination among team members and stakeholders. We examined the effects of horizontal and vertical coordination on project performance. A total of 169 responses from IS project managers listed in the Project Management Institute of the USA were solicited, obtained, and analyzed. The results indicated that horizontal coordination can enhance the level of leadership empowerment and knowledge transfer, and help to clarify the mission and objectives among team members, while vertical coordination can enhance knowledge transfer. The results further suggested that project performance was improved by empowering team members, promoting knowledge transfer among team members and specifying clear mission and project objectives.     

Impacts of collaborative IS on software development project success in Indian software firms: a service perspective

The collaborative work of team members has become a common occurrence in software development projects. Collaborative information systems (CIS), designed to facilitate and support teamwork, appear critical for software project success. However, the quality and convenience of the services and functions delivered by CIS have not received robust attention in academia. Hence, the current study investigates the role of the CIS service characteristics of service quality and service convenience in teamwork and software development project success using DeLone and McLean’s (D&M) Information System (IS) Success Model as the theoretical framework. This study incorporates the success indicators of teamwork quality, teamwork performance, and project success as measured by software quality and project performance. Data from 153 Indian software companies confirm that collaborative IS services, as well as teamwork quality/performance, are central to software development project success. We believe that the findings of this study will be helpful to project managers of software development firms.     

Do organizational citizenship behaviors lead to information system success?: Testing the mediation effects of integration climate and project management

We adapted a model in organizational theory to determine whether organizational citizenship behaviors (OCBs) of system implementation teams influenced that organization's integration climate and improved their project management, resulting in successful system implementation. Surveys were elicited from 254 system users in various business organizations that had implemented large-scale IS in the previous year; the analysis of their responses provided support for our model, suggesting that the OCB of the implementation team created a higher level of integration climate and more effective project management, and that these in turn influenced information system success. Implications for researchers and managers are discussed and limitations are identified.     

The role of project management in ineffective decision making within Agile software development projects

Decision making in traditional software development lies with the project manager. In contrast, Agile software development teams are empowered to make decisions, while the role of project manager has changed from one of command and control (i.e. to make decisions and ensure they are implemented) to one of a facilitator. This article argues that decision making in software development is not characterised by a sequence of isolated or exclusive decisions; rather, decisions are inter-related, with each decision leading to further decisions, the chain of which often spans the entire duration of a project. Over this extended period, there are several potential factors that can negatively affect the efficacy of decision making by Agile teams. One of the findings of this exploratory longitudinal study is that the high level of empowerment of a cohesive software development team undertaking an Agile project may be one of these negative factors, as empowered, cohesive teams can exhibit problems such as groupthink or the Abilene Paradox. This article therefore argues that the role of project manager in Agile development initiatives needs to be reassessed, with project managers taking on the role of devil's advocate in the decision-making process.     

Concept for multidevelopment project and team organization of product and process generations

Large and middle-sized manufacturers need to carry out multiple development projects simultaneously to serve a variety of products to markets with different customer needs. The purpose of this article is to explore product development project and team organization with respect to technology and design transfer strategy among multiple development projects, as well as their impact on project integrity and performance. The focus is on the strategic and cross-functional integration of product and process generations with distinctive platforms and their derivative projects. First, this study proposes a concept of multilayer development project and team organization, which builds a creative environment through effective information sharing among and within the individual development projects and teams. Second, using analysis results on six product development projects at a large Japanese computer manufacturer, it is concluded that multilayer teams are effective in realizing project integrity through implementing inter- and intraproduct and process generation technology and design transfer strategy. © 1998 John Wiley & Sons, Inc.     

Blending bureaucratic and collaborative management styles to achieve control ambidexterity in IS projects

Managing information systems (IS) projects requires what we refer to as ‘control ambidexterity’, which is the use of different types of control to meet conflicting demands. This leads to the use of contrasting styles of IS project management and creates tensions in managerial practice, neither of which are well understood. We address this theoretical gap in our understanding based on an exploratory case study of an IS implementation project in the financial services industry. Adopting the lens of management styles as a meta-theoretical perspective, we sought to address two research questions: (1) Which management style(s) do IS project managers draw upon in practice and why? (2) What kinds of tensions result for IS project managers and team members from drawing upon contrasting management styles in combination – and how do IS project managers and team members deal with these tensions? Two contrasting styles of management emerged from our data – bureaucratic and collaborative – that are drawn upon by IS project managers to achieve control ambidexterity. Furthermore, drawing upon these two different styles in combination within the confines of a single project creates tensions. We explore these tensions and present an illustrative example of how IS project managers can deal with these tensions successfully in practice. Specifically, we find that they can be dealt with effectively by a tandem of two project managers who share responsibility for managing the IS project. The findings of this study have important implications for our understanding of control ambidexterity in IS projects.     

Case study: factors for early prediction of software development success

Project managers can make more effective and efficient project adjustments if they detect project high-risk elements early. We analyzed 42 software development projects in order to investigate some early risk factors and their effect on software project success. Developers in our organization found the most important factors for project success to be: (1) the presence of a committed sponsor and (2) the level of confidence that the customers and users have in the project manager and development team. However, several other software project factors, which are generally recognized as important, were not considered important by our respondents.     

Towards an integrated measurement of IS project performance: The project performance scorecard

Determining the contribution of information system (IS) projects is a difficult endeavour. This research presents a framework for evaluating and measuring IS project performance that seek to address this problem while moving away from the reliance on the traditional assessment method (time, cost, specifications). When IS projects fail or succeed is difficult to determine what conditions enabled the outcome. However, if we are to develop a higher level of IS project management competence we need frameworks that can help in assessing IS project outcomes while critically reflecting and learning from IS project management practices. The Project Performance Scorecard (PPS) recommended here is one framework that can help to advance our understanding IS project management and evaluation approaches. This framework integrates concepts from existing models of IS success, the Balanced Scorecard and project management practices. A case study approach is used to illustrate the use of the PPS, and offers insights into how it can be useful in assessing the performance of IS projects.

User commitment and collaboration: Motivational antecedents and project performance

ContextPrior research into the success of information system development projects views user commitment and collaboration as unrelated concepts in models that take either a perspective of mediators or one of processes. This perspective is limiting in that mediators and processes may interact during the course of an information system development project.ObjectiveIn this work, we model both mediators and processes as important to project outcomes and propose that processes will also be impacted by affective mediators, specifically the behavioral mediator of user commitment and the project process of collaboration. The model also allows behavioral antecedents to be considered in relation to the mediation variable, specifically the ability of the users and the extrinsic motivators perceived by the users.MethodA questionnaire containing constructs of collaboration processes, user commitment, abilities, and extrinsic motivation are completed by users in a development project and project success is measured by the IS staff for a matching independent variable. 128 matching pairs were collected and the model analyzed using partial least squares regression.ResultsResults indicate that the affective mediator can be influenced by the tested antecedents showing that IS project managers should be able to choose users with essential abilities and also establish sufficient rewards to employees, even those who may not be direct subordinates. Similarly, collaboration is still important to the success of a project, indicating that procedures to encourage collaboration be installed from the beginning of the project. However, commitment alone is sufficient to predict collaboration, meaning that motivation outside the processes in place may not be necessary to encourage collaboration between the users and IS staff.ConclusionIS researchers should consider both process mediators and affective states in future work when considering the link between antecedent inputs of software projects to the success of outputs. IS managers should promote commitment among users beyond placing collaboration mechanisms in place. This might require project managers have more decision authority in the rewards provided to user participants.     

Determinants of software quality: A survey of information systems project managers

Software quality is important for the success of any information systems (IS). In this research, we find the determinants of software quality. We used five attributes for software quality: system reliability, maintainability, ease of use, usefulness, and relevance. By surveying 112 IS project managers, we collected data about their perceptions on the software quality attributes and their determinants. We arrived at six factors through exploratory factor analysis. We determined the individual factors that impacted the software quality attributes; for example, reliability is associated with responsiveness of IS department; ease of use is influenced by the capabilities of users and attitude of management; and usefulness is impacted by capabilities of IS department and responsiveness of IS department. We show that organizational factors are more important than technical factors in impacting software quality in IS projects. We provide implications of our research to practice and to future research.     

An OO project management strategy

Large object oriented projects pose coordination, logistical, and communication problems for managers. We have developed a strategy designed to help solve these problems. Our strategy calls for an iterative development process. In addition, we call for specialized work teams and the division of projects into strategic and tactical areas. Strategic processes address issues that have system-wide ramifications, such as system architecture. The strategic work is divided into setup, architecture definition, and development phases. Tactical processes address day-to-day activities, such as software design and testing. Dividing a project this way for organization and management purposes allows strategic and tactical issues to be addressed in a more focused and effective manner     

Distributed Java applets for project management on the Web

The rapid evolution of our data communications infrastructure is making distributed projects increasingly viable. Without a common infrastructure, computer-supported collaborative tools for distributed teams have been prohibitively expensive to build and maintain. However, the increasing availability of the Internet is enabling companies to develop cost-effective collaborative solutions. Traditional desktop project management software is designed as a single-user tool that lets the project manager track tasks, milestones and deliverables. As teams spread over geographic distances with multiple centers of control, the communication, coordination, and tracking of ongoing project activity become key issues for project success. This article looks beyond the traditional planning focus of project management applications to a network-centric focus on collaboration. It describes the implementation of ActionPlan, a 100 percent Java-based application from Netmosphere that supports real-time collaboration among Java thin clients to facilitate distributed project management     

Integrating Process and Project Management for Multi-Site Software Development

Recent advances in information technology have made Internet-based collaboration much easier. It is now possible for a software team to draw on talented developers from around the world without the need to gather them together physically. However, being able to tap into a large pool of talent does not guarantee success. Software managers have to be able to manage these distributed teams. They need to define sharper processes and ensure that they are followed. They also need to better control project execution. To do so effectively, we have developed a tool that integrates features for both project and process management. Existing project management tools were originally designed for projects on a single site. Many of them do not provide the features necessary to support cooperative multi-site software projects or process management. We have developed a tool, called IPPM, which supports these features. IPPM, which integrates features for process and project management, resolves differences between existing project and process tools, and provides a number of unique features to support multi-site development. IPPM has been implemented and used by several development teams working in different regions in Hong Kong and Mainland China.