Author:
Peter Faßbinder
Affiliation:
Siemens AG, Germany
Keyword(s):
Agile Development, Large Systems, “Hybrid” Projects, Agile Requirements Management, Agile Testing, Agile Roles, Process Integration, Tailoring Concepts, Industry Experience.
Related
Ontology
Subjects/Areas/Topics:
Agile Methodologies
;
Service-Oriented Software Engineering and Management
;
Software and Systems Development Methodologies
;
Software Engineering
;
Software Process Improvement
;
Software Project Management
Abstract:
Ten years after the publication of the agile manifesto, the following statements still hold true: Defining an agile development process for a small co-located software team is straight forward; there are many theories, models and examples for this. However, integrating agile development into an overall standard process of a complex organization, that includes hardware and system development, and has large distributed projects, is still a major challenge: How do you integrate the agile development approach into the standard process? How much agility do you have to abandon to satisfy the boundary conditions of such an environment? What is the ideal process architecture to address the needs of the different project types? What compromises do you have to accept and where are the limits that you should not cross? This work provides possible answers to these questions, and describes suitable approaches to address the three key challenges faced when integrating agile development into a stan
dard system development process. The results are based on experiences from many agile implementation projects within the Siemens AG.
(More)