Modelling and Simulation of Scrum Team Strategies: A Multi-agent Approach

Wang, Zhe

doi:10.1007/978-3-030-63322-6_4

Cited by 2 publications

(3 citation statements)

References 55 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This activity falls under continuous planning as it focuses on the ongoing planning and refinement of the project backlog. Daily Standup (P10): The Daily Standup is part of Continuous Planning because it provides a regular opportunity for the team to plan their day and align their efforts 80 . It helps in identifying any obstacles or dependencies that may affect the planned work and allows for course correction if needed. Effective Sprint Retrospectives (P18): Sprint retrospectives are part of the agile methodology and occur at the end of each sprint or iteration 81 . They provide an opportunity for the team to reflect on their performance, identify areas of improvement, and make necessary adjustments.…”

Section: Results and Analysismentioning

confidence: 99%

See 1 more Smart Citation

Multicriteria decision‐making–based framework for implementing DevOps practices: A fuzzy best–worst approach

Kumar,

Nadeem,

Shameem

2023

J Software Evolu Process

View full text Add to dashboard Cite

Increasingly, software organizations are implementing DevOps culture to benefit from it in terms of continuous testing, delivery, improvement, and so forth. Implementing DevOps is difficult due to a lack of understanding about the practices and their effective application for its effective implementation. This paper aims to explore different DevOps practices that can be implemented in software organizations. The study involves conducting a systematic literature review (SLR) to identify DevOps implementation practices, followed by the utilization of the fuzzy best–worst method (FBWM) to establish a taxonomy or classification of software practices. We have used an SLR to investigate the practices, and subsequently, the survey method was followed to validate the identified practices. Moreover, the best–worst method (BWM) was considered to evaluate the significance and develop the taxonomy of the practices. The results of this study extracted 19 practices that have been identified in the SLR process. The identified factors are further classified into six core DevOps lifecycle phases. The results of the BWM approach are shown. The outcomes of the study conclude that the proposed taxonomy of the practices could help DevOps practitioners and researchers effectively implement them in software development organizations.

show abstract

Section: Results and Analysismentioning

confidence: 99%

“…• Effective Sprint Retrospectives (P18): Sprint retrospectives are part of the agile methodology and occur at the end of each sprint or iteration. 81 They provide an opportunity for the team to reflect on their performance, identify areas of improvement, and make necessary adjustments.…”

Section: Validation Responsesmentioning

confidence: 99%

Multicriteria decision‐making–based framework for implementing DevOps practices: A fuzzy best–worst approach

Kumar,

Nadeem,

Shameem

2023

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Wang [51] introduces an agent-based simulation tool to compare solo and pair-programming, and other agile practices, in the context of Scrum development. The simulation tool can simulate all types of Scrum context and team composition to test designed strategies under various what-if assumptions in agent-based modelling.…”

Section: ) Simulation Of Software Processmentioning

confidence: 99%

Assessing the Risk of Software Development in Agile Methodologies Using Simulation

Lunesu¹,

Tonelli

Marchesi

et al. 2021

IEEE Access

View full text Add to dashboard Cite

Agile methodologies aim to reduce software development risk using short iterations, featuredriven development, continuous integration, testing automation, and other practices. However, the risk of project failure or time and budget overruns is still a relevant problem. The aim of this paper is to present and discuss a new approach to model some key risk factors in agile development, using software process simulation modeling (SPSM), which can complement other approaches, and whose usage is particularly suited for agile development. We introduce a new approach to modeling some key risk factors -namely project duration, number of implemented issues, and key statistics of issue completion time -using a simulator of agile development, which we developed to this purpose. The approach includes modeling the agile process, gathering data from the tool used for project management, and performing Monte Carlo simulations of the process, to get insights about the expected time and effort to complete the project, and to their distributions. The model's parameters that can cause risk are errors in effort estimation of the features to develop, variations in developers' assignment to these features, impediments related to developers' availability and work completion. To validate the simulator, and to demonstrate how the method can be used, we analyzed three open source projects, gathering their data from JIRA repositories. We ran Monte Carlo simulations of these projects, showing that the simulator can well approximate the progress of the real project, then varying the identified risk factors and statistically evaluating their effects on the risk parameters. The proposed approach is relevant for project managers, being able to quantitatively evaluate the risks, provided that the process and the project's data are properly modeled and gathered. As for the future, we are working to improve our risk assessment method, evaluating it on more case studies, scaling the model from a single team to multiple teams involved in one or more projects.INDEX TERMS Effort estimation error, random issue allocation, risk analysis, software process development, software process simulation.

show abstract

Modelling and Simulation of Scrum Team Strategies: A Multi-agent Approach

Cited by 2 publications

References 55 publications

Multicriteria decision‐making–based framework for implementing DevOps practices: A fuzzy best–worst approach

Multicriteria decision‐making–based framework for implementing DevOps practices: A fuzzy best–worst approach

Assessing the Risk of Software Development in Agile Methodologies Using Simulation

Contact Info

Product

Resources

About