by Christian Glück

Mobility is on the rise, as well as digital traffic and the need for customer-oriented solutions. Therefore, companies look for ways how to keep on track. However, the bigger the company the more difficult it may get to become agile – especially if an organisation was not organically “raised” functioning agile.

“There are many ways leading to Rome”

With the delivery of projects – software delivery projects, but now more often also other types of projects – enterprises have to choose which methodology to follow. On the team level, there is a variety of them one can apply, be it Scrum, Kanban or the standard Waterfall method. On the Enterprise level, there is also a variety one can follow – like LeSS, Nexus(TM) or the Scaled Agile Framework® (SAFe®). SAFe can still be combined with, e.g., individual teams operating in Scrum or Kanban. Therefore, it can be seen as a tool coordinating the collaboration between various teams.

Let us deal with the question for whom this framework is the right thing. But first of all, let us take a look what SAFe actually is.

The definition. And the challenge.

Putting it in simple language, when attempting to spread collaboration beyond multiple company layers, SAFe offers you a helping hand for doing so. It’s a blueprint explaining the way how to start with agile at a company level that is not used to agile functioning. It provides a set of explicit principles available and visible to everyone in the organisation – and most importantly, these principles and rules are the same for everyone. The main difference to the other agile methods is that SAFe is more formal; the entire framework is described for all levels so that there is little left to be organised by oneself.

The challenge for long-established companies is the mindset.

The principle is to prioritise tasks in the backlog on an objective and transparent basis. Transparency and a synchronized execution on all levels is actually the biggest advantage of SAFe. The entire company is working towards a common objective. There are tasks to be completed in a backlog. Each task gets a transparent priority and therefore, on an objective basis, everybody knows what task to fulfil first. This goes hand in hand with raising efficiency as the backlog carries the objective truth.

For whom is SAFe suitable?

In general, everyone having several teams can apply the SAFe methodology, but it’s most suitable for teams with above 50 members. The distinguishing factor is how innovative the company is, because SAFe is rather unsuitable for highly innovative companies like Amazon or Netflix that grew up with the agile mode of working. For them, the strong framework could be rather limiting. Taking it from the opposite end, the methodology is fitting for companies that are not too acquainted with working in the lean and agile mode.

Are you considering SAFe-based solutions tailor-made for your needs?

We hold the Scaled Agile® Silver Partner Status, enabling us to apply SAFe in our consulting services and to provide SAFe Training. Our more than 20 certified “SAFe Agilists” as well as ca. 10 SAFe SPCs (SAFe Program Consultants) can assist you in introducing SAFe at your company via consultancy or training.

My second article out of the series will be dealing with the topic of how an enterprise can become a lean and agile organisation embracing the basic principles of SAFe.

About ERNI

At ERNI, we believe in the impact of Swiss Software Engineering to create value for customers. Our mission is to boost people and businesses in the innovation of software-based products and services. Therefore, we are building a global platform based on a Swiss mindset and adapted to the needs of local customers.

Consensus building with a focus on time and quality is our mostly valued contribution in software engineering.


News from ERNI

In our newsroom, you find all our articles, blogs and series entries in one place.

  • 06.12.2023.

    Streamlining software development: The journey from multiple to unified requirements management tools

    Productivity in software development is slowed down by managing specifications across various requirements management (RM) tools. Although moving to a single, updated RM tool involves an upfront investment, the long-term benefits are considerable. These include increased process efficiency, enhanced collaboration, superior traceability, improved software specification quality, cost reductions, scalability and better integration with other RM tools, among others.

  • 22.11.2023.

    Recognising trends: An insight into regression analysis

    Data plays a very important role in every area of a company. When it comes to data, a distinction is made primarily between operational data and dispositive data. Operational data play an important role, especially in day-to-day business. However, they are not nearly as relevant as dispositive data. This is because these data are collected over a longer period of time and provide an initial insight into the history or the past.

  • 08.11.2023.

    Why do we need digital transformation for medical devices?

    For hospitals, it is not up for discussion as to whether they want to digitalise. The increasing age of the population in western countries and the progressive shortage of medical professionals mean that without digitalisation, the healthcare system will not be able to provide the quality that patients want in the future.

  • 25.10.2023.

    Mastering the challenges of mobile app testing: Strategies for efficient quality assurance

    Discover the unique challenges faced in testing mobile applications and learn how to overcome them effectively. From selecting suitable devices and operating systems to leveraging cloud-based test platforms, test automation and emulators, this article provides seven essential strategies for optimising your mobile app testing process.

  • 11.10.2023.

    Incorporating classical requirements engineering methods in agile software development for a laboratory automation system

    Traditional agile methodologies can sometimes struggle to accommodate the complexity and regulatory requirements of laboratory automation systems, leading to misalignment with stakeholder needs, scope creep, and potential delays. The lack of comprehensive requirements documentation can result in ambiguous expectations and hinder effective communication among cross-functional teams.

  • 27.09.2023.

    Unveiling the power of data: Part III – Navigating challenges and harnessing insights in data-driven projects

    Transforming an idea into a successful machine learning (ML)-based product involves navigating various challenges. In this final part of our series, we delve into two crucial aspects: ensuring 24/7 operation of the product and prioritising user experience (UX).

  • 13.09.2023.

    Exploring Language Models: An overview of LLMs and their practical implementation

    Generative AI models have recently amazed with unprecedented outputs, such as hyper-realistic images, diverse music, coherent texts, and synthetic videos, sparking excitement. Despite this progress, addressing ethical and societal concerns is crucial for responsible and beneficial utilization, guarding against issues like misinformation and manipulation in this AI-powered creative era.

  • 01.09.2023.

    Peter Zuber becomes the new Managing Director of ERNI Switzerland

    ERNI is setting an agenda for growth and innovation with the appointment of Peter Zuber as Managing Director of the Swiss business unit. With his previous experience and expertise, he will further expand the positioning of ERNI Switzerland, as a leading consulting firm for software development and digital innovation.