According to a leading automotive manufacturer, only about 15% of software vendors achieve Automotive SPICE Level 1 immediately, and only about 3% achieve Level 2.

There are many reasons for this. One important reason is certainly a discrepancy between documented software development processes and the agile approach to software development that is often used in real-world projects.

Many software developers prefer an agile way of working but are not familiar with the process requirements in the automotive industry and Automotive SPICE, while many documented software development processes are comprehensively structured but do not provide sufficient flexibility for software development in a rapidly changing environment.

This agile project model brings both positions together by maintaining the agile work approach at the detailed and adding a comprehensive but flexible and iterative project management structure that meets the expectations of an ASPICE-compliant project implementation while still being easy and efficient to manage.

This is achieved through a SAFe approach by adding work products, reviews and other process requirements required by Automotive SPICE to the SAFe structures.

The project model can be easily adapted to differently structured customer projects. Process extensions for different project situations and standards such as ISO 26262 or ASPICE Cybersecurity Engineering (ISO 21434) are available or can be easily added.

The project model is designed in such a way that it can be implemented with current project management and engineering tools such as Confluence, JIRA and Codebeamer etc.

Has the process model proven itself?

 

The process model is based on the experience of many consulting projects at automotive OEMs and automotive suppliers. It combines best practices from different models and development approaches into an independent process model that translates the requirements for agility and flexibility into a comprehensible and efficient model while adhering to the structures required by Automotive SPICE.

 

Basic concepts like the project execution strategy (see below) and a built-in QA concept have been implemented at a company for the development of automotive audio technology and have proven its practicability and efficiency in software development projects.

 

A leading German engineering R&D services provider  with over 2,000 employees has decided to implement this process.

 

The main reasons for the decision were the flexible adaptability to customer projects, the acceptance by the software developers, the complete coverage of Automotive SPICE Level 2 as well as the possibility to easily implement the process with current tools such as Confluence, JIRA, Codebeamer, etc.

 

How can I support you as an external consultant?

 

• Provision of the complete process description as a PDF file (approx. 400 pages) or as an import file for Confluence.
• This process description may serve as a example and reference for improving your own process but can also be adopted and adapted entirely.
• Provision of a set of tasks (Masterboard) for all project phases as import file for JIRA (all tasks except of product implementation tasks), this needs some adaptations.
• Support for implementation and customization in your company.

 

For more information please request the White Paper and contact: info@fuchsberger.consulting

 

 

 

Project Execution Strategy

Process Characteristics

• Flexible project execution strategy
• Complete set of work product descriptions, prepared as Master Boards for each project phase
• Role descriptions for agile/conventional role setup and for small and medium size projects
• Built-in QA concept
• Review concept and review criteria for all processes
• Metric definitions for all processes
• Guidelines/templates for many project situations
• Workflow descriptions for support processes, risk management, requirements management
• Process extensions (work products) for supplier management, requirements elicitation
• Support for functional safety and cybersecurity
• Compliant to ASPICE Level 2, prepared for Level 3
• Easy to implement with current tools
• Reference list for ASPICE 4.0, ASPICE Guidelines 2.0, Agile SPICE, ASPICE for Cybersecurity Engineering
• This project model is a ASPICE compliant extension to SAFe.