From the Blogosphere
DevOps Strategy Gives Grocery Retailer Food for Thought | @DevOpsSummit #DevOps #ContinuousDelivery
Learn how this retailer cuts deployment error rate from 50% to almost zero by adopting DevOps practices
By: Automic Blog
Jul. 7, 2017 02:00 PM
DevOps Strategy Gives Grocery Retailer Food for Thought
Retailers are witnessing a rising trend towards customers ordering food online and requesting hybrid delivery, such as home delivery, picking up from stores or dedicated pickup points. In light of this and other emerging innovations, retailers need to develop and deploy new applications quickly to support new customer-oriented services that maximize user convenience. If they fail, customers will turn to competitors offering the service capability they want and likely never return.
In this case study, we demonstrate how a major grocery and non-grocery retailer is being impacted by the digital economy, and how DevOps has come to the rescue to deliver faster release cycles, business growth, and increasing customer loyalty.
Situation Before DevOps
There are challenges in development too. The grocery retailer has ten development teams in different locations and from different vendors. Initially, most teams applied some form of SCRUM, but there were no synchronized sprints and the output of sprints was not stable. Moreover, each sprint had to go through complete unit test, system test, and system integration test with partial and full regression. Sometimes it took several weeks before all systems were working in an integrated scenario after a sprint and BEFORE tests could even be started. Test cycles through ST and SIT took one month.
Release deployments were complex as well, requiring 16 hours and four hours of downtime owing to complex dependencies. Some 50% of deployments also had problems related to mistakes in manual steps such as application or environment configuration. As a result, the total release cycle time from demand to production was approximately six months (with about two months of development). Environment provisioning took several months and consequently environment congestion slowed down releases and caused a cascade of delays.
Scope of the Project
Latest AJAXWorld RIA Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week