A case study of effective practices for the management of global software development projects

Global software development has proliferated in recent years because of rapid globalization, development of telecommunication and information technologies, and maturing of the software development processes. This thesis synthesizes available research on the global software development paradigm into an integrated model. The theoretical study analyzes different aspects of dispersion, their effect on traditional group processes of communication, coordination and control, and the recommendations in the literature for addressing some of these issues. The model developed in the theoretical study was then used to perform a detailed case study of a CMM Level 5 software company that specializes in global software development. A comparison of findings from the literature survey with these insights from a practitioner organization was used to draw inferences about how closely the theoretical model follows the real issues faced by industry, the practices and methodologies actually being used, and some areas of concern that available research does not address adequately. This case study revealed overlaps as well as differences between academic research and practice. Recommendations are made to managers of global software projects and areas of future research are identified

EMPIRICAL CHARACTERIZATION OF SOFTWARE QUALITY

The research topic focuses on the characterization of software quality considering the main software elements such as people, process and product. Many attributes (size, language, testing techniques etc.) probably could have an effect on the quality of software. In this thesis we aim to understand the impact of attributes of three P’s (people, product, process) on the quality of software by empirical means. Software quality can be interpreted in many ways, such as customer satisfaction, stability and defects etc. In this thesis we adopt ‘defect density’ as a quality measure. Therefore the research focus on the empirical evidences of the impact of attributes of the three P’s on the software defect density. For this reason empirical research methods (systematic literature reviews, case studies, and interviews) are utilized to collect empirical evidence. Each of this research method helps to extract the empirical evidences of the object under study and for data analysis statistical methods are used. Considering the product attributes, we have studied the size, language, development mode, age, complexity, module structure, module dependency, and module quality and their impact on project quality. Considering the process attributes, we have studied the process maturity and structure, and their impact on the project quality. Considering the people attributes, we have studied the experience and capability, and their impact on the project quality. Moreover, in the process category, we have studied the impact of one testing approach called ‘exploratory testing’ and its impact on the quality of software. Exploratory testing is a widely used software-testing practice and means simultaneous learning, test design, and test execution. We have analyzed the exploratory testing weaknesses, and proposed a hybrid testing approach in an attempt to improve the quality. Concerning the product attributes, we found that there exist a significant difference of quality between open and close source projects, java and C projects, and large and small projects. Very small and defect free modules have impact on the software quality. Different complexity metrics have different impact on the software quality considering the size. Product complexity as defined in Table 53 has partial impact on the software quality. However software age and module dependencies are not factor to characterize the software quality. Concerning the people attributes, we found that platform experience, application experience and language and tool experience have significant impact on the software quality. Regarding the capability we found that programmer capability has partial impact on the software quality where as analyst capability has no impact on the software quality. Concerning process attributes we found that there is no difference of quality between the project developed under CMMI and those that are not developed under CMMI. Regarding the CMMI levels there is difference of software quality particularly between CMMI level 1 and CMMI level 3. Comparing different process types we found that hybrid projects are of better quality than waterfall projects. Process maturity defined by (SEI-CMM) has partial impact on the software quality. Concerning exploratory testing, we found that exploratory testing weaknesses induce the testing technical debt therefore a process is defined in conjunction with the scripted testing in an attempt to reduce the associated technical debt of exploratory testing. The findings are useful for both researchers and practitioners to evaluate their project

Effective Virtual Teams for New Product Development

At present, the existing literature shows that the factors which influence the effectiveness of virtual teams for new product development are still ambiguous. To address this problem, a research design was developed, which includes detailed literature review, preliminary model and field survey. From literature review, the factors which influence the effectiveness of virtual teams are identified and these factors are modified using a field survey. The relationship between knowledge workers (people), process and technology in virtual teams is explored in this study. The results of the study suggest that technology and process are tightly correlated and need to be considered early in virtual teams. The use of software as a service, web solution, report generator and tracking system should be incorporated for effectiveness virtual teams

An Integrated Six-Sigma and CMMI framework for software process improvement

A process improvement framework such as Capability Maturity Model (CMM) can help develop the maturity of a software development organization over time to achieve predictable and repeatable process performance. However, in the absence of a methodology for process performance measurement, ongoing data-oriented process improvement is hard to institutionalize. For organizations following CMMI, this makes navigating their way through higher-level process management and optimization activities called forth in CMMI Level 4 and Level 5 especially challenging. Altogether, this constitutes a major stumbling block for software organizations striving for higher process maturity as Level 4 and Level 5 Process Areas are essential to institutionalizing process improvement in an organization. Six-Sigma introduces tremendous process measurability through its statistical error-control focus and offers compelling tools and techniques that have strong applicability to software development. Six-Sigma focus on data and metrics married with the CMMI coverage of all aspects of software development through its Process Areas can together provide a powerful process control and improvement framework. A CMMI and Six-Sigma hybrid framework has been presented as a means of achieving software development performance and productivity improvements through statistical error control. Such a hybrid CMMI and Six Sigma framework provides not just greater guidance and rigor in certain areas than CMMI alone but also an inherent flexibility by making an extensive toolset available for use in a wide variety of scenarios. This integrated framework demonstrates that CMMI and Six Sigma are highly complementary and are capable of adding greater value when used in conjunction with each other. This is partly because together they address the weaknesses that may become apparent when either framework is used alone. Six Sigma answers the \u27how\u27 for areas where CMMI only provides the \u27what\u27. Conversely, CMMI provides the overall vision and roadmap that is lacking from individual Six Sigma improvements. It is hoped that this will serve as a blueprint for an implementation of CMMI that makes use of relevant Six Sigma tools and techniques

A life cycle for creating an uncomplicated software

Modern software development life cycle models tend to be less formal and less rigid then Waterfall based models of the past. However, creating software without following even the most basic of plans often results in poorly structured, faulty, and hard to maintain software. This paper proposes a practical development model for the purpose for software development. Following some sort of plan produces better code than no plan at all. This model has been shown to be successful even with inexperienced developers

The Applications of Artificial Intelligence in Managing Project Processes and Targets: A Systematic Analysis

Artificial intelligence (AI) has emerged as the defining technology of the 21st century and has far-reaching impacts on project management (PM). This study assesses the applications of AI in managing project processes and targets through a systematic analysis of publications from 2017 to 2021. The analysis has revealed interesting insights, trends, gaps, and issues. This study informs the researchers and practitioners of the status of AI applications in the management of project processes and targets. It helps stimulate research efforts that can lead to more advances in applying AI to augment PM practices