Scaling agile methods to regulated environments: An industry case study

@article{Fitzgerald2013ScalingAM,
  title={Scaling agile methods to regulated environments: An industry case study},
  author={Brian Fitzgerald and Klaas-Jan Stol and Ryan O'Sullivan and Donal O'Brien},
  journal={2013 35th International Conference on Software Engineering (ICSE)},
  year={2013},
  pages={863-872}
}
Agile development methods are growing in popularity with a recent survey reporting that more than 80% of organizations now following an agile approach. Agile methods were seen initially as best suited to small, co-located teams developing non-critical systems. The first two constraining characteristics (small and co-located teams) have been addressed as research has emerged describing successful agile adoption involving large teams and distributed contexts. However, the applicability of agile… 
View on ACM
ulir.ul.ie
163 Citations
Highly Influential Citations
14
Background Citations
68
Methods Citations
22
Results Citations
2

Figures and Tables from this paper

163 Citations

Citation Type

Citation Type

Agile Methods on Large Projects in Large Organizations
TLDR
This article investigates the adoption and adaptation of agile methods for use on large projects in large organizations and finds that some features are common to almost all observations, whereas others show extreme variability.
Agile development as a change management approach in software projects: Applied case study
  • Mohammed Alawairdhi
  • Business
    2016 2nd International Conference on Information Management (ICIM)
  • 2016
TLDR
It has been argued that that agile software development, with its practices for user involvement and product visibility, can be used as a change management approach in most small to medium scale projects.
Characterizing the presence of agility in large-scale agile software development
TLDR
This work conducted a study to identify how large-scale agile teams that have been using agile for a certain while perceive themselves in terms of maturity in agile aspects and contributes to researchers and professionals better understand how agility is defined and perceived in large settings.
Crossing the Boundaries - Agile Methods in Large-Scale, Plan-Driven Organizations: A Case Study from the Financial Services Industry
TLDR
A best-practice model for their effective implementation in a complex environment is proposed and an organization-specific agile development framework and continuous stakeholder involvement are identified as crucial success factors.
What Makes Agile Software Development Agile?
TLDR
An empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility, concluding that agility cannot be defined solely at the process level.
What Makes Agile Software Development Agile?
TLDR
An empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility, concluding that agility cannot be defined solely at the process level.
Suitability of Agile Methods for Safety-Critical Systems Development: A Survey of Literature
TLDR
The findings indicate that many organizations are relying on traditional methods to develop safety critical systems because they are familiar with them and have been thoroughly tested over time, but with the advent of agile methods there is a paradigm shift by non safety critical system developers.
Systematic Literature Review of Agile Scalability for Large Scale Projects
TLDR
This study will identify the current research problems of the agile scalability for large size projects by giving a detail literature review of the identified problems, existed work for providing solution to these problems and will find out limitations of the existing work for covering the identified Problems.
Strategies for doing Agile in a non-Agile Environment
TLDR
This work investigates practitioners' mitigation strategies related to the challenge of doing Agile in a non-Agile environment to better understanding of how Agile practitioners can accomplish bottom-up change in their organisation.
Understanding the Benefits of Agile Software Development in Regulated Environments
TLDR
The main achievement is the development of four categories, which describe the benefit of agile software development in regulated environments, which are master complexity, reduce effort, improve usability, and promote collaboration.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 64 REFERENCES
Lean/Agile Software Development Methodologies in Regulated Environments - State of the Art
TLDR
Drawing on the results of a systematic literature review, it is found that evidence is sparse for Lean/Agile adoption in these domains and “out-of-the-box” Agile practices do not seem to fully suit these environments but rather tailored Agile versions combined with more plan-based practices seem to be making inroads.
‘Lots done, more to do’: the current state of agile systems development research
TLDR
Agile research has lagged behind practice, as is often the case with new and emerging phenomena in Information Systems Development (ISD).
Escape the waterfall: Agile for aerospace
TLDR
This paper will document successful integration of test-driven development, pair programming, refactoring, an iterative approach, and other Agile methods into a traditional DO-178B software development process.
Assumptions Underlying Agile Software-Development Processes
TLDR
The principles and advocated practices of agile processes are examined and limitations that may arise from these assumptions are identified and how the limitations can be addressed by incorporating other software-development techniques and practices into agile development environments are outlined.
Coevolving Systems and the Organization of Agile Software Development
TLDR
Time pacing, self-management with discipline and routinization of exploration are among the agile enablers found in the cases studies while event pacing, centralized management, and lack of resources allocated to exploration are found to be inhibitors to agility.
Agile Software Development in Large Organizations
TLDR
This analysis relies on experience collected and shared among four SEC members namely ABB, DaimlerChrysler, Motorola, and Nokia to generalize their findings by analyzing some of their common experiences in the particular context of large organizations with well-established structures and processes.
Agile methods for open source safety‐critical software
TLDR
Agile methods have matured since the academic community suggested almost a decade ago that they were not suitable for safety‐critical systems; the experiences on the image‐guided surgical toolkit project are presented as a case study for renewing the discussion.
Agile Methods for Large Organizations - Building Communities of Practice
TLDR
Three agile methods developed at Nokia that use facilitated workshops to solve multiteam issues are studied to suggest that workshop practices that amass people from different parts of organizations to perform a specific well-defined task can be used effectively to solve issues that span over multiple teams and to build up communities of practice.
How extreme does extreme programming have to be? Adapting XP practices to large-scale projects
TLDR
The key differences between agile principles proposed in prior literature and the agile practices that are suitable for large-scale, complex software development are highlighted and general guidelines on tailoring agile development methodologies are proposed.
Get Ready for Agile Methods, with Care
TLDR
Although many of their advocates consider the agile and plan-driven software development methods polar opposites, synthesizing the two can provide developers with a comprehensive spectrum of tools and options, and a combined approach is feasible and preferable in some circumstances.
...
1
2
3
4
5
...