scispace - formally typeset
Search or ask a question
Posted Content

Understanding the Perceived Relevance of Capability Measures: A Survey of Agile Software Development Practitioners

TL;DR: In the light of swift, incremental and iterative nature of Agile Softwar, the role of human-aspects of software engineers needs to be considered in the context of agile development.
Abstract: Context: In the light of the swift and iterative nature of Agile Software Development (ASD) practices, establishing deeper insights into capability measurement within the context of team formation is crucial, as the capability of individuals and teams can affect team performance and productivity. Although a former Systematic Literature Review (SLR) synthesized the state of the art in relation to capability measurement in ASD with a focus on selecting individuals to agile teams, and capabilities related to team performance and success, determining to what degree the SLR's results apply to practice can provide progressive insights to both research and practice. Objective: Our study investigates how agile practitioners perceive the relevance of individual and team level measures for characterizing the capability of an agile team and its members. Furthermore, to scrutinize variations in practitioners' perceptions, our study further analyzes perceptions across stratified demographic groups. Method: We undertook a Web-based survey using a questionnaire built based on the capability measures identified from a previously conducted SLR. Results: Our survey responses (60) indicate that 127 individual and 28 team capability measures were considered as relevant by the majority of practitioners. We also identified seven individual and one team capability measure that have not been previously characterized by our SLR. The surveyed practitioners suggested that an agile team member's responsibility and questioning skills significantly represent the member's capability. Conclusion: Results from our survey align with our SLR's findings. Measures associated with social aspects were observed to be dominant compared to technical and innovative aspects. Our results can support agile practitioners in their team composition decisions.
Citations
More filters
Journal ArticleDOI
TL;DR: In this article , the authors derived an overarching model covering both human and organizational factors facilitating the development of safe and secure robotic systems, including 17 individual factors and 13 organizational factors that enhance safety and security by design.

1 citations

Proceedings ArticleDOI
07 Nov 2022
TL;DR: In this article , the authors use Heterogeneous Information Network (HIN) analysis to profile the vulnerability inducing and vulnerability fixing behaviors of developers in software projects using HIN analysis and investigate the impact of developer profiles in predicting vulnerability inducing commits, and compare the findings against the approach based on code metrics.
Abstract: Software vulnerability prediction and management have caught the interest of researchers and practitioners, recently. Various techniques that are usually based on characteristics of the code artefacts are also offered to predict software vulnerabilities. While other studies achieve promising results, the role of developers in inducing vulnerabilities has not been studied yet. We aim to profile the vulnerability inducing and vulnerability fixing behaviors of developers in software projects using Heterogeneous Information Network (HIN) analysis. We also investigate the impact of developer profiles in predicting vulnerability inducing commits, and compare the findings against the approach based on the code metrics. We adopt Random Walk with Restart (RWR) algorithm on HIN and the aggregation of code metrics for extracting all the input features. We utilize traditional machine learning algorithms namely, Naive Bayes (NB), Support Vector Machine (SVM), Random Forest (RF) and eXtreme Gradient Boosting (XGBoost) to build the prediction models.We report our empirical analysis to predict vulnerability inducing commits of four Apache projects. The technique based on code metrics achieves 90% success for the recall measure, whereas the technique based on profiling developer behavior achieves 71% success. When we use the feature sets obtained with the two techniques together, we achieve 89% success.

1 citations

Book ChapterDOI
01 Jan 2022
TL;DR: In this paper , the authors report on the design and validation of a capability measurement instrument for software delivery teams that make use of the DevOps approach, based on the results of a systematic literature review and was developed and validated by involving a total of five domain experts and conducting a field study among six team members.
Abstract: Abstract This paper reports on the design and validation of a capability measurement instrument for software delivery teams that make use of the DevOps approach. The instrument is based on the results of a systematic literature review and was developed and validated by involving a total of five domain experts and conducting a field study among six DevOps team members. To this end, we used qualitative and survey-based data collection methods from participatory action research as well as design science. The resulting instrument encompasses five dimensions, covering seventeen capabilities and thirty-eight associated practices. The practices are evaluated on five capability levels. The results of the validation process indicate clear agreement of the domain experts and team members with all aspects of the instrument. As a contribution to practice, this research offers a pragmatic tool for IS practitioners which provides insight into the status of their DevOps transformation and offers directions for improving DevOps team performance. Furthermore, this research contributes to the ongoing research stream on DevOps by providing novel insights into the nature of DevOps capabilities and their potential configurations.
Journal ArticleDOI
TL;DR: In this article , the authors examined the factors that influence team members of software development projects to continue using agile methodologies after their initial adoption and found that confirmation of expectations regarding perceived usefulness and satisfaction are key determinants of agile continuance intentions in software development large-scale projects.
Journal ArticleDOI
TL;DR: This paper mined 9,096 Open Source Software Java projects with a total of 435 million LOC and more than 500,000 comments labeled as SATD, including both Easy to Find and Hard to Find.
Abstract: Most Self-Admitted Technical Debt (SATD) research utilizes explicit SATD features such as 'TODO' and 'FIXME' for SATD detection. A closer look reveals several SATD research uses simple SATD ('Easy to Find') code comments without the contextual data (preceding and succeeding source code context). This work addresses this gap through PENTACET (or 5C dataset) data. PENTACET is a large Curated Contextual Code Comments per Contributor and the most extensive SATD data. We mine 9,096 Open Source Software Java projects with a total of 435 million LOC. The outcome is a dataset with 23 million code comments, preceding and succeeding source code context for each comment, and more than 500,000 comments labeled as SATD, including both 'Easy to Find' and 'Hard to Find' SATD. We believe PENTACET data will further SATD research using Artificial Intelligence techniques.
References
More filters
Book
01 Oct 2001
TL;DR: Agile Software Development as discussed by the authors compares software development to a game, where team members play the game knowing that the ultimate goal is to win, always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice.
Abstract: Software development paradigms are shifting. The development group's "team" ability, and the effects of the individual developer, become more important as organizations recognize that the traditional approach of increasing process pressure and overworking team members is not getting the job done. The pioneers of Agile methodologies question the preconceived processes within which development teams work. Rather than adding to the burden of the individual developer, Agile asks "how can we change the process so that the team is more productive, while also improving quality?" The answer is in learning to play the "game." Written for developers and project managers, Agile Software Development compares software development to a game. Team members play the game knowing that the ultimate goal is to win---always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice. Players must keep an open mind to different methodologies, and focus on the goal of developing quality software in a short cycle time.

