Quality metrics in Agile Software Development Projects

ARPN journal of engineering and applied sciences, 2016

Ample of research has been carried out on the topic software metrics. Lots of metrics have been projected and validated in the field of software engineering especially for software development. However, metrics that related to software project management are still need to explore more especially from the industrial or practitioners. Identification of metrics for software project management may guide the project managers to manage and control the software projects. This is indirectly may reduce the software project failures in the industrial. This paper presents the processes and activities that used to identifying the performance criteria and the related metrics that can be used to monitor the performance of software projects. The aim of this paper is to identify the performance criteria and related metrics from the perspectives of practitioners. We carried out structured interview sessions among project managers from Malaysian Public Sector to accomplish this task. The results of t...

Software Quality Professional Magazine, 2007

An agile process has two primary actors. One is the development team, which commits to develop software for a specific small set of requirements in a limited amount of time, and then develops and tests this software. The other is overall project management, which hands off the requirements and appropriate components to the teams and interfaces with stakeholders such as customers. In a similar vein, metrics for an agile process should have two parts: one for the development team and one for project management. This article outlines metrics for an agile process being used at Brooks Automation. The process uses lightweight metrics at the development team level, where the focus is on developing working code, and more heavyweight metrics at the project management level, where the focus is on delivering a quality release to the customer. The authors describe the process and carry out a goal-question-metric (GQM) analysis to determine the goals and questions for such a process. They then examine the specific metrics used in the process, identifying them as either team-related or project-management-related; compare their scope to that shown by the GQM analysis; and identify issues in the existing metrics. Approaches to rectify those issues are then described.

In this paper, we present the Metrics Monitoring Tool, a tool for project members, project managers and upper management for reporting and following projects' metrics. We introduce how the tool was developed and how it was evaluated in students' software development projects. As a result, we show how the tool supported different user groups, suggest some new features, and propose some guidelines on how this tool could be utilized in software development and teaching of software project work.

Int. J. Hum. Cap. Inf. Technol. Prof., 2017

This paper presents the Metrics Monitoring Tool MMT that was developed in university graduate and undergraduate courses on software project work in 2014-2016. The tool aims to support project members, project managers and upper management in reporting and monitoring software and project metrics for their easier and more effective utilization. The paper covers the development process of the tool, evaluation assessment, its current composition and features. The paradigm applied in this study is Design Science Research and the methods for evaluation include prototype, expert evaluation, case study and technical experiment. Data was collected from the tool users by two questionnaires. As a result, MMT was evaluated to ease the metrics handling, while several aspects related to the richness of functionalities and usability still require further development.

Blockchain, Artificial Intelligence, and the Internet of Things, 2021

Every software development project is unique and different from repeatable manufacturing process. Each software project share different challenges related to technology, people and timelines. If every project is unique, how project manager can estimate project in a consistent way by applying his past experience. One of the major challenges faced by the project manager is to identify the key software metrics to control and monitor the project execution. Each software development project may be unique but share some common metric that can be used to control and monitor the project execution. These metrics are software size, effort, project duration and productivity. These metrics tells project manager about what to deliver (size), how it was delivered in past (productivity) and how long will it take to deliver with current team capability (time and effort). In this paper, we explain the relationship among these key metrics and how they statistically impact each other. These relationships have been derived based on the data published in book "Practical Software Estimation" by International Software Benchmarking Group. This paper also explains how these metrics can be used in predicting the total number of defects. Study suggests that out of the four key software metrics software size significantly impact the other three metrics (project effort, duration and productivity). Productivity does not significantly depend on the software size but it represents the nonlinear relationship with software size and maximum team size, hence, it is recommended not to have a very big team size as it might impact the overall productivity. Total project duration only depends on the software size and it does not depend on the maximum team size. It implies that we cannot reduce project duration by increasing the team size. This fact is contrary to the perception that we can reduce the project duration by increasing the project team size. We can conclude that software size is the important metrics and a significant effort must be put during project initiation phases to estimate the project size. As software size will help in estimating the project duration and project efforts so error in estimating the software size will have significant impact on the accuracy of project duration and effort. All these key metrics must be re-calibrated during the project development life cycle.

Evaluating, monitoring, and improving the effectiveness of project management can contribute to successful acquisition of software systems. According to our empirical studies on a range of software development projects, half of the variation in software project success ratings may be explained by project management effectiveness measurements. To improve the quality of the management, to focus our improvement efforts on the right issues, and to increase the odds of success in software projects, it is essential to measure the effectiveness of software project management. In this paper, we introduce four different approaches for measuring software project management effectiveness. Two of these approaches discussed in this paper were successfully used in the development of a metric for software project management effectiveness. The contribution of this paper is the introduction of these approaches for guiding the researchers for the development of other project management metrics.

