In today's software development, especially in the automotive sector, two approaches are often contrasted: ASPICE and Agile. This question often comes up in assessments and meetings: "Can ASPICE and an agile approach harmonize with each other?"
Or are Agile and ASPICE as different as oil and water?
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
At first glance, ASPICE and Agile might appear to be two diametrically opposed approaches. ASPICE is a strongly process-oriented model that focuses in particular on quality assurance in software development, while agility stands for flexibility and rapid iterations. However, this black-and-white view falls short.
Automotive SPICE® is not tied to a specific development method. In practice, many projects in the automotive industry use a hybrid approach that combines the classic waterfall model with agile methods. In fact, the agile principles as defined in the Agile Manifesto can also be integrated into ASPICE-compliant processes.
Automotive SPICE® (ASPICE)
ASPICE stands for "Automotive Software Process Improvement and Capability dEtermination " and is a process model designed to ensure the quality of software development processes in the automotive sector. It provides a systematic basis to:
Agile methods, as described in the Agile Manifesto, focus on
The two best-known agile frameworks are:
At first glance, ASPICE and Agile have different focuses, but this does not mean that they are at odds with each other. In fact, there are many overlaps in their objectives - namely the efficient development of high-quality software.
Different strengths
Both approaches can complement each other in a project to ensure both quality and efficiency.
Despite the many synergies, there are also challenges when trying to combine both approaches:
In the automotive sector, development cycles are often characterized by prototypes such as A-samples and B-samples. Too frequent deliveries are uneconomical here, as prototypes are expensive and time-consuming. The agile idea of regular delivery can therefore be difficult to implement. This is where hardware-in-the-loop (HIL ) and software-in-the-loop (SIL) offer a solution to simulate development increments and perform tests without the need for expensive physical prototypes.
The second principle of the Agile Manifesto emphasizes that changes to requirements are welcome even late in the project. In ASPICE, this is also a topic that is dealt with in the SUP.10 Change Request Management process. However, changes must be analyzed and approved in detail, which can limit flexibility.
Agile development teams often work in short sprints, while ASPICE-compliant projects tend to follow long-term milestones and project plans. The challenge lies in combining both schedules without unnecessarily slowing down either system.
A practical example shows how hybrid approaches can overcome these problems. Many companies use agile frameworks such as Scrum for software development, while the overarching framework is controlled by ASPICE. Here, release plans are often used to determine which functionalities are to be implemented in the various prototype phases (e.g. A-Sample, B-Sample).
In these phases, the features to be developed can be divided into smaller, manageable packages that agile teams implement in sprints. In this way, the granularity of the work steps is adapted to the agile approach, while the traceability and process quality of ASPICE are maintained.
A pioneering approach is Agile SPICE™, a process reference model that facilitates the use of agile practices within an ASPICE framework. Agile SPICE™ helps to combine agile methods with the strict requirements of the Automotive SPICE® standards without losing the basic process attributes. This allows agile practices to be seamlessly integrated into the assessment according to ASPICE criteria.
The question of whether ASPICE and Agile go together can be answered clearly: yes, they can complement each other perfectly in the right context. However, it is important that the teams harmonize well and that the right processes are selected for the respective project.
ASPICE helps to manage the complexity of automotive development, while Agile allows you to react quickly to changing customer requirements. Combining both approaches is not a technical challenge - it is rather up to those involved whether they are prepared to live this synergy.
The message is clear:
ASPICE and Agile can not only coexist, but complement each other in order to remain competitive in a dynamic market.
You are currently viewing a placeholder content from OpenStreetMap. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
You need to load content from hCaptcha to submit the form. Please note that doing so will share data with third-party providers.
You are currently viewing a placeholder content from Google Maps. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.