2,081 citations

01 Jan 2001
TL;DR: Atkinson and Flint as discussed by the authors used snowball sampling to identify respondents who are then used to refer researchers on to other respondents, which has a number of advantages for sampling University of Surrey Sociology at Surrey.
Abstract: Rowland Atkinson and John Flint are researchers at the Department of Urban Studies, University of Glasgow. Both have an interest in the spatial distribution and experience of social exclusion and have been commissioned to devise a methodology for tracing residents who leave regeneration areas in Scotland. •In its simplest formulation snowball sampling consists of identifying respondents who are then used to refer researchers on to other respondents. •Snowball sampling contradicts many of the assumptions underpinning conventional notions of sampling but has a number of advantages for sampling University of Surrey Sociology at Surrey

2,023 citations


"Understanding the Perceived Relevan..." refers background in this paper

  • ...This technique has been observed to be particularly useful in hard-to-reach populations, where the researcher tries to contact a network of qualified study subjects with the support of first point contacts [68]....

    [...]

Book
01 Feb 1992
TL;DR: This work presents an overview of the Sample Survey Process, and discusses how to design and manage effective questionnaires, and the importance of knowing the sample size and quality.
Abstract: Figures, Tables, Exhibits, and Worksheets. Preface. The Authors. PART ONE: DEVELOPING AND ADMINISTERING QUESTIONNAIRES. 1. An Overview of the Sample Survey Process. 2. Designing Effective Questionnaires: Basic Guidelines. 3. Developing Survey Questions. 4. Utilizing Focus Groups in the Survey Research Process. PART TWO: ENSURING SCIENTIFIC ACCURACY. 5. Descriptive Statistics: Measures of Central Tendency and Dispersion. 6. The Theoretical Basis of Sampling. 7. Confidence Intervals and Basic Hypothesis Testing. 8. Determining the Sample Size. 9. Selecting a Representative Sample. PART THREE: PRESENTING AND ANALYZING SURVEY RESULTS. 10. Analyzing Cross-Tabulated Data. 11. Testing the Difference Between Means. 12. Regression and Correlation. 13. Preparing an Effective Final Report. Resource A: Table of Areas of a Standard Normal Distribution. Resource B: Glossary. Resource C: Answers to Selected Exercises. Bibliography. Index.

1,816 citations


"Understanding the Perceived Relevan..." refers background in this paper

  • ...According to Rea and Parker [92], the following are the interpretations for ε2 value: weak effect (0....

    [...]

  • ...According to Rea and Parker [92], the following are the interpretations for ε2 value: weak effect (0.01 ε2 0.04), moderate (0.04 ε2 0.16), relatively strong (0.16 < ε2 < 0.36), strong (0.36 < ε2 < 0.64) and very strong (0.64 < ε2 < 1)....

    [...]

Journal Article
TL;DR: This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
Abstract: Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.

1,087 citations


"Understanding the Perceived Relevan..." refers background in this paper

  • ...Some of the studies conducted in other contexts reported that perceptions of software professionals differ based on their role [40], work experience [55] and work environment (ASD methodology [56] and team size [57])....

    [...]

Journal ArticleDOI
TL;DR: This research study was a survey study on the critical success factors of Agile software development projects using quantitative approach, finding that only 10 out of 48 hypotheses were supported, identifying threecritical success factors for AgileSoftware Engineering Techniques, Delivery Strategy, and Team Capability.

908 citations


"Understanding the Perceived Relevan..." refers background in this paper

  • ...The studies employed interviews [44], survey [46] and a mix of both mechanisms [24], [45], for gathering data....

    [...]

  • ...4]) was discussed by two studies [44], [46]....

    [...]

  • ...Chow and Cao [46] conducted a survey for identifying the critical success factors of ASD projects....

    [...]

  • ...[46] Survey Investigating critical success factors in ASD projects...

    [...]

  • ...On the other hand, four studies reported team level skills and abilities, within ASD context [24], [44], [45], [46]....

    [...]