Evaluating, monitoring, and improving the effectiveness of project management can contribute to successful acquisition of software systems. In this dissertation, we introduce a quantitative metric for gauging the effectiveness of managing a software-development project. The metric may be used to evaluate and monitor project management effectiveness in software projects by project managers, technical managers, executive managers, project team leaders and various experts in the project organization. It also has the potential to be used to quantify the effectiveness improvement efforts on project management areas. The metric is validated by conducting survey studies on software projects from public and private sectors. A statistical analysis of sixteen surveys on software projects, spanning small to large development projects, indicated that there is a strong positive correlation with software project success ratings provided by study participants and project management effectiveness measurements. Other contributions of this research include identification of approaches for measuring project management effectiveness of software projects, establishment of theories on project management and on project management effectiveness measurement, and the introduction and validation of a framework for software project management.

2000

Quality Management is very important in Software Projects. Quality is achieved to the extent that a project end product meets the client's needs and expectations; it also means that a product should meet its specification. Paper discusses about Life Cycle approach to Software Quality Management process and its principles, activities, factors, methods, benefits, and also Principles of Quality Risk Management.

2013

The Central role that software development plays in today's world is beyond anyone's imagination. Software development is one of the major areas of focus for any organisations. The managers are increasingly focusing on process improvement in software development area. This demand has led to improved approaches to software development, with the most prominent being object-oriented software design. The focus on process improvement has increased the demand for software measures or metrics with which we can manage the things effectively and efficiently. This research addresses these needs through the development and identification of metrics that can be used in a project. We have used Metrics developed in previous research, while contributing to the field's understanding of software design. An automated data analysis tool was used to compare the relevance of these metrics in different projects. We have taken three projects of Web, Desktop and Mobile nature to ascertain the v...

The requirement in software projects and initiatives can be considered as a living organism that is evolved throughout the project development process. Controlling the evolution of the project requirements can successfully assure qualitative and quantitative project management metrics. Managing software projects by tracking and measuring the requirements behavior in a project life cycle is an innovative and challenging software project management conception and approach. This paper aims to introduce a new project management method based on requirements management tracking, using a number of metrics that analyze the requirements evolutional behavior against weighted project implementation phases, weighted project functionality and weighted project goals and expectations. To achieve such results, the requirements are also weighted themselves on project complexity and criticality. This weighted requirements based project tracking process, is supported by a project tracking analysis model combining a set of metrics that result to the identification of a single volume indicating the progress of the project.

2010

In a world of growing competitiveness, ”quality” is a main subject. On recent years, there has been a trend towards the improvement of software projects’ quality. This means improving not only the final software products, but especially the quality of leadership and of project management. It is now recognized that the quality of software products and services can be improved if quality management is accomplished according to the unique characteristics and complexity of each project. In this paper we present the main concepts of quality management, as also some approaches of software quality assurance.

Software metrics provides a quantitative measure that enables software people to gain insight into the efficacy of the software projects. These metrics data can then be analyzed and compared to determine and improve the quality of the software that is being developed. Therefore, it is essential to compute metrics. The proposed metrics tool facilitates the users to calculate the various metrics during the life cycle of a project. This unique feature is not available with existing metrics tools as they need to use different tools to compute the metrics for each phase in SDLC. The metrics values that are calculated help us in determining the quality and reliability of the project. This tool also helps us in determining the risks as well as the possibility of errors getting introduced into the code due to changes based on the cyclomatic complexity of the project. The various metrics that can be determined includes Function Point Metrics, Project Point Metrics, Estimated Effort and Duration of a project using COCOMO Model,

2018

Trabalho financiado pelo Edital DPI / DPG - UnB n° 02/2018 (Apoio a Publicacao de Artigos em Anais de Eventos, resultantes de Pesquisa Cientifica, Tecnologica e de Inovacao de servidores do Quadro da Universidade de Brasilia).

Computer Standards & Interfaces, 2020

This is a PDF file of an article that has undergone enhancements after acceptance, such as the addition of a cover page and metadata, and formatting for readability, but it is not yet the definitive version of record. This version will undergo additional copyediting, typesetting and review before it is published in its final form, but we are providing this version to give early visibility of the article. Please note that, during the production process, errors may be discovered which could affect the content, and all legal disclaimers that apply to the journal pertain.