Mastery of software development and software deliveries has become the foundation of successful projects in automotive. How fast new innovations can be deployed to cars in the field largely depends on the development methodology. Automotive is more and more embracing know-how from other domains and particularly interested in leaving traditional process models. However, automotive requirements don’t make it a straight forward exercise to apply agile methodology successfully. This presentation will give some insight into how we structure large-scale projects, how we deal with the complexity and where this journey might take us.

The era of big upfront design has passed, we live in a world with a high degree of volatility in software. A new term has recently coined out: "evolutionary". During our session, we will share guidelines and tactics in order to design and protect an evolutionary architecture in agile environment. Nowadays, the Architect role seems blurry in light of Agile environments, especially due to Agile Manifesto Principle #11 which states “best architectures […] emerge from self-organizing teams”. On the other side, the business driver wants the product to be delivered on time, to be flexible, extensible, modifiable and easily maintainable. In regards to that blending Agile and Architecture in most of the projects is not an easy task, especially when the focus is towards delivering functionality and less on internal product quality.