Table of Links Abstract and 1. Introduction Abstract and 1. Introduction Background and 2.1. Related Work
2.2. The Impact of XP Practices on Software Productivity and Quality
2.3. Bayesian Network Modelling


Model Design
3.1. Model Overview
3.2. Team Velocity Model
3.3. Defected Story Points Model


Model Validation
4.1. Experiments Setup
4.2. Results and Discussion


Conclusions and References Background and 2.1. Related Work
2.2. The Impact of XP Practices on Software Productivity and Quality
2.3. Bayesian Network Modelling Background and 2.1. Related Work Background and 2.1. Related Work 2.2. The Impact of XP Practices on Software Productivity and Quality 2.2. The Impact of XP Practices on Software Productivity and Quality 2.3. Bayesian Network Modelling 2.3. Bayesian Network Modelling Model Design
3.1. Model Overview
3.2. Team Velocity Model
3.3. Defected Story Points Model Model Design Model Design 3.1. Model Overview 3.1. Model Overview 3.2. Team Velocity Model 3.2. Team Velocity Model 3.3. Defected Story Points Model 3.3. Defected Story Points Model Model Validation
4.1. Experiments Setup
4.2. Results and Discussion Model Validation Model Validation 4.1. Experiments Setup 4.1. Experiments Setup 4.2. Results and Discussion 4.2. Results and Discussion Conclusions and References Conclusions and References Conclusions and References 4.1. Experiments Setup Collecting data from real projects to validate our model was a difficult task due to several reasons. Due to XP simplicity value, it is difficult to find company collecting information regarding their activities and practices. Moreover, most real XP projects are developed by private companies having restrictions on publishing their internal development process. In addition, there is no guarantee that the available data is sufficient for model validation. Two XP projects provided enough data to test our model. The first one is the Repo Margining System project [4]. The second one is a controlled case study reported by Pekka Abrahamsson [17]. We will refer to this case study in the rest of this paper by Abrahamsson Case Study. The model input data for the two projects are shown in tables 2 and 3. The model internal parameters are summarized in table 4. Repo Margining System Abrahamsson Case Study Authors:
(1) Mohamed Abouelelam, Software System Engineering, University of Regina, Regina, Canada;
(2) Luigi Benedicenti, Software System Engineering, University of Regina, Regina, Canada. Authors: Authors: (1) Mohamed Abouelelam, Software System Engineering, University of Regina, Regina, Canada; (2) Luigi Benedicenti, Software System Engineering, University of Regina, Regina, Canada. This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. available on arxiv available on arxiv

Part of HackerNoon's growing list of open-source research papers, promoting free access to academic material.

The Final Verdict: Is Pair Programming Worth the Effort?

Predictive Modeling in Practice: A Case Study with AgenaRisk

Bayesian Inference Explained

Too Long; Didn't Read

Make resilience your competitive advantage

The Challenges of Data Collection for Software Engineering Research

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Future Research in XP Modeling: A Call for Self-Learning Models

EffConPy: Open Source Causality Discovery in Python

Predicting Software Development with XP: A Look at Existing Models

The Role of Onsite Customers in Agile Software Development

Understanding Bayesian Networks: A Graphical Model for Uncertainty

Future Research in XP Modeling: A Call for Self-Learning Models

EffConPy: Open Source Causality Discovery in Python

Predicting Software Development with XP: A Look at Existing Models

The Role of Onsite Customers in Agile Software Development

Understanding Bayesian Networks: A Graphical Model for Uncertainty

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps