“What room for manoeuvre do you have in your projects to try out other approaches and to consciously take new, easy paths? To what extent do companies give project managers, scrum masters and product owners as well as consultants a free hand in the choice of procedure, in project planning, communication or in the type of cooperation in the team (keyword self-organization)? And with what approaches do you succeed?” This is what the project magazine asks in the latest blog parade with the topic“More success through new freedoms in the project“.

I am happy to participate in this blog parade and answer the questions asked from my point of view. I am part of a team (with 5 people) that provides infrastructure services for a major customer. The product is a mixture of hardware and software such as a car, aircraft or an ICE. In order for the customer to remain anonymous, I do not elaborate on the product. It is important that a product is produced (hardware) that communicates with various IT systems via IT infrastructure and maps special use cases for the user. “A use case is a use case and bundles all possible scenarios that can occur when an actor tries to achieve a specific technical goal with the help of the system under consideration” (Source: Wikipedia).


One day, our customer demanded that we more agile from now on and the various service providers become more networked. He suggested the Scrum of Scrums method. The idea was that we on the one hand, work with the same software (Jira – software for the and project tracking) and, on the other hand, regularly cross-service providers Exchange. We are a total of four service providers in the project, which until 12 months have worked side by side rather than together:

  • IT infrastructure service provider (we)
  • IT software service providers
  • Hardware
  • Business Consulting

Scrum of Scrums: short and concise

I have already described the method behind Scrum of Scrums in detail in my article on scaling Scrum, so I will only briefly outline it here: The simplest approach to scaling Scrum is Scrum of Scrums. Imagine a project with six teams. Each team, in turn, consists of 8 team members. All teams hold their own Daily Scrum Meeting. Subsequently, further (comprehensive) scrum teams are formed, each consisting of a representative of the six teams and meeting weekly.

Scrum of Scrums in practice

In our project, each service provider has its own Team that works according to the classic assignment of the customer. In doing so, as an outsourcing service provider, we use our own tools and Ways. We used to contact one or more contact persons of the customer about the tasks. Due to the new Scrum of Scrums we now work together in a networked agile and together.

Scrum of Scrums in our project

In the first step, we have jointly who needs to work closely with whom? The first result was the Collaboration between hardware and business consulting. This was important because especially the hardware can be changed difficult during the course of the project and for a series production, the use cases of the specialist department are must be voted on. In terms of content, the meeting usually revolves around the Technical concept.

Subsequently, as an infrastructure service provider, we the task of adapting our servers and virtual environments to new hardware Adjust. In this process, the hardware manufacturer agrees extensively with in another meeting. Content here is usually the technical Implementation of use cases.

Finally, there is another round of consultation with the IT software service providers in which software and operating topics are clarified (DevOps). DevOps is an art word from the terms development and IT operations and denotes a process improvement approach. To ensure that requirements are not misunderstood, a representative from the business team is often also present at the meeting. There is no need to coordinate software and hardware because we have virtualized the environments to the extent that it is not important for the software manufacturer which hardware is used.

Due to the contractual situation, service providers must continue to be controlled by the customer. For this reason, each circle in the second level, a dedicated contact person of the customer as organiser and Scrum Master. We work together on a Jira board of the customer, which synchronizes with our internal ticket systems.

A meeting in each week is also held in of the overall round. In doing so, the representatives of the district report as a representative of each service provider discusses the overall progress and discussthes the overall Questions. All contact persons and decision-makers of the customer are also invited to this weekly meeting. The central element is a Jira Board with Epics so that everyone can get a quick overview. An Epic is short said a major task (e.g. setting up a webshop) that would be included in other subtasks (Securing a domain, installing a webshop system, etc.) Structured Is.

Implications for collaboration and success

This new way of working has improved cooperation on complex product issues, which can only be handled by several experts. The cohesion and fun in the project have also greatly increased, as well as the loyalty to the customer as well as the commitment to the product. In order not to violate guidelines, each meeting and each circle is conducted by a special contact person of the customer. It took us just under a year to establish the way we work and always had the full support of the customer’s management.

In my experience, clients nowadays are not only open to new approaches, they are often even so familiar and know what they want that they themselves ask the contractor to use certain methods. What experiences have you learned? Join the blog parade with your experience!

Genderhinweis: Ich habe zur leichteren Lesbarkeit die männliche Form verwendet. Sofern keine explizite Unterscheidung getroffen wird, sind daher stets sowohl Frauen, Diverse als auch Männer sowie Menschen jeder Herkunft und Nation gemeint. Lesen Sie mehr dazu.

Falls es noch Fragen gibt, können Sie mich gerne anrufen. Hierzu einfach im Buchungssystem nach einen freien Termin schauen. Ich nehme mir jeden Monat einige Stunden Zeit um mit Lesern zu interagieren.

Helfen Sie meinem Blog, vernetzen Sie sich oder arbeiten Sie mit mir

Sie haben eigene, interessante Gedanken rund um die Themenwelt des Blogs und möchten diese in einem Gastartikel auf meinem Blog teilen? – Aber gerne! Sie können dadurch Kunden und Fachkräfte ansprechen.

Ich suche aktuell außerdem Werbepartner für Bannerwerbung für meinen Blog. Sollte es für Sie spannend sein Fachkräfte oder Kunden auf Ihre Seite zu leiten, dann bekommen Sie mehr Informationen hier.

Vernetzen Sie sich in jedem Fall auf Xing oder LinkedIn oder kontaktieren Sie mich direkt für einen Austausch, wenn Sie gleich mit mir ins Gespräch kommen wollen. Werfen Sie auch einen Blick in meine Buchvorschläge zur Digitalisierung, vielleicht wollen Sie mir auch ein Buch empfehlen?

Ich arbeite gerne mit Unternehmen zusammen. Sie können mich ebenfalls gerne bezüglich folgender Punkte anfragen:


I blog about the impact of digitalization on our working environment. For this purpose, I present content from science in a practical way and show helpful tips from my everyday work. I am a manager in an SME myself and I wrote my doctoral thesis at the University of Erlangen-Nuremberg at the chair of IT Management.

Durch die weitere Nutzung der Seite stimmen Sie der Verwendung von Cookies zu. Weitere Informationen

Die Cookie-Einstellungen auf dieser Website sind auf "Cookies zulassen" eingestellt, um das beste Surferlebnis zu ermöglichen. Wenn du diese Website ohne Änderung der Cookie-Einstellungen verwendest oder auf "Akzeptieren" klickst, erklärst du sich damit einverstanden.