Set up agile framework
In addition to classic project work according to the waterfall model, agile methods are increasingly gaining acceptance. Iteration, rapid feedback between project teams, users and external partners, and a more active role for developers lead to greater efficiency, better results and greater acceptance in the agile approach. The following agile frameworks are currently relevant in the industry.
Team level: Scrum, Kanban, hybrid forms, DevOps, OKR, design thinking
Scaled deployment: SAFe, Scrum@Scale, LeSS, Scrum of Scrums
Agile working requires a culture of corresponding values and principles in which employees can develop their potential.
Reach your goal quickly with agile methods
Because of its highly complex product development, manufacturing and marketing, the automotive industry has always been crisis-prone. Digitization, electromobility, stricter legal requirements and new competitors, some of whom act as partners and others as rivals, require fast, sometimes unconventional responses. Agile process models are designed precisely for such confusing, changeable situations. Based on a deeper understanding of the target groups, agile teams take responsibility for the product, implement customer needs promptly, and overcome organizational hurdles and silo thinking.
How to make the switch
For more than a decade, our coaches have been supporting companies in various industries in their transition to agile working – not only in IT, but also in core departments such as procurement, production or sales. Many companies have already tested agile process models in IT projects. The success has convinced many so much that they want to extend the working method to the core business. A three-phase approach has proven successful in the software product cycle.
To break out of old thought patterns and focus more on what customers want, the agile teams work with approaches such as the customer journey or design thinking at the beginning of the project. Already, the developers are involved. Consileans versed in creativity techniques, team building and agile principles accompany this stage as coaches.
In the second phase, the actual product development begins. We recommend a test-driven development (TDD) approach here. By far the most common agile framework is Scrum. For larger projects, it is worthwhile to use a scaling model such as SAFe, Scrum@Scale or Scrum of Scrums. If work is to be done with DevOps, the preliminary work for this now needs to be done. The coaches train the project teams for this. Priority is given to deepening the developers’ knowledge of the customer, for example through shadowing, as well as the training and continuing education of product owners, Scrum masters and managers.
In phase three, the teams iteratively build out the product in intervals of a few weeks, called sprints. Here, the focus is on collaboration between the developers and the subsequent administrators. The coaches accompany the introduction of DevOps. The focus is on opening up organizational silos, promoting collaboration among the teams and integrating their work results.