Extreme programming explained: embrace change
Extreme programming explained: embrace change
Qualitative Methods in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Software Verification and Validation for Practitioners and Managers, Second Edition
Software Verification and Validation for Practitioners and Managers, Second Edition
The Rational Unified Process: An Introduction, Second Edition
The Rational Unified Process: An Introduction, Second Edition
Agile Software Development with Scrum
Agile Software Development with Scrum
Computer
IEEE Software
Lean Software Development: An Agile Toolkit
Lean Software Development: An Agile Toolkit
How Extreme Does Extreme Programming Have to Be? Adapting XP Practices to Large-Scale Projects
HICSS '04 Proceedings of the Proceedings of the 37th Annual Hawaii International Conference on System Sciences (HICSS'04) - Track 3 - Volume 3
Generalizing Generalizability in Information Systems Research
Information Systems Research
Who Is Liable for Insecure Systems?
Computer
Agile Methods for Large Organizations - Building Communities of Practice
ADC '04 Proceedings of the Agile Development Conference
Ahaa --agile, hybrid assessment method for automotive, safety critical smes
Proceedings of the 30th international conference on Software engineering
Coevolving Systems and the Organization of Agile Software Development
Information Systems Research
Agility and Architecture: Can They Coexist?
IEEE Software
Agile methods for open source safety-critical software
Software—Practice & Experience
Software and Systems Traceability
Software and Systems Traceability
Using a protocol template for case study planning
EASE'08 Proceedings of the 12th international conference on Evaluation and Assessment in Software Engineering
| Hi-index | 0.00 |
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 methods for developing safety-critical systems in regulated environments has not yet been demonstrated unequivocally, and very little rigorous research exists in this area. Some of the essential characteristics of agile approaches appear to be incompatible with the constraints imposed by regulated environments. In this study we identify these tension points and illustrate through a detailed case study how an agile approach was implemented successfully in a regulated environment. Among the interesting concepts to emerge from the research are the notions of continuous compliance and living traceability.