Search results

The purpose of this paper is to examine the ways in which management control is enacted in a product development setting, to provide new insights into the different roles that control can play in this context.

A nine‐month, in‐depth field study was carried out at a subsidiary of an Australasian multinational firm which operates in the consumer foods industry. A participant observation approach was used to collect field notes and documents from the organisation, which were analysed through the lens of ethnomethodology.

The results indicate that the role of management control during product development is mainly focused on reducing uncertainty at each stage and promoting goal congruence at the decision gates. The authors argue that this helps explain why management control has a positive effect in a product development setting.

The implication of this finding is that the role of management control changes during product development due to the involvement of different organisational members (communities of practice) and the activities that they carry out. This helps build a more holistic understanding of control in product development. As this is a field study of a specific company, the findings are not generalizable to other companies or settings. Future research needs to investigate other possible roles which management control may play in this context.

The paper extends the research in this area by showing how and why management control can take on multiple roles in practice.

While the choices available for project management methodologies have increased significantly, questions remain on whether project managers fully consider their alternatives. When project categorization systems and criteria are not logically matched with project objectives, characteristics and environment, this may provide the key reason for why many software projects are reported to fail to deliver on time, budget or do not give value to the client. The purpose of this paper is to identify and categorize critical success factors (CSFs) and develop a contingency fit model contrasting perspectives of traditional plan-based and agile methodologies.

By systematically reviewing the previous literature, a total of 37 CSFs for software development projects are identified from 148 articles, and then categorized into three major CSFs: organizational, team and customer factors. A contingency fit model augments this by highlighting the necessity to match project characteristics and project management methodology to these CSFs.

Within the three major categories of CSFs, individual factors are ranked based on how frequently they have been cited in previous studies, overall as well as across the two main project management methodologies (traditional, agile). Differences in these rankings as well as mixed empirical support suggest that previous research may not have adequately theorized when particular CSFs will affect project success and lend support for the hypothesized contingency model between CSFs, project characteristics and project success criteria.

This research is conceptual and meta-analytic in its focus. A crucial task for future research should be to test the contingency fit model developed using empirical data. There is no broad consensus among researchers and practitioners in categorizing CSFs for software development projects. However, through an extensive search and analysis of the literature on CSFs for software development projects, the research provides greater clarity on the categories of CSFs and how their direct, indirect and moderated effects on project success can be modelled.

This study proposes a contingency fit model and contributes towards developing a theory for assessing the role of CSFs for project success. While future empirical testing of this conceptual model is essential, it provides an initial step for guiding quantitative data collection, specifies detailed empirical analysis for comparative studies, and is likely to improve clarity in debate. Since previous studies have not rigorously assessed the impact of fit between project characteristics, project environment and project management methodology on project success, additional empirically robust studies will help to clarify contradictory findings that have limited theory development for CSFs of software development projects to date.

Previous research for software development projects has frequently not fully incorporated contingency as moderation or contingency as fit (traditional vs agile). This research sets out to develop fully a contingency fit perspective on software development project success, through contrasting traditional plan-driven and agile methodologies. To do this, the paper systematically identifies and ranks 37 CSFs for software projects from 148 journal publications and holistically categorizes them as organizational, team, customer and project factors.

This paper seeks to describe the application of the Agile software development approach to rapidly develop and deploy a variety of innovative IT applications.

The Agile approach is flexible and iterative with continuous feedback and constant communication. It is also marked by frequent and short delivery schedules. An Agile team of staff and students was formed for different projects, and visual tools were used to show process and progress. Team members were also co‐located (situated in the same space), a key element that allowed faster and direct communication. Within the Agile framework, the Crystal Clear methodology was selected, which is based on team size and criticality of the application to develop the workflow and iterative processes.

The Agile approach is particularly suited to innovation development and creative teams for rapid development of products, services, and technology. However, its acceptance is dependent on organizational culture and nature of application.

As a next step, it would be useful to test the Agile approach in an innovative application that is on a larger scale than six team members and with a different level of criticality.

Flexibility and adaptability are needed in managing the development of IT innovations and applications as they vary in size and complexity. The flexible and iterative Agile approach provided the framework to develop and implement these projects despite the small staff size.

There is little in the professional literature on software development and project management approaches for small teams. The Agile approach would be of interest to an IT unit or library with limited staff resources and interested in a lightweight framework to develop and deploy innovative projects.

Presents five case studies of industrial software projects specifically involving prototyping. Designates projects ranging from 240 person‐years to two person‐years involving large industrial corporations to small/medium software manufacturers. Analyses the benefits and limitations of prototyping. Concludes that prototyping is conducive to the quality of the product and the development process, particularly when used in conjunction with an evolutionary development strategy and when all parties are aware of the benefits and limitations.

