Agility at scale: Economic governance, measured improvement, and disciplined delivery

Brown, Alan W.; Ambler, Scott W.; Royce, Walker

doi:10.1109/icse.2013.6606636

Cited by 17 publications

(19 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several primary studies make reference to product architecture and design [2,7,8,15,51,62,79,16,17]. CD demands a software architecture in which the product and its underlying infrastructure continuously evolve and adapt to changing requirements [16,51]. Thus, it is essential that the underlying architecture is flexible and is able to accommodate rapid feedback [7,8,51].…”

Section: Flexible Product Design and Architecturementioning

confidence: 99%

“…new functionality, product enhancements and innovation) rather than defensive efforts (e.g. bug fixes) [8,7,51,16]. To achieve this, the software architecture and design have to be highly modular and loosely coupled [51,62,8].…”

Section: Flexible Product Design and Architecturementioning

confidence: 99%

“…TDD and test planning [59]) and GUI testing are discussed. Code driven testing practices are mostly preferred by practitioners working in CD [1,8,57,10,59,16]. However, due to limitations such as high costs and the effort required to train and manage test-programs, Agarwal [1] recommends the use of automated GUI testing.…”

Section: Test Automationmentioning

confidence: 99%

See 2 more Smart Citations

Continuous deployment of software intensive products and services: A systematic mapping study

Rodríguez

Haghighatkhah

Lwakatare

et al. 2017

Journal of Systems and Software

198

153

View full text Add to dashboard Cite

BACKGROUND-The software intensive industry is moving towards the adoption of a value-driven and adaptive real-time business paradigm. The traditional view of software as an item that evolves through releases every few months is being replaced by the continuous evolution of software functionality. OBJECTIVE-This study aims to classify and analyse the literature related to continuous deployment in the software domain in order to scope the phenomenon, provide an overview of the state-of-the-art, investigate the scientific evidence in the reported results and identify areas suitable for further research. METHOD-We conducted a systematic mapping study and classified the continuous deployment literature. The benefits and challenges related to continuous deployment were also analysed. RESULTS-The systematic mapping study includes 50 primary studies published between 2001 and 2014. An in-depth analysis of the primary studies revealed ten recurrent themes that characterize continuous deployment and provide researchers with directions for future work. In addition, a set of benefits and challenges of which practitioners may take advantage were identified. CONCLUSION-Overall, although the topic area is very promising, it is still in its infancy, thus offering a plethora of new opportunities for both researchers and software intensive companies.

show abstract

Section: Flexible Product Design and Architecturementioning

confidence: 99%

Section: Flexible Product Design and Architecturementioning

confidence: 99%

See 1 more Smart Citation

Continuous deployment of software intensive products and services: A systematic mapping study

Rodríguez

Haghighatkhah

Lwakatare

et al. 2017

Journal of Systems and Software

198

153

View full text Add to dashboard Cite

show abstract

“…Hodgetts presents the refactoring of development practices to incrementally improve selected practices. In this regard, Brown et al and Rodríguez et al present general principles, ie, steering using economic governance, measure incremental improvements honestly, and empower teams to improve the agility of an organization and, especially, motivate the use of Lean principles, especially Design Thinking to push agile methods and their effective use.…”

Section: Study Resultsmentioning

confidence: 99%

How has SPI changed in times of agile development? Results from a multi‐method study

Küpper

Pfahl

Jürisoo

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

The emergence of agile methods and practices has not only changed the development processes but might also have affected how companies conduct software process improvement (SPI).Through a set of complementary studies, we aim to understand how SPI has changed in times of agile software development. Specifically, we aim (a) to identify and characterize the set of publications that connect elements of agility to SPI, (b) to explore to which extent agile methods/practices have been used in the context of SPI, and (c) to understand whether the topics addressed in the literature are relevant and useful for industry professionals. To study these questions, we conducted an in-depth analysis of the literature identified in a previous mapping study, an interview study, and an analysis of the responses given by industry professionals to SPI-related questions stemming from an independently conducted survey study. Regarding the first question, we identified 55 publications that focus on both SPI and agility of which 48 present and discuss how agile methods/practices are used to steer SPI initiatives. Regarding the second question, we found that the two most frequently mentioned agile methods in the context of SPI are Scrum and Extreme Programming (XP), while the most frequently mentioned agile practices are integrate often, test-first, daily meeting, pair programming, retrospective, on-site customer, and product backlog. Regarding the third question, we found that a majority of the interviewed and surveyed industry professionals see SPI as a continuous activity. They agree with the agile SPI literature that agile methods/practices play an important role in SPI activities but that the importance given to specific agile methods/practices does not always coincide with the frequency with which these methods/practices are mentioned in the literature. KEYWORDSagile methods, software process improvement, SPI, systematic review INTRODUCTIONSoftware has become the key driver in many industry sectors, and software development processes face increasing demands for flexibility, customer-and value-orientation, short time-to-market cycles, and high quality. As a consequence, companies are challenged with finding appropriate software development methods that, on the one hand, allow for flexible project operation and, on the other hand, allow for creating high-quality products. To define, adapt, evaluate, and improve their software processes, companies implement software process improvement (SPI) initiatives. According to Humphrey 1 and Münch et al, 2 SPI comprises a variety of tasks, ie, scoping, assessment, design and realization, and continuous improvement. Furthermore, SPI is considered relevant to companies 3 regardless of their size and industry sector.SPI has been around for decades, 4 and numerous approaches to conduct SPI have been proposed. 5,6 The different SPI approaches range from formal/prescriptive/de-facto (commercial) standards, such as the Capability Maturity Model Integration (CMMI) or ISO/IEC 15504, which are often critic...

show abstract

“…Many researchers suggest that agile principles are helpful in minimizing DSD challenges. [1,4,[25][26][27][28][29][30].…”

Section: Related Workmentioning

confidence: 99%

Towards Scrum Based Agile Framework for Global Software Development Teams

Shafiq

Hafeez

Ali

et al. 2019

Mehran Univ. res. j. eng. technol.

View full text Add to dashboard Cite

Organizations are moving their workforce to guarantee matters of trade and profit where accounts are expected to be less expensive and provide better quality products with the accessibility of skilled labor. With the evident benefits, distributed teams often face challenges with reliable and efficient communication coordination patterns that lead towards project failure. In the rapidly growing software industry, it becomes critical for any business to have better management activities to acquire right processes and practices. Agile methods are considered as a remedy for mitigating distributed teams’ challenges, with their consistent focus on communication. Here, we intend to propose a tailored Scrum based solution for distributed teams that empowers anticipated communication and coordination throughout the development process. In the first phase of framework development we have evaluated the state of agile practices from both literature and industry; based on collected evidence and suggestive guidelines a scrum based agile framework was formulated. The Scrum is a project management method in Agile Methods family. Scrum is an iterative process that asks for incremental development of the product, includes cross functional development and testing teams. Evaluation results show that the proposed framework contributes positively to improve development process quality. We have performed theoretical as well as empirical evaluation to validate proposed framework. We have eight project managing rising aspects in DSD (Distributed Software Development) to evaluate the proposed framework.

show abstract

Agility at scale: Economic governance, measured improvement, and disciplined delivery

Cited by 17 publications

References 6 publications

Continuous deployment of software intensive products and services: A systematic mapping study

Continuous deployment of software intensive products and services: A systematic mapping study

How has SPI changed in times of agile development? Results from a multi‐method study

Towards Scrum Based Agile Framework for Global Software Development Teams

Contact Info

Product

Resources

About