Kurzgeschichte zur Klärung des Warum.

Warum nutzen Unternehmen einen kontinuierlichen Softwarelieferprozess für SAP? Diese fiktive Geschichte erläutert die Gründe:

The marketing department of an organization has realized that the count of visitors on their website has been growing enormously. A new registration process should attract potential customers to submit their name and contact details and directly interface with SAP CRM©. The intend is to gain more customers and increase the revenue.

Shortly after the change request has been submitted to the development department the realization completed. After deployment into the acceptance environment the renewed registration process has to be tested. During the first test cycle an error was identified. Meanwhile the original developer was working on a different requirement which caused some lead time for the error to be resolved. Due to a manual testing process not all errors could easily be reproduced whilst others even revealed shortcomings in the applied testing procedures. Now it was time to promote the delivery into production. The production deployment was a complicated procedure. All changes that have been tested and signed-off successfully will be moved in a specific sequence during night/weekend.

During production deployment an error occured which had to be analysed by the expert team on an emergency callout. The team had a hard time fixing the problem due to complexity originating from a high number of dependencies. The next business day the environment was still not released for productive usage. At that time the team felt stressed - every minute of downtime translates into loss of revenue, not even counting the negative perception any downtime creates.

The point of no-return has been passed already - rollback to the previous stable version was no longer possible given the time needed to restore. During the day, a special task-force could finally identify and eliminate the root cause of the problem. Shortly after both the website and its SAP CRM© integration where brought to live.

The root cause analysis summerized that a configuration transport was missed for production deployment which was directly responsible for bringing CRM usage down. During the downtime of the website not a single client could register. Summerized, the envisionned process improvement painfully resulted in the opposite, sales opportunities where missed instead of created.


Maßnahmen

  • Erhöht die Frequenz der Bereitstellung
  • Neue Funktionen können bereits kurz nach dem erfolgreichen Test in der Produktion genutzt werden.
  • Zeitnahes Testen
  • Fehler werden frühzeitig erkannt und durch den verursachenden Entwickler behoben.
  • Verteilung zur Gewohnheit machen
  • Je öfter eine Tätigkeit wiederholt wird desto routinierter kann sie ausgeführt werden. CD macht sich eben diese Tatsache zu nutzen.
  • Reduktion von Komplexität.
  • Mit der Erhöhung der Bereitstellung verringert sich in der Regel die Anzahl der Transporte für den nächsten Import. Im Vergleich zu Entwicklungreleases reduziert sich die Komplexität und damit das Risiko eines Fehlers signifikant.

Vorteile

Beschleunigt Time to Market

Building the Right Product

Verbessert Produktivität und Effizienz

Verlässliche Releases

Verbesserung der Produkt Qualität

Steigert die Kundenzufriedenheit

Helfer für Continous Delivery

Softwarelogistik

Transport Center unterstützt bei der Erhöhung der Importfrequenz, durch einen automatisierten und sicheren Transportprozess.

Transport Center

Snapshot & Rollback

Falls ein Fehler passiert, empfehlen wir RE.Do mit seiner Snapshot & Rollback Funktion für SAP© Transporte.

RE.Do

Kontakt

Kontaktanfrage

Durch das Abschicken des Formulars bestätigen Sie, dass Sie unsere Datenschutzerklärung gelesen haben und diese akzeptieren.
 

Address

ABAP-Experts.com
NCMI GmbH
 Münchenerstr. 49, 85051 Ingolstadt, Deutschland
 Phone: +49 911 4902 1918