scholarly journals An Efficient Framework for Cost and Effort Estimation of Scrum Projects

2021 ◽  
Vol 9 (11) ◽  
pp. 1478-1487
Author(s):  
Chitrak Vimalbhai Dave
Keyword(s):  
Software Development ◽  
Cost Estimation ◽  
Process Models ◽  
Agile Development ◽  
Software Systems ◽  
Effort Estimation ◽  
Related Factors ◽  
Inappropriate Use ◽  
Development Methodology ◽  
Soft Computing Techniques

Abstract: Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index. Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms ofestimation. Keywords: Cost Estimation, Effort Estimation, Scrum, Machine Learning, Agile Software Development

An efficient effort and cost estimation framework for Scrum Based Projects

2018 ◽  
Vol 7 (4.12) ◽  
pp. 52
Author(s):  
Mohit Arora ◽  
Dr. Sahil Verma ◽  
Dr. Kavita
Keyword(s):  
Cost Estimation ◽  
Process Models ◽  
Agile Development ◽  
Software Systems ◽  
Effort Estimation ◽  
Related Factors ◽  
Inappropriate Use ◽  
Business Units ◽  
Development Methodology ◽  
Soft Computing Techniques

Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index.  Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms of estimation. 

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.

scholarly journals Quality of agile adoption in global software development: An assessment model

2021 ◽  
Vol 21 (1) ◽  
pp. 367
Author(s):  
Mahnaz Afshari ◽  
Taghi Javdani Gandomani
Keyword(s):  
Software Development ◽  
Assessment Model ◽  
Global Software Development ◽  
Agile Development ◽  
Related Factors ◽  
Face To Face ◽  
Human Power ◽  
Software Teams ◽  
Research Gap

<span>Over the last decade, software development has faced two approaches to Agile and global software development (GSD). While Agile development is focused on the reduction of software development overhead by reducing the distance between individuals and face-to-face communications, in global software development, the use of human power in various sites is considered. Despite their inherent differences, the combination of these two approaches has received considerable attention from researchers and software professionals. Meanwhile, the lack of a model or tool capable of assessing teams' adaptation to Agile methods seems to be a research gap. The current research aims to solve this challenge by proposing a model in this regard. Considering the major related factors and weighting them, this model allows software teams to assess the rate of their adaptation and success in global software development.</span>

On the Rim Between Business Processes and Software Systems

2019 ◽  
pp. 170-196 ◽  
Author(s):  
Maria Estrela Ferreira da Cruz ◽  
Ricardo J. Machado ◽  
Maribel Yasmina Santos
Keyword(s):  
Software Development ◽  
Business Process ◽  
Process Model ◽  
Process Management ◽  
Business Processes ◽  
Process Models ◽  
Software Systems ◽  
Business Process Model ◽  
Constant Change ◽  
Development Processes

The constant change and rising complexity of organizations, mainly due to the transforming nature of their business processes, has driven the increase of interest in business process management by organizations. It is recognized that knowing business processes can help to ensure that the software under development will meet the business needs. Some of software development processes (like unified process) already refer to business process modeling as a first effort in the software development process. A business process model usually is created under the supervision, clarification, approval, and validation of the business stakeholders. Thus, a business process model is a proper representation of the reality (as is or to be), having lots of useful information that can be used in the development of the software system that will support the business. The chapter uses the information existing in business process models to derive software models specially focused in generating a data model.

Software Process Paradigms and Crowdsourced Software Development

Crowdsourcing ◽  
2019 ◽  
pp. 1551-1568
Author(s):  
Nitasha Hasteer ◽  
Abhay Bansal ◽  
B. K. Murthy
Keyword(s):  
Software Development ◽  
Development Strategy ◽  
Software Process ◽  
Process Models ◽  
Development Methodology ◽  
Develop Software ◽  
The Common ◽  
Traditional Process ◽  
Use Of Social Media ◽  
The Right

Production of quality software requires selecting the right development strategy. The process and development strategies for creating software have evolved over the years to cope with the changing paradigms. Cloud computing models have made provisioning of the computing capabilities and access to configurable pooled resources as convenient as having access to the common utilities. With the recent advancements in the use of social media and advent of software development through crowdsourcing, the need to comprehend and analyze the traditional process models of software development, with regard to the changed paradigm have become ever more necessary. The changes in the way software are being created and the continuous evolution in the processes of development and deployment has created a need to understand the development process models. This chapter provides an insight on the transition from the conventional process models of software development to the software development methodology being used to develop software through crowdsourcing.

Governance of Software Development

2009 ◽  
pp. 266-284 ◽  
Author(s):  
Yael Dubinsky ◽  
Avi Yaeli ◽  
Yishai Feldman ◽  
Emmanuel Zarpas ◽  
Gil Nechushtai
Keyword(s):  
Software Development ◽  
Conceptual Model ◽  
It Governance ◽  
Agile Development ◽  
Decision Rights ◽  
Development Methodology ◽  
Governance Model ◽  
Large Software ◽  
Laws And Policies

Governance is the exercise of control and direction over a subject such as a society, an organization, processes, or artifacts, by using laws and policies that are defined, deployed, and executed. In this chapter we develop this definition into a formal conceptual model that can be applied to a variety of governance domains. At the heart of this model lies the concept of the governance solution and its lifecycle. The governance solution embodies the set of mechanisms—decision rights, policies, controls, and measurements—applied to a governance scope in order to achieve some governance goals. As part of the lifecycle, the effectiveness of the governance solution is measured, and corrections and alignments are made as necessary. We demonstrate how this model can be applied to multiple governance domains by providing examples from IT governance as well as software-development governance. We conclude by providing a detailed scenario in the software-development governance space, which looks at large software organizations undergoing transition to agile development methodology. We further demonstrate how the governance model is instantiated and evolved in the context of this scenario.