eLSEwise is the acronym of ESPRIT project 20876 which investigated the Information and Communication Technology (ICT) needs of Large Scale Engineering (LSE) construction over the next 10 years. eLSEwise investigated the business needs related to market and client demands for change in the future delivery processes of LSE construction projects and how the constructors perceive their roles changing in response. It also undertook a state‐of‐the‐art review of the existing and emergent technologies. From these investigations eLSEwise then postulated a vision how LSE construction projects may be delivered in the future, fully utilizing the benefits of emergent technology to satisfy the business needs. The project also considered how companies may progress from their present condition towards this future view, leading to basic development strategy. This paper presents the eLSEwise views of such a future. These findings are presented in three parts: the eLSEwise vision, development routes and recommendations.

The purpose of this paper is to review the content, contributions and subsequent developments of the seminal paper by Barry Boehm, “A spiral model of software development and enhancement” written in 1988. The relationships of this paper to software development, agile projects, real options and present practice are put into perspective.

Basically an essayist approach is taken. First, the contents of Boehm's paper are reviewed and then associated with subsequent developments.

Review of the paper as published represents a documentation of cutting‐edge software development as it existed at the time. Fundamentally it suggests the viability of a non‐linear, customer‐influenced, development approach.

This basic approach illustrated in the spiral model of course has found its way into complex project approaches and management.

This paper follows the lines of increasing attention to classics, which is the purpose of this special issue of the journal. In particular, attention is called to the transition of thought on projects and project management from supplier‐oriented, linear processes to customer/client‐influenced, non‐linear ones.

The purpose of this research is to obtain an updated assessment of the use of standard methods in IS development practice in New Zealand, and to compare these practices to those reported elsewhere.

A web‐based survey of IS development practices in New Zealand organisations with 200 or more full‐time employees was conducted. The results of the survey were compared to prior studies from other national contexts.

The results suggest that levels of standard method use continue to be high in New Zealand organisations, although methods are often used in a pragmatic or ad hoc way. Further, the type of method used maps to a shift from bespoke development to system acquisition or outsourcing. Organisations that reported using standard methods perceived them to be beneficial to IS development in their recent IS projects, and generally disagreed with most of the published limitations of standard methods.

As the intent was to consider only New Zealand organisations, the results of the survey cannot be generalised further afield. More comparative research is needed to establish whether the trends identified here occur at a wider regional or international level.

A significant proportion of organisations anticipated extending their use of standard methods. Growth in packaged software acquisition and outsourced development suggests an increasing need for deployment management as well as development management, possibly reflecting the increased visibility of standard project management methods.

The relevance of traditional standard methods of IS development has been questioned in a changing and more dynamic IS development environment. This study provides an updated assessment of standard method use in New Zealand organisations that will be of interest to researchers and practitioners monitoring IS development and acquisition elsewhere.

This paper examines the managerial skills and role perceptions between the design leader and the client's in‐house professional staff which affect corporate communications. It also examines the consequential factors that influence the time taken to finalise the design for commercial building projects. Whilst all aspects of the design should be discussed to achieve a good product, the time spent on the development of design should not be so long that it affects the overall construction time and the achievement of the client's desired financial objectives. Each specialist in the design team will have something to contribute to the project which may consequently increase the complexity of conventional design development for commercial properties. The research methodology adopted in this study involves in‐depth case studies of two building projects which fundamentally seek to determine the organisational change, leadership and communication factors that influence effective design development of commercial building projects.

The aim of this paper is to make an attempt to find good values of onsite–offshore team strength; number of hours of communication between business users and onsite team and between onsite and offshore team to reduce cost and improve schedule for re-engineering projects in global software development environment.

The system dynamics technique is used for simulation model construction and policy run experimentation. The experts from Indian software outsourcing industry were consulted for model construction, validation and analysis of policy run results in both co-located and distributed software development environment.

The study results show that there is a drop in the overall team productivity in outsourcing environment by considering the offshore options. But the project cost can be reduced by employing the offshore team for coding and testing work only with minimal training for imparting business knowledge. The research results show that there is a potential to save project cost by being flexible in project schedule.

The study found that there could be substantial cost saving for re-engineering projects with a loss of project schedule when an appropriate onsite–offshore combination is used. The quality and productivity drop, however, were rather small for such combinations. The cost savings are high when re-engineering work is sent to offshore location entirely after completion of requirement analysis work at onsite location and providing training to offshore team in business knowledge The research findings show that there is potential to make large cost savings by being flexible in project schedule for re-engineering projects.

The software project manager can use the model results to divide the software team between onsite and offshore location during various phases of software development in distributed environment.

The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in global software development environment.

The fundamental principles of project management governing time, cost and quality should be closely adhered to right from the conceptual design stage in property development to ensure minimal design changes that can have subsequent implications on the overall development of a project. The prognosis of a not so well‐thought out design can be costly once tenders are confirmed. This paper aims to identify the differences in the role perceptions between the client’s project managers and the consultant architects and to determine the major factors that will have a significant influence on the design development time of commercial properties. The study involves a questionnaire survey to determine these factors. The survey findings focus on the size of the design team and client’s in‐house team, communications and decision making in relation to the design development time of completed commercial projects.