scholarly journals The Use of Repeatable Components in Hybrid Models to Enhance Software Project Management Success

2021 ◽  
Vol 12 (3) ◽  
pp. 2058-2063
Author(s):  
Marzanah A. Jabar Et.al
Keyword(s):  
Relevant Information ◽  
Hybrid Models ◽  
Second Order ◽  
Software Project ◽  
Success Rates ◽  
Software Projects ◽  
Agile Methodologies ◽  
Test Models ◽  
Order Components ◽  
Hybrid Management

The management of software project development requires a dynamic and reactive environment to meet shorter time-to-market demands to address competition efficently in the software industry. This scenario requires the use of effective and robust methodologieswhere opportunities are not lost due to delays and failures in timely software project deliveries.The Agile Manifesto in 2001 which introduced 4 values and 12 principles was designed to develop and manage software projects in a more suitable and effective way to improvethe success rates of software projects. But, increase in overall success rates are still not significant with failure rates remaining plauteaued at about 30% over the last 10 years.  Hybrids methodologies seem to have worked better as agile hybrid management methodshave shown more promise when compared to pure agile methods with an overall success rate increase of 16%. There is evidence too that by combining agile methodologies with traditional methodologies, there would be a further increase in success rates. Whilst many hybrid methodologies have been suggested and researched, the gaps in the literature review reveal there is a lack of hybrid models that have been empirically developed and studied as second order components. To build a robust hybrid model, it is important to gather the relevant information and careful consuideration must be given to the design of the questionnaireto fit second order components and models must incorporate and provide for the use repeatable ways to test models once the data is collected.This paper presents a review of the current gaps in hybrid methodologies and proposes a questionnaire design that supports the research methodology and empirical study to be undertaken with second order components (Constructs).Further it looks at the design approach in questionnaires which incorporates the use of repeatable constructs and the measures used and emphasizes this as an important ingredient for developing and testing hybrid models in research studies.

eXtreme Programming, Agile Methodologies, Software Project Management, Customer Role, Rigorous Testing

2022 ◽  
pp. 163-182
Author(s):  
Kamalendu Pal
Keyword(s):  
Project Management ◽  
Software Development ◽  
Extreme Programming ◽  
Acceptance Testing ◽  
Software Project ◽  
Software Project Management ◽  
Software Projects ◽  
Agile Methodologies ◽  
Rigorous Testing ◽  
Software Development Methodologies

Agile software development methodologies are attracting attention from academics and practitioners for planning and managing software projects. The eXtreme Programming (XP) challenges conformist wisdom regarding software system development processes and practices as agile methodologies. To work efficiently in the current software development practice, characterized by requirements fuzziness, XP moves away from document-centric operations into people-centric management. In the XP-based software project, the customers play an essential role, having multiple responsibilities such as driving the project, gathering requirements (‘user stories'), and exercising quality control (or acceptance testing). Besides, the customers must liaise with external project stakeholders (e.g., funding authorities, end-users) while maintaining the development team's trust and the wider business. The success of such software project management practices relies on the quality result of each stage of development obtained through rigorous testing. This chapter describes three characteristics of XP project management: customer role, software testing feedback, and learning.

scholarly journals The Effects of Agile Methodologies on Software Project Management in Pakistani Software Companies

2021 ◽  
Vol 12 (3) ◽  
pp. 1717-1727
Author(s):  
Javed Iqbal Et.al
Keyword(s):  
Project Management ◽  
Software Development ◽  
Extreme Programming ◽  
Software Project ◽  
Software Project Management ◽  
Software Projects ◽  
Software Companies ◽  
Agile Methodologies ◽  
Management Factors ◽  
Main Determinants

Agile methodologies are always tends to increase the quality of software and also handling the complex software projects. However, the software companies in Pakistan have recently felt the disparity of producing successful software. In this context, an extensive survey has been conducted in 52 prominent software development companies of Pakistan to identify this remedy and the motivation behind this production discrepancy. It is revealed from the survey that there is a lack of empirical evidence in the relationship of agile methodologies with the effective and progressive management of software project management factors including, schedule, scope, risk, budget, quality and resources. Therefore, the proposed study delivers an extensive statistical comparison to determine the effectiveness of agile methodologies in terms of their effects on the project management factors. The results suggest that in general all agile methodologies play a significant role towards the successful software development in the software company. However, Extreme Programming, Scrum, Kanban and Agile modeling are the main determinants of production disparity among software companies. Furthermore, it is determined that the quality factor has a positive correlation with the rest of the factors. It is also found that the budget factor has significantly correlated with other five factors, while rest of the factors has insignificant correlation. We have also compared agile methodologies in terms of project management factors, which specify that each agile methodology has its own importance and effect with respect to managing different factors of project management.

Insights on Cost Estimation Methods and its Uses in Software Project Design

2020 ◽  
pp. 166-169
Author(s):  
Aravindhan K
Keyword(s):  
Project Management ◽  
Cost Estimation ◽  
Estimation Methods ◽  
Software Project ◽  
Estimation Model ◽  
Software Projects ◽  
Software Applications ◽  
Software Companies ◽  
Cost Estimation Model ◽  
The Cost

Cost estimation of software projects is risky task in project management field. It is a process of predicting the cost and effort required to develop a software applications. Several cost estimation models have been proposed over the last thirty to forty years. Many software companies track and analyse the current project by measuring the planed cost and estimate the accuracy. If the estimation is not proper then it leads to the failure of the project. One of the challenging tasks in project management is how to evaluate the different cost estimation and selecting the proper model for the current project. This paper summarizes the different cost estimation model and its techniques. It also provides the proper model selection for the different types of the projects.

scholarly journals Software Project Management Systems Using Kanban Method in the CV. Primavisi Globalindo

2020 ◽  
Vol 4 (2) ◽  
pp. 215-231
Author(s):  
Muhammad Aliyya Ilmi ◽  
Fajar Pradana ◽  
Widhy Hayuhardhika Nugraha Putra
Keyword(s):  
Project Management ◽  
Project Planning ◽  
Software Project ◽  
Unit Testing ◽  
Functional Requirements ◽  
Software Projects ◽  
Management Planning ◽  
Scheduling System ◽  
Usability Test ◽  
Project Management And Scheduling

Reducing the risk of failure in working on software projects is one of the successes for the company. It can be done by implementing project planning management properly. One important aspect of project management planning is scheduling. Scheduling includes recording human resources and tasks in the project. The Kanban method is one of the methods used to overcome problems in controlling project schedules. This study aims to develop a project scheduling system that applies the Kanban method. In this research, project management and scheduling system will be developed using the Kanban method. This system expected to be able to assist companies in handling projects. Kanban was chosen because it can easily respond to project changes, easily implemented, and company needs. In this study, unit testing was performed on the system's three main features and tested the validity of the system's 49 functional requirements. The usability test produces a value of 76. Based on the validation and usability test results, it can be concluded that the system is included in the acceptable category.

scholarly journals ANALISIS MANAJEMEN PROYEK PERANGKAT LUNAK SISTEM INFORMASI AKUNTANSI PADA BIRO SISTEM INFORMASI PT. X

2014 ◽  
Vol 9 (2) ◽  
pp. 101
Author(s):  
Alusyanti Primawati ◽  
Dewi Mustari
Keyword(s):  
Information System ◽  
Project Management ◽  
Information Systems ◽  
Management Information Systems ◽  
Software Project ◽  
Management Information ◽  
Software Projects ◽  
Accounting Information System ◽  
Management Actions ◽  
Application Systems

The software is an intermediary between system hardware computer with user as human. Based on the emerging software projects because of the importance of the functions already affects many functions in various aspects. Software projects that have become this need ultimately require management actions to manage the process in the project. Project management is necessary for the success of the project. Bereau Information System PT. X is one part of a company that provides software for functional PT. X. Analysis results from the concept of software project management information systems Bureau at PT. X when the process of designing application systems information accounting PT. X aims to answer how concept of project management Information Systems Bureau in designing the Accounting Information System applications. The methods used in this research is the study of the library with a general empirical approach based on experience and theories related to project management especially in software projects. The conclusions obtained that the activity of the management software on System Information Bureau is in compliance with the application of existing theory, but science is constantly evolving so as to do the development management activities after conducting evaluation regularly for the maintenance of long-term software project.

scholarly journals Impact of Risk Determinants on the Perceived Performance of Software Projects in Emerging Economies

2020 ◽  
Vol V (IV) ◽  
pp. 48-59
Author(s):  
Ashfaq Ahmad ◽  
Nisar Ahmad ◽  
Nadia Malik
Keyword(s):  
Risk Factors ◽  
Software Industry ◽  
Effective Control ◽  
Software Project ◽  
Software Projects ◽  
Perceived Performance ◽  
Project Risks ◽  
Risk Determinants ◽  
The Impact ◽  
Industry Risk

Effective control of risk factors ensures the performance of projects in any industry. Risk factors can influence software projects of any size and type. This research aims to identify and examine different risk factors associated with projects in the software industry. The relationship between Software Project Risks (SPRs) and Perceived Project Performance (PPP) measures is determined. This study is based on a survey approach, and a questionnaire is used to record opinions and responses from 199 software professionals working in the Pakistan software industry. The results showed that the association between SPRs and PPP measures is statistically significant, and there exist a positive relationship. It is concluded that an increase in understanding of SPRs can increase PPP measures used to evaluate the software project. The results will help researchers and professionals in understanding the impact of different risk factors on software projects' perceived performance.

scholarly journals Curating GitHub for engineered software projects

2016 ◽  
Author(s):  
Nuthan Munaiah ◽  
Steven Kroh ◽  
Craig Cabrey ◽  
Meiyappan Nagappan
Keyword(s):  
Software Engineering ◽  
High Precision ◽  
Ground Truth ◽  
Software Project ◽  
Software Projects ◽  
Data Set ◽  
High Recall ◽  
Home Work ◽  
Reference Implementation ◽  
Engineering Practices

Software forges like GitHub host millions of repositories. Software engineering researchers have been able to take advantage of such a large corpora of potential study subjects with the help of tools like GHTorrent and Boa. However, the simplicity in querying comes with a caveat: there are limited means of separating the signal (e.g. repositories containing engineered software projects) from the noise (e.g. repositories containing home work assignments). The proportion of noise in a random sample of repositories could skew the study and may lead to researchers reaching unrealistic, potentially inaccurate, conclusions. We argue that it is imperative to have the ability to sieve out the noise in such large repository forges. We propose a framework, and present a reference implementation of the framework as a tool called reaper, to enable researchers to select GitHub repositories that contain evidence of an engineered software project. We identify software engineering practices (called dimensions) and propose means for validating their existence in a GitHub repository. We used reaper to measure the dimensions of 1,994,977 GitHub repositories. We then used the data set train classifiers capable of predicting if a given GitHub repository contains an engineered software project. The performance of the classifiers was evaluated using a set of 200 repositories with known ground truth classification. We also compared the performance of the classifiers to other approaches to classification (e.g. number of GitHub Stargazers) and found our classifiers to outperform existing approaches. We found stargazers-based classifier to exhibit high precision (96%) but an inversely proportional recall (27%). On the other hand, our best classifier exhibited a high precision (82%) and a high recall (83%). The stargazer-based criteria offers precision but fails to recall a significant potion of the population.

Toward Agile Interactive Software Development Process Models for Crowd Source Projects

2014 ◽  
pp. 117-131
Author(s):  
Izzat Alsmadi ◽  
Saqib Saeed
Keyword(s):  
Software Development ◽  
Process Models ◽  
Agile Development ◽  
Software Project ◽  
Interactive Software ◽  
Crowd Sourcing ◽  
Software Projects ◽  
The Public ◽  
Development Models ◽  
High Level

Typical traditional software development models are initially designed for company-style software project teams. They also assume a typical software project that has somewhat clear goals, scope, budget, and plan. Even Agile development models that are very flexible in considering previous project parameters assume somewhat stable team and project structures. However, in recent years, the authors have noticed expansion in software projects that are developed in a very illusive flexible team, scope, budget, and plan structures. Examples of such projects are those projects offered in open competition (also called crowd sourcing) structure for software developers to be part of. In typical open competition projects, initial, high level project ideas are submitted to the public through the Internet. The project initiators give their initial requirements, constraints, and conditions for successful products or submissions. Teams can be organized before or through the competition. Submission and evaluation of deliverables from teams are subjected to project initiator evaluation along with evaluation teams organized through the open competition host. This chapter investigates all traditional project characteristics. The authors elaborate on all those elements that should be modified to fit the open competition agile structure. They use several case studies to demonstrate management issues related to managing software projects in open competitions.

Simple System Dynamics and Control System Project Models

2014 ◽  
pp. 113-133
Author(s):  
A. S. White
Keyword(s):  
Control System ◽  
Software Project ◽  
Software Projects ◽  
Initial State ◽  
Control Models ◽  
Non Linear ◽  
Dynamics And Control ◽  
Control System Model ◽  
System Project ◽  
And Control

This chapter examines the established Systems Dynamics (SD) methods applied to software projects in order to simplify them. These methods are highly non-linear and contain large numbers of variables and built-in decisions. A SIMULINK version of an SD model is used here and conclusions are made with respect to the initial main controlling factors, compared to a NASA project. Control System methods are used to evaluate the critical features of the SD models. The eigenvalues of the linearised system indicate that the important factors are the hiring delay time, the assimilation time, and the employment time. This illustrates how the initial state of the system is at best neutrally stable with control only being achieved with complex non-linear decisions. The purpose is to compare the simplest SD and control models available required for “good” simulation of project behaviour with the Abdel-Hamid software project model. These models give clues to the decision structures that are necessary for good agreement with reality. The final simplified model, with five states, is a good match for the prime states of the Abdel-Hamid model, the NASA data, and compares favourably to the Ruiz model. The linear control system model has a much simpler structure, with the same limitations. Both the simple SD and control models are more suited to preliminary estimates of project performance.

Sign in / Sign up

Export Citation Format

Share Document