A critical examination of recent industrial surveys on agile method usage

Stavru, Stavros

doi:10.1016/j.jss.2014.03.041

Cited by 101 publications

(89 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…According to the State of Agile Survey (VersionOne 2016), 43% of the self-selected respondents worked in development organizations having more than 50% of teams using agile, while only 4% of respondents stated that none of their teams were agile, and 62% of almost 4000 respondents came from an organization with over a hundred people in software development. While the survey is nonscientific, and problematic from a methodological point of view (Stavru 2014), it is the largest reoccurring survey on agile adoption, and it indicates that a significant number of big organizations use agile. Moreover, practitioners at the XP conference in 2010 listed the topic "Agile and large projects" as the number one top burning research question (Freudenberg and Sharp 2010).…”

Section: Introductionmentioning

confidence: 99%

“…Moreover, practitioners at the XP conference in 2010 listed the topic "Agile and large projects" as the number one top burning research question (Freudenberg and Sharp 2010). In recent workshops on large-scale agile development, the introduction of agile methods was one of the highlighted themes needing more research (Dingsøyr and Moe 2013;2014).…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Large-scale agile transformation at Ericsson: a case study

et al. 2018

View full text Add to dashboard Cite

Many large organizations are adopting agile software development as part of their continuous push towards higher flexibility and shorter lead times, yet few reports on large-scale agile transformations are available in the literature. In this paper we report how Ericsson introduced agile in a new R&D product development program developing a XaaS platform and a related set of services, while simultaneously scaling it up aggressively. The overarching goal for the R&D organization, distributed to five sites at two continents, was to achieve continuous feature delivery. This single case study is based on 45 semistructured interviews during visits at four sites, and five observation sessions at three sites. We describe how the organization experimented with different set-ups for their tens of agile teams aiming for rapid end-to-end development: from component-based virtual teams to totally cross-functional, cross-component, cross-site teams. Moreover, we discuss the challenges the organization faced and how they mitigated them on their journey towards continuous and rapid software engineering. We present four lessons learned for large-scale agile transformations: 1) consider using an experimental approach to transformation, 2) consider implementing the transformation step-wise in complex large-scale settings, 3) team inter-changeability can be limited in a complex large-scale product -specialization might be needed, and 4) not using a common agile framework for the whole organization, in combination with insufficient common trainings and coaching may lead to a lack of common direction in the agile implementation. Further in-depth case studies on large-scale agile transformations, on customizing agile to large-scale settings, as well as on the use of scaling frameworks are needed.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Large-scale agile transformation at Ericsson: a case study

et al. 2018

View full text Add to dashboard Cite

show abstract

“…Stavru surveyed the usage of agile methods through industrial survey studies published between 2011 and 2012 [19]. They determined the papers, which could be trusted and recommend that the quality level of researches could be improved.…”

Section: Agile Methodsmentioning

confidence: 99%

Agile Software Development Methodologies: Survey of Surveys

Al-Zewairi¹,

Biltawi²,

Etaiwi³

et al. 2017

JCC

View full text Add to dashboard Cite

Agile software design and development methodologies have been gaining rigorous attention in the software engineering research community since their early introduction in the mid-nineties in addition to being highly adopted by the software development industry. In the last 15 years, an excessive number of research studies have been conducted on agile methods, a great number of notable methods have been proposed and various surveys have been presented by many researchers. In this study, the authors intend to conduct a literature survey study of the surveys of the different agile methodologies ranging from January 2000 to December 2015 using an intuitive research methodology called "Compare and Review" (CR). Furthermore, these survey papers were classified into four major categories according to their area of study. Additionally, the newly proposed agile methodologies that have not been addressed yet in any other literature review were reviewed and compared in terms of where the changes that they proposed lay on the SDLC.

show abstract

“…As the study used non-probabilistic sampling, the findings cannot be generalised to a wider population (Stavru 2014). However, the respondents do appear to represent a diverse group of experienced practitioners, and the common findings should therefore provide a useful indication of widely used approaches to design quality.…”

Section: The Respondentsmentioning

confidence: 98%

Recognising object-oriented software design quality: a practitioner-based questionnaire survey

Stevenson

Wood

2017

Software Qual J

View full text Add to dashboard Cite

Design quality is vital if software is to be maintainable. What practices do developers actually use to achieve design quality in their day-to-day work and which of these do they find most useful? To discover the extent to which practitioners concern themselves with object-oriented design quality and the approaches used when determining quality in practice, a questionnaire survey of 102 software practitioners, approximately half from the UK and the remainder from elsewhere around the world was used. Individual and peer experience are major contributors to design quality. Classic design guidelines, well-known lower level practices, tools and metrics all can also contribute positively to design quality. There is a potential relationship between testing practices and design quality. Inexperience, time pressures, novel problems, novel technology, and imprecise or changing requirements may have a negative impact on quality. Respondents with most experience are more confident in their design decisions, place more value on reviews by team leads and are more likely to rate design quality as very important. For practitioners, these results identify the techniques and tools that other practitioners find effective. For researchers, the results highlight a need for more work investigating the role of experience in the design process and the contribution experience makes to quality. There is also the potential for more in-depth studies of how practitioners are actually using design guidance, including Clean Code. Lastly, the potential relationship between testing practices and design quality merits further investigation.

show abstract

A critical examination of recent industrial surveys on agile method usage

Cited by 101 publications

References 14 publications

Large-scale agile transformation at Ericsson: a case study

Large-scale agile transformation at Ericsson: a case study

Agile Software Development Methodologies: Survey of Surveys

Recognising object-oriented software design quality: a practitioner-based questionnaire survey

Contact Info

Product

Resources

About