Scaled Agile Framework (SAFe)

SAFe and the reality of Software architecture development in the automotive industry

Download the paper

Avant de remplir le formulaire d'inscription, veuillez lire le Privacy notice conformément à l'article 13 du règlement UE 2016/679

entrée non valable
entrée non valable
entrée non valable
entrée non valable
entrée non valable
entrée non valable

Privacy


Je déclare avoir lu et pleinement compris la note d'information sur la protection des données personnelles Privacy Notice et j'exprime par la présente mon consentement au traitement de mes données personnelles par Reply SpA à des fins de marketing, en particulier pour recevoir des communications promotionnelles et commerciales ou des informations concernant des événements ou des webinaires de l'entreprise, en utilisant des moyens de contact automatisés (par exemple, SMS, MMS, fax, e-mail et applications web) ou des méthodes traditionnelles (par exemple, appels téléphoniques et courrier papier).

What is Scaled Agile Framework and why should i care ?

Discover how SAFe can offer many benefits for software architecture development in the automotive industry


Software architecture development in the automotive industry is a complex and challenging process. It requires collaboration between multiple teams and stakeholders, adherence to automotive industry regulations and standards, and the ability to deliver high-quality products within tight timelines. In recent years, many automotive companies have turned to SAFe (Scaled Agile Framework) to improve their software architecture development processes. While SAFe offers many benefits, it’s important to recognise that there are also some challenges that need to be addressed.


One of the biggest challenges of using SAFe in software architecture development is the difficulty with sticking to commitments. SAFe emphasises continuous feedback and iterative development, which can result in changing requirements and priorities. This can make it difficult to deliver products on time and within budget, which potentially impacts customer satisfaction and overall project success. Another challenge is do with aligning software development with hardware development.

SAFe places a strong emphasis on software development, but in automotive engineering it’s equally important to ensure that software development aligns with hardware development. In some cases, the SAFe process may not be optimised for hardware development, which can lead to delays and misalignment between software and hardware.

In addition, using SAFe may not address all domains adequately, for example, domains, such as cybersecurity and safety may require specialised expertise that may not be easily incorporated into the SAFe process.

This can result in overlooking critical requirements that may put the final product at risk. Moreover, while SAFe promotes collaboration, this can result in teams struggling to work together effectively.

Different teams may have different goals, priorities, and ways of working, which can lead to conflicts and communication breakdowns. This can ultimately impact the quality and timeliness of the final product. Despite these challenges, many companies have successfully used SAFe to improve their software architecture development processes.

By adopting SAFe, companies have increased collaboration, improved the quality of their products, and delivered value to their customers. However, it's important to recognise that SAFe is not a one-size-fits-all solution. Companies need to carefully consider their specific needs and challenges when implementing SAFe so they can achieve the best possible outcomes.

Conclusion

In conclusion, SAFe can offer many benefits for software architecture development in the automotive industry. However, it’s important to recognise that there are also challenges and drawbacks that need to be addressed. By carefully considering the realities of software architecture development and adopting SAFe in a thoughtful and strategic manner, companies can achieve better outcomes and deliver high-quality products that meet the demands of today's customers.


  • strip-0

    Within the Reply Group, Autonomous Reply is the specialist in the specification, development, integration and validation of autonomous and connected embedded systems. We offer a portfolio of services covering the entire value chain, from strategy definition to implementation and operational safety. Autonomous Reply's services include consulting, real-time systems engineering, software development and integration of autonomous solutions.