Agile software development is a light framework that focusses more on early value delivery and incremental improvement than traditional tasks like detailed up-front planning, comprehensive specifications and technical documentation. But from the perspective of regulatory compliance, this planning and documentation serve a purpose. How can we reconcile agile approaches that value a working product over documentation with the need to meet regulatory requirements for, e.g. medical devices or telecommunications? I will discuss how to bring together the apparently conflicting needs of regulatory compliance and agile, and show by example how agile teams actually approach tough regulatory requirements in finance, healthcare and telecommunications.
- How to use agile in a highly-regulated environment
- How to incorporate strict regulatory requirements within an agile development approach
- The power of agile as a risk-limiting software development approach