Handling of Software Quality Defects in Agile Software Development

2011 ◽  
pp. 90-113 ◽  
Author(s):  
J. Rech
Keyword(s):  
Software Development ◽  
Software Quality ◽  
Software Maintenance ◽  
Agile Software Development ◽  
Agile Development ◽  
Software Systems ◽  
Software System ◽  
History Of ◽  
Effective Development ◽  
Agile Software

Software quality assurance is concerned with the efficient and effective development of large, reliable, and high-quality software systems. In agile software development and maintenance, refactoring is an important phase for the continuous improvement of a software system by removing quality defects like code smells. As time is a crucial factor in agile development, not all quality defects can be removed in one refactoring phase (especially in one iteration). Documentation of quality defects that are found during automated or manual discovery activities (e.g., pair programming) is necessary to avoid wasting time by rediscovering them in later phases. Unfortunately, the documentation and handling of existing quality defects and refactoring activities is a common problem in software maintenance. To recall the rationales why changes were carried out, information has to be extracted from either proprietary documentations or software versioning systems. In this chapter, we describe a process for the recurring and sustainable discovery, handling, and treatment of quality defects in software systems. An annotation language is presented that is used to store information about quality defects found in source code and that represents the defect and treatment history of a part of a software system. The process and annotation language can not only be used to support quality defect discovery processes, but is also applicable in testing and inspection processes.

Motivation in Component-Based Software Development

2006 ◽  
pp. 414-421 ◽  
Author(s):  
G. Chroust
Keyword(s):  
Software Development ◽  
Software Systems ◽  
Willingness To Accept ◽  
Development Methodology ◽  
Component Based Development ◽  
Computer Interfaces ◽  
The People ◽  
Human Computer Interfaces ◽  
Development Approach

Information systems are designed for the people, by the people. The design of software systems with the help of software systems is another aspect of human-computer interfaces. New methods and their (non-)acceptance play an important role. Motivational factors of systems developers considerably influence the type and quality of the systems they develop (Arbaoui, Lonchamp & Montangero, 1999; Kumar & Bjoern-Andersen, 1990). To some extent, the quality of systems is a result of their developers’ willingness to accept new and (supposedly) better technology (Jones, 1995). A typical example is component-based development methodology (Bachmann et al., 2000; Cheesman & Daniels, 2001). Despite considerable publication effort and public lip service, component-based software development (CBD) appears to be getting a slower start than anticipated and hoped for. One key reason stems from the psychological and motivational attitudes of software developers (Campell, 2001; Lynex & Layzell, 1997). We therefore analyze the attitudes that potentially hamper the adoption of the component-based software development approach. Maslow’s Hierarchy of Need (Boeree, 1998; Maslow, 1943) is used for structuring the motives.

Effort Estimation Model for each Phase of Software Development Life Cycle

2012 ◽  
pp. 238-246
Author(s):  
Sarah Afzal Safavi ◽  
Maqbool Uddin Shaikh
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Cost Estimation ◽  
Use Case ◽  
Effort Estimation ◽  
Cost Overrun ◽  
Estimation Model ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
The Cost

The assessment of main risks in software development discloses that a major threat of delays are caused by poor effort / cost estimation of the project. Low / poor cost estimation is the second highest priority risk [Basit Shahzad]. This risk can affect four out of a total five phases of the software development life cycle i.e. Analysis, Design, Coding and Testing. Hence targeting this risk alone may reduce the overall risk impact of the project by fifty percent. Architectural designing of the system is a great activity which consumes most of the time in SDLC. Obviously, effort is put forth to produce the design of the system. It is evident that none of the existing estimation models try to calculate the effort put on designing of the system. Although use case estimation model uses the use case points to estimate the cost. But what is the cost of creating use cases? One reason of poor estimates produced by existing models can be negligence of design effort/cost. Therefore it shall be well estimated to prevent any cost overrun of the project. We propose a model to estimate the effort in each of these phases rather than just relying upon the cost estimation of the coding phase only. It will also ease the monitoring of project status and comparison against planned cost and actual cost incurred so far at any point of time.

scholarly journals Software Development Effort Duration and Cost Estimation using Linear Regression and K-Nearest Neighbors Machine Learning Algorithms

2019 ◽  
Vol 9 (2) ◽  
pp. 1043-1047
Keyword(s):  
Machine Learning ◽  
Linear Regression ◽  
Software Development ◽  
Cost Estimation ◽  
Performance Metrics ◽  
Nearest Neighbors ◽  
Machine Learning Algorithms ◽  
Development Effort ◽  
Effort Estimation ◽  
K Nearest Neighbors

Effort estimation is a crucial step that leads to Duration estimation and cost estimation in software development. Estimations done in the initial stage of projects are based on requirements that may lead to success or failure of the project. Accurate estimations lead to success and inaccurate estimates lead to failure. There is no one particular method which cloud do accurate estimations. In this work, we propose Machine learning techniques linear regression and K-nearest Neighbors to predict Software Effort estimation using COCOMO81, COCOMONasa, and COCOMONasa2 datasets. The results obtained from these two methods have been compared. The 80% data in data sets used for training and remaining used as the test set. The correlation coefficient, Mean squared error (MSE) and Mean magnitude relative error (MMRE) are used as performance metrics. The experimental results show that these models forecast the software effort accurately.

Sign in / Sign up

Export Citation Format

Share Document