Search results

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.

To provide a primer on the major project management protocols and examples of how these protocols have been used to manage library projects.

The chapter presents a broad review of the literature on project management in general, and as it has been applied in library settings, including brief histories of each major methodology, its development, component elements, and examples of its use in libraries.

Many of the major project management protocols, such as Six Sigma, Agile, Lean, Scrum, and Waterfall, have been used successfully in library settings across a broad range of areas and project types.

As libraries continue to innovate and expand their services, the management of complex projects and processes has become commonplace. This chapter will serve as a primer on the major project management protocols, highlighting the ways in which they can be used in libraries, and to which types of library projects they have been successfully applied.

This research aims to examine the challenges of recruiting participatory action research (PAR) in managing innovation projects. An enhanced methodology based on PAR was developed to mitigate the challenges related to recruiting PAR in managing innovation projects. The proposed methodology was evaluated by comparing it to established methodologies/frameworks such as Scrum, Design Thinking (DT) and The Lean Startup (TLS). The evaluation aimed to determine the advantages and limitations of the proposed methodology in managing innovation projects.

The proposed enhanced methodology consists of eight steps, ranging from developing an understanding of the industry and business structure to learning and knowledge management. In addition, the enhanced methodology uses other techniques, such as Force field analysis and 12 boundary questions.

The research findings indicate that using the proposed methodology can improve the formalization of collaboration in PAR, enabling the organization to respond better to market changes. It helps define the project scope more clearly, encouraging innovation, addressing communication barriers and considering different worldviews and practical issues. Based on the findings, the proposed enhanced methodology could complement other methodologies/frameworks such as Scrum, DT and TLS.

The current research adds to the existing literature by identifying the challenges of recruiting PAR in managing innovation projects. A deductive reasoning process was utilized because there is no comprehensive research concerning the challenges of recruiting PAR in managing innovation projects. On the other hand, the PAR 4-phase cycle has been reviewed and enhanced to manage innovation projects.

The proposed methodology was used in a new product development project. The case study was done on one of the payment service provider companies that design, develop and deploy a digital product for marketing, installation, repair and maintenance of electronic funds transfer at point of sale devices.

No research has yet sought to identify the challenges of using PAR in innovation project management (IPM). Identifying the challenges associated with applying PAR in the IPM and providing an enhanced methodology to mitigate the challenges could fill a gap in IPM studies.

The literature on software project management is extended into the broader domain of large‐scale IS management by studying enterprise‐wide system upgrade projects. In particular; examines the role that the intervention of project management practices (formal project methodologies and outsourcing) play in large and/or complex IS projects, which result in good project performance.

A survey instrument was completed by 449 information systems managers about a specific upgrade project. The primary analytical approach used was structural equation modeling (SEM).

It was found that neither project complexity nor project size are good indicators of meeting a project's target date. Large projects that adopted formal project management practices were more probable to meet the project target date. Projects with a high degree of complexity which involved outsourcing and adopted formal project management practices, were more likely to meet the project target date.

Clearly, the message to managers of IS projects is to establish a project methodology, especially in large, enterprise‐wide projects, and when some degree of outsourcing is required.

Future research should consider additional measures of performance such as cost, end‐user satisfaction and business value.

Much had been written in the literature about how large, complex IT projects have high failure rates. Our study provides conclusive evidence that, the greater the degree of methodology implementation, the greater the chance for meeting the project's target date. Prior to this research, this had not been explicitly shown in the research literature.

Organizational culture has an impact on various activities in organizations, including project management (PM). The aim of the study is to answer the following research questions: RQ1: what significance is attributed to organizational culture compared to the objective project characteristics when choosing the dominant PM methodology in organizations? RQ2: which type of organizational culture is preferred for successful implementation of different PM methodologies? RQ3: what kind (if any) of relationship exists between the dominant type of organizational culture in organizations and the dominant PM methodology?

The author surveyed 100 project managers working in the financial industry in Poland with the use of personal structured interviews. The competing values framework (CVF) concept authored by Cameron and Quinn was used.

Project managers find organizational culture more important than objective project characteristics when choosing the dominant PM methodology in an organization. Although statistical analysis revealed a significant relationship between the preferred type of organizational culture and PM methodology, there is no significant relationship between the existing type of organizational culture and the PM methodology which prevails in the company.

Future research should investigate other industries and other typologies of organizational culture.

The paper provides recommendations for management practice on how to shape organizational culture in the context of successful PM with the application of different PM methodologies.

This study fills a gap in the theory of PM by identifying and empirically verifying the theoretical linkage between the type of organizational culture and PM methodology.

Aligning the project management methodology (PMM) to a particular project is considered to be essential for project success. Many outsourced software projects fail to deliver on time, budget or do not give value to the client due to inappropriate choice of a PMM. Despite the increasing range of available choices, project managers frequently fail to seriously consider their alternatives. They tend to narrowly tailor project categorization systems and categorization criterion is often not logically linked with project objectives. The purpose of this paper is to develop and test a contingency fit model comparing the differences between critical success factors (CSFs) for outsourced software development projects in the current context of traditional plan-based and agile methodologies.

A theoretical model and 54 hypotheses were developed from a literature review. An online Qualtrics survey was used to collect data to test the proposed model. The survey was administered to a large sample of senior software project managers and practitioners who were involved in international outsourced software development projects across the globe with 984 valid responses.

Results indicate that various CSFs differ significantly across agile and traditional plan-based methodologies, and in different ways for various project success measures.

This study is cross-sectional in nature and data for all variables were obtained from the same sources, meaning that common method bias remains a potential threat. Further refinement of the instrument using different sources of data for variables and future replication using longitudinal approach is highly recommended.

Practical implications of these results suggest project managers should tailor PMMs according to various organizational, team, customer and project factors to reduce project failure rates.

Unlike previous studies this paper develops and empirically validates a contingency fit model comparing the differences between CSFs for outsourced software development projects in the context of PMMs.

The objective of this paper is to provide a description of the model for standardized project management developed by the Project Management Institute (PMI), as applied to digital library projects.

Using the PMI model for project management, the paper develops a context for managing digital library projects according to the PMI's standard methodology.

The paper finds that by using a standard methodology increases the likelihood of delivering projects on time and on budget.

This paper will be of interest to digital library project managers as it fills a gap in the literature by providing an accessible overview of the major components of standard project management methodology as defined by the PMI.

The purpose of this conceptual chapter is to highlight the disadvantages of project management to help the reader put project management work in context.

Different project management methodologies such as waterfall project management, Agile project management, Six Sigma, and Kanban are discussed in terms of overall problems and then specific problems with each methodology. Managing multiple projects and the problems with program and portfolio management are discussed.

The findings are that most formalized project management methods are ill-suited to most library-related situations. However, some aspects of project management are well suited to any project, at any size, and those are discussed.

The value of this paper is that readers will get a strong understanding of project management methodologies in context and a clear idea of the strengths and weaknesses of each.

The purpose of this paper is to qualitatively validate the constructs of a theoretically derived research model while gaining insights to steer the direction of a greater study on methodologies, their elements, and their impact on project success. In doing so, to investigate whether different project environments, notably project governance, impacts the relationship between methodologies and project success.

A deductive approach was applied to validate a theoretically derived research model. In total, 19 interviews across 11 industrial sectors and four countries were used to collect data. Pattern-matching techniques were utilized in the analysis to deductively validate the research model.

There is a positive relationship between project methodology elements and the characteristics of project success; however, environmental factors, notably project governance, influence the use and effectiveness of a project methodology and its elements with a resulting impact on the characteristics of project success.

Project governance plays a major role in the moderating effect of a project methodology’s effectiveness. Contingency theory is applicable to a project’s methodology’s selection and its customization according to the project environment.

Understand the impact of project methodologies and their elements on the characteristics of project success while being moderated by the project environment, for example, the risk of suboptimal project performance due to the effectiveness of methodology elements being negatively impacted by the project environment.

The impact of a project methodology (collection of heterogeneous-related elements) on the characteristics of project success is identified while being moderated by the project environment, notably project governance.

The paper aims to provide methodological support for hybrid project management, in which the discipline of predictive methodologies combines with the flexibility of adaptive ones. Specifically, the paper explores the extent complexity and volatility dimensions of organisational problems inform choices of PM methodologies both theoretically and in current practice, as a first step towards better methodological support for hybridisation.

The paper takes a mixed method approach, including both secondary research and primary research with practitioners. Primary research consists of a small scale survey (n = 31) followed by semi-structured interviews, with findings triangulated against secondary evidence.

The paper provides empirical insights on how complexity and volatility of organisational problems can inform hybrid project management practices. Specifically, it suggests a mapping between volatility and complexity dimensions and predictive and adaptive risk controls as a first step towards the systematisation of hybrid combinations in projects.

Due to the small participant sample, the research results may lack generalisability.

The paper includes implications for the development of methodological support for setting up hybrid projects in practice.

The paper addresses a gap acknowledged both in the literature and by practitioners.