Search results

The aim of this paper is to present the results from an empirical investigation of Six Sigma in the Indian software industry

The paper begins with a review of literature of Six Sigma and its role in the software industry. The importance of Six Sigma in the software domain is presented, followed by presentation of the results from an empirical investigation of Six Sigma in the Indian software industry

The research reflects the status of Six Sigma application and implementation in the software industry, identifies the commonly used statistical and non statistical and software engineering tools and frameworks used within software business; and determines the critical success factors (CSFs) for a successful Six Sigma initiative in the software/IT industry. The most important factor was management commitment and involvement. Documentation management and suppliers' involvement were found to be the least important factors.

This study was carried out with some boundaries like the number of companies, available resources, time constraints, etc.

This paper dispels the myths concerning the unsuitability of Six Sigma in the software arena. At the same time it highlights the status of Six Sigma implementation in Indian software organizations and the critical success factors for implementation of Six Sigma.

Little research has been carried out in terms of empirical survey relating to the application of Six Sigma in the software industry like that demonstrated in this paper. The paper will be valuable for quality professionals and management personnel in software organizations.

This paper aims to investigate the relationship of software company culture and core values and project management methodologies on the demand for corporate real estate (CRE), impacting decisions regarding location, square footage, office design and amenities.

A researcher-administered survey was designed with the assistance of a purposive sample of brokers, architects and interior designers to elicit responses from the CRE officers in software companies at four stages of growth, from small, entrepreneurial startups to large, publicly traded software companies, located in the same metropolitan area of the USA. Quantitative responses are summarized with traditional statistics and data visualizations. Linguistic analysis, including sentiment analysis and keyword relevance, was performed on the unstructured, English text responses.

Differences exist in the office layouts, amenities and locations across the four software company size categories studied. Linguistic analysis of company descriptions of office design, culture and core values, and the relationship between the two, provide another way for brokers, investors and other stakeholders to understand company perspectives and communication idioms related to CRE needs. The research was unable to show any differences in any dependent variable based on software project management methodologies due to sampling limitations.

This study is limited by the sample size of the participating software companies based on access to company leadership. Results are not generalizable.

Architects, investors, brokers and lenders may find value in using this study’s approach to better understand the needs of software technology clients. Specifically, stakeholders may find value in examining the linkage from software company size, culture and core values to CRE office layout, amenities and location.

The qualitative findings suggest that software company culture and core values and company size influence the design of the CRE demanded by software companies. Multivariate data visualization was designed to communicate longitudinal CRE data. Linguistic analysis was used to extract the emotional content and relevance scores from company descriptions of office design, company culture and core values and the reported effect of culture and core values on office design. Findings may be beneficial for stakeholders involved in the design, location and future CRE investments, and they suggest the need for future research on a larger sample.

At the authors’ libraries, they consolidated two departments and attempted to find ways to increase productivity, reduce duplication and improve job happiness within their software development teams. The authors have lost institutional knowledge when developers leave the team, yet the authors remain responsible for critical library services. The merging of the authors’ departments provided the opportunity to rethink how their teams are structured and whether a different model could provide better professional development, more knowledge sharing and better stability of their services. This article presents a case study of moving from a project-centric approach to a platform-based model.

The authors met with those responsible for establishing priorities for their services and developers to assess successful and unsuccessful implementations and pivoted based on those assessments.

The authors found that their developers were happier to increase their portfolios and professional development, and the librarians were satisfied with more stable services during a particularly unstable time within the authors’ institution.

This is a practical example of a positive way to structure development teams in libraries. Frequently, teams support a single service to the library because of the criticality of that service on a day-to-day basis, but that can create a lack of shared knowledge during institutional instability. This study reveals the benefits of a platform-based approach, including increased developer happiness, reduced disruptions due to staff turnover and improved system stability. It also discusses the challenges of managing product owners' expectations and balancing feature development with maintenance work.

The purpose of this study is to analyze the interaction between the enablers and barriers to successful project control system (PCS) implementation in petroleum and chemical projects and to provide a knowledge-based foundation for the evaluation of the dominant factors of PCS success.

An integrated approach of interpretive structural modeling (ISM) and cross-impact matrix multiplication applied to classification (Matrice d’Impacts Croisés Multiplication Appliquée à un Classement) were used. An expert group of industry professionals and academics was consulted at the initial stage as an input for the ISM methodology to explore the contextual relationships among the critical factors to PCS implementation in petroleum and chemical projects.

This study identifies three dominants enablers of PCS success: the technical skills of the project controller; explicitly defined roles of project team members; and an accurate work breakdown structure. Additionally, six dominant barriers to successful PCS implementation have been identified: lack of standard processes, vague contract deliverables, unclear project goals, unclear project milestones, disparate control system between owner and contractor and lack of information communication. Organizations in the petroleum and chemical sectors should put more effort into the development of these factors to optimize the implementation of PCS.

A limitation of this current study is its focus on the petroleum and chemical sectors in Saudi Arabia. It is expected that the findings will have wider applicability, but further studies in different sectors and geographic regions should be undertaken to validate this assumption. In this study, a second validation expert group was used to ensure the reliability of the results as much as was possible. However, further studies could be completed to evaluate alternate classification schemes and to test the robustness of the expert consensus and techniques reported, in this study, including an increased number of experts.

The present study makes some practical contributions to the project delivery process. It provides different project stakeholders with a better understanding of the factors that improve PCS outcomes and helps project owners and contractors to evaluate the PCS used by both parties to understand how they might be aligned for successful project execution.

The successful implementation of PCS is a key contributor to the total project delivery process. Although there is growing attention on PCS as a critical project management tool in petroleum and chemical projects, the literature in project management shows that PCS implementation has not been taken up as much as originally anticipated. This paper will address this gap by focusing on improving the take-up of strategical PCS implementation through the identification of six dominant enablers and nine dominant barriers as driver factors of success.

The aim of this paper is to present the key areas of activity to be used for drafting service level agreements (SLAs) for electronic services and, at the same time, to present best practices and problems that arise from the application of this discipline.

A range of recently published (2000‐2005) works has been reviewed, in order to: a) analyse how an SLA has to be defined and applied b) identify the applicable best practices and c) identify the problem areas.

Provides guidance for the business and the Application Service Provider (ASP) when they want to engage in an outsourcing agreement by presenting best practices and problems that occur from the application of SLAs.

Suggests further research is needed in a number of research areas such as: development of semantic models for SLAs, development of flexible pricing models in relation with SLAs, definition of SLAs in cases of dynamic service creation, etc.

A useful source of information both for academia and the business.

Provides practical insight on a specialized topic and guidance to researchers.

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.

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 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.

The purpose of this paper is to illustrate how knowledge takes effect in different software development methodologies by relating them to different knowledge cycles.

The results were find by conducing a general review about the topics of knowledge cycles and software development methodologies.

All software development methodologies have knowledge cycles. In Waterfall methodology, the cycle followed is I-Space. For “code and fix,” there is a parallel with March’s cycle. Scrum shows a parallel with SECI cycle. Among the methodological options, results show there an increase in hierarchy, documentation, processes and explicit knowledge.

Identified parallels of each methodology with knowledge cycles; established which Scrum artifacts are performed at each stage of SECI, which Waterfall steps correspond to I-Space phases and which activities in “code and fix” deal with exploration and exploitation of knowledge; and features shown increase or decrease according to the adoption of each methodology.

Results help knowledge sharing implementations and foster inter-team knowledge sharing, with the identification of the correct methodology-cycle match and the personalization of the strategy for each team based on the adopted methodology. Training for knowledge initiatives can be improved by determining how knowledge-sharing activities are incorporated on the determined series of actions established by the methodologies adopted on the firm.

The identification of how knowledge is generated and shared among teams in each methodology, the optimum pairing of the methodology and the parallels with the other, and the differences that emerge from the adopted knowledge cycle show that software projects are embedded in a knowledge cycle.

A cost estimate is considered to have a high impact on software project success. Because of this, different methodologies for creating an accurate estimate have been studied over decades. Many methodologies produce accurate results, when used properly. However, software projects still suffer from inaccurate estimates. The disparity may result from organisational hindrances. This paper focuses on top management support (TMS) for software cost estimation (SCE). The purpose of this paper is to identify current practices and attitudes of top management involvement in SCE, and to analyse the relationship between these two and project success.

A list of 16 TMS practices for SCE has been developed. A survey was conducted to capture the frequency of use and the experienced importance of support practices. Data has been collected from 114 software professionals in Finland. Correlations between the frequency of use, attitudes and project success were analysed.

Top management invests a significant amount of attention in SCE. The extent of use and experienced importance do not correlate strongly with each other or project success.

The results may lack generalisability. Researchers are encouraged to validate the results with further studies.

Software professionals invite senior managers to participate in SCE. A list of practices for participating is provided.

This paper suggests a list of 16 TMS practices for SCE. The paper also reports on the extent of use and experienced importance of practices, and the correlations between these two and project success.