A DOES Journey: HPE and Urban Science – Where Are They Now?
A DOES Journey: HPE and Urban Science – Where Are They Now?
HPE’s and Urban Science’s DOES journeys are interesting because of the scale in which they operate and their approach to DevOps adoption. Read on to learn more.
Join the DZone community and get the full member experience.Join For Free
Discover how you can reduce your Kubernetes installation from 22 steps to 1.
DevOps (and in particular, DevOps in the enterprise) is a journey – one of continuous improvement, optimization, and learning. For large organizations, the journey may be more complex and tangled, more difficult at times, with more stakeholders and more at stake. However, as we’ve seen, the rewards of a successful DevOps adoption are truly phenomenal.
We know that in order for DevOps to take roots, you need to be in it for the long haul. There’s no one silver bullet or one big-bang corporate initiative (or a corporate memo) that will clean up, streamline, and accelerate your delivery pipelines in one swoop. It takes work, dedication, trial and error, and good people to share the vision and the road with.
One of the things we look forward to the most every year at DevOps Enterprise Summit (DOES), is hearing from returning speakers in charge of leading these large-scale transformations about where they are on the next step of their DevOps journey.
- What changes have they seen in their organization in the last year?
- How have they built on previous successes?
- What have they learned from past failures?
- What roadblocks do they still need to tackle?
- What are they experimenting with now, in order to solve the next DevOps challenge?
- Perhaps most interesting, how do they do all of it at scale so that the entire organization reaps the benefits of DevOps?
Hearing those DevOps transformation stories as they unfold through the years is fascinating. Not only do we get a front-row seat to the workings of another IT organization (and are able to be there with these speakers along the journey, celebrating their successes and empathizing with their challenges), but we also get to see how their experiences apply to our own path.
- What can we emulate from the patterns and processes others have tried out to streamline our own DevOps adoption?
- How can we avoid the pitfalls that these trailblazers highlighted for us along the path?
- Seeing the impact DevOps has had on their companies, what should we aspire to for ours?
This year, DOES16 sees several speakers coming back to share the next stage of their journey for the third year in a row, such as Heather Mickman from Target, Tapabrata Pal from Capital One, Carmen DeArdo from Nationwide Insurance, Jason Cox from Disney, and more.
HPE’s and Urban Science’s respective DOES journeys are interesting not only because of the scale in which they operate but also due to their strategic approach to rolling out their DevOps adoption across the organization. It’s amazing to witness the incredible results of their DevOps evolution, and for us at Electric Cloud, it is humbling to see the critical role that ElectricFlow plays for their business – supporting their DevOps automation and application release at such a large scale.
HPE’s DOES Journey
HPE started their journey with enabling their developers – by supporting the building blocks of CI and Deployments to be delivered as-a-service to their internal Dev teams. Then, they moved on to end-to-end monitoring, self healing and auto-management of these complex applications, environments and and processes at scale – making life easier for both Dev and Ops.
HPE shared their story around enabling Continuous Integration as a centralized service using ElectricFlow.
This self-service, highly-available, centralized, build-test-deploy solution is used by 3k+ developers across nine regions, running 1,000,000+ jobs per month. On their talk, HPE provided a step-by-step blueprint for implementing CI-as-a-Service in your organization on a large scale, including HA, robust security and access control topology, procedures for creating baseline artifacts (resource, workspace, gateway, project, zones, etc.), environment cleanup, shared processes for easy on-boarding and reuse, and more.
HPE shared the next stage of their journey towards end-to-end application monitoring and self-healing in a DevOps world.
With integrated pipelines, open-source monitoring solutions, and reproducible APIs, HPE achieved end-to-end monitoring and automated self-healing of complex applications. Self-healing, alongside investment in accelerated deployment strategy across all applications further bridged the gap between Dev and Ops, with greater visibility and in-depth insight into all environments and auto recovery of failures. This was also HPE’s initial investments in ChatOps for increased visibility, collaboration, and self-managing operations.
Coming up at DOES 2016: Doubling Down on ChatOps in the Enterprise
This year, HPE will discuss the proliferation of ChatOps within the organization. Daniel Perez, Build and Deploy Architect at HPE, will discuss the decisions that lead them to these investments, the key lessons learned, and the scale at which their ChatOps operate, and also provide their open-source repo for various ElectricFlow and Hubot integrations and capabilities.
Urban Science’s DOES Journey
Urban Science is one of the key players in the automotive industry that you may not have heard of. As a global automotive retail performance expert, Urban Science serves nearly every automotive OEM in over 70 countries. From Acura to Volvo and just about every manufacturer in between, Urban Science is finding new and innovative ways for auto companies to increase market share and improve profitability. Their goal is to identify and solve the toughest business challenges of this massive industry. They work with manufacturers to help them understand how people are buying, servicing, and using their cars. Basically, if there is any kind of statistic around the automotive industry, Urban Science is tracking and interpreting it. You can imagine the infrastructure and software updates required to support such an operation, with its demanding customers, high-stakes business, and a massive amount of data being collected from all over the world and analyzed 24/7.
Marc Priolo from Urban Science presented Vision Versus Execution – Implementing Continuous Delivery. He shared how Urban Science achieved a big Continuous Delivery win – increasing software test coverage and delivery velocity and efficiency.
Coming up at DOES 2016: “Are we there yet?” Continuous Improvement and Scaling DevOps at Urban Science
In the last two years, Marc’s team has been busy scaling DevOps, Continuous Delivery, and Lean principles across teams and practices throughout Urban Science. This rollout included implementing a centralized, shared, self-service Pipeline Solutions Catalog enabling teams to easily opt-in for an automated, vetted pipeline.
Marc will share learnings gathered through this experience and discuss the challenges and the value of scaling DevOps across the organization.
What makes Urban Science’s DevOps story particularly compelling are the bottom line numbers that show the exponential improvement in every possible metric (deployments numbers, ROI, release velocity, etc.) that an organization can achieve once you hit your stride and crack how to best scale your initial implementation and those early wins. (We won’t steal Marc’s thunder, so you’ll just have to attend the talk to see his pretty graphs!)
Check out all of the other great speakers and conference sessions here.
Published at DZone with permission of Anders Wallgren , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.