New techniques and technologies, such as microservices, containers, and Kubernetes are enabling developers to deliver and change code faster.  However, there is no silver bullet - failures still happen, and they can happen at any stage of the application lifecycle. Planning for these failures is a key aspect to ensuring you keep your applications (and your business) running smoothly. In this session we'll explore planning for failures across the application lifecycle: Minimise deployment failures with automated deployment "Shift left" with automated testing and lessen the impact of each code issue Recognise failures quickly with effective monitoring React and quickly remediate failures via Incident management

1. DevOps
- Succeed by Planning for Failure

2. James Moore
Principal Offering Manager, IBM
Charlene O’Hanlon
Managing Editor, Devops.com
Charlene O’Hanlon
Managing Editor, Devops.com
James Hunter
Program Director, IBM
Speakers

3. increased deployment frequency increased
revenue
Faster lead time and repairs
A Mariner 1 spacecraft bug cost $18M
Amazon could lose $1.6B every year if they
slowed down by just one second
3
Sources:
• Continuous Delivery: A Maturity Assessment Model, ThoughtWorks
• https://www.bitcatcha.com/blog/2015/6-reasons-why-website-speed-matters-how-amazon-would-lose-1-6-billion-if-it-slowed-down/
• 2017 State of DevOps Report
The bottom line

4. DEPLOY
OPERATE
DEVELOP

5. AUTOMATE
TRACK
COLLABORATE

6. Accelerating delivery
Development SCM Build Package
Repo
Deploy Test Stage Production
… what could possibly go wrong?

7. Transformation is a journey
Plan and deploy
Draft a cloud-native
transformation strategy
Adopt
Enablement on agile DevOps
with microservices
Refractor
Migrate Extend
Scale
Deploy and start to
manage cloud environment
Refractor monolithic
applications
Build MVP
Initiate net new
cloud-native apps
Custom and commercial
off-the-shelf (COTS)
on-premises applications
Modern language
applications
Leverage high-value APIs and expose existing
services to new applications and business models
Leverage a global cloud
footprint for its elasticity and
client’s economic advantage

8. DevOps
Breaking
down walls
Dev SecBiz
Agile Dev
fixes this
DevOps
fixes this
DevSecOps
fixes this
Ops
Requirements Code Security
… in a multi-speed IT world

9. In production: scale and perform …
… amidst constant change & failures
Monitoring

10. IBM Event & Incident Management – Detect, Prioritize & Resolve
Chat
Resolved
SM
S
Chat
e-mail
Incident
Chat
Run
Rollback
Run
App
Check
All good!
Escalate
App owner
Operator
App owner
SRE
Run Books
Notification
It’s a config issue.
Let’s roll it back.
My App is
Unresponsive!
Service x is
impacting our
Biz Critical App!

11. IBM Operations Management – Monitor and Manage
11
üExpedite problem determination
üRestore service quickly
üAnalyze and improve operational health
üBridge the gap between Dev and Ops
Consolidated monitoring, event and incident correlation, prioritization and resolution
• 95% faster time to acknowledge incidents
• 75% less time performing event investigation
• 50% fewer repeating events
• 50% fewer generated incidents
IBM’s Operations Management track record sets the bar:
• 30% faster incident resolution
• 75% fewer events presented to operators

12. DevOps is no longer optional

13. IBM Cloud DevOps
for Hybrid
Deployment
IBM Cloud
Management for
Hybrid Deployment
IBM Cloud Application
Platform for Hybrid
Deployment
DevOps

14. Continuous
Testing
Collaborative
Development
Accelerating delivery
Continuous
Delivery
Continuous
Integration
Development SCM Build Package
Repo
Deploy Test Stage Production

15. Development SCM Build Package
Repo
Deploy Test Stage Production
IBM Rational IBM UrbanCode
IBM Cloud Event
Management
IBM Velocity
IBM Cloud
Application
Performance Mgt
IBM Cloud Event
Management
IBM capabilities

16. Examples in practice
Rabobank creates exceptional customer experiences
and a competitive advantage, by delivering a single
360-degree view of clients for more personalized
service with IBM DevOps.
Fidelity avoided more than $2.3 million
per year in costs on a single application.

17. • Crypto-anchors and blockchain
• Lattice cryptography
• AI powered robot microscopes
• AI bias will explode
• Quantum computing will be mainstream
Learn more at: research.ibm.com/5-in-5
Planning for failure doesn’t stop
… what could possibly go wrong … again?

18. IBM DevOps helps project teams deliver reliable
software as quickly as possible and identify and
resolve problems as quickly as possible during
runtime.

19. James Moore
Principal
Offering
Manager, IBM
Charlene
O’Hanlon
Managing
Editor,
Devops.com
James Hunter
Program
Director, IBM
Request a no charge
DevOps assessment
https://bit.ly/2Nt1yDv
Learn more Visit our website: https://www.ibm.com/cloud/devops
Watch videos: https://bit.ly/2oSWpGU
Connect with us James Hunter - linkedin.com/in/mrjameshunter
James Moore - linkedin.com/in/james-moore-7a04775

20. Questions
Request a no charge
DevOps assessment
https://bit.ly/2Nt1yDv
Learn more Visit our website: https://www.ibm.com/cloud/devops
Watch videos: https://bit.ly/2oSWpGU
Connect with us James Hunter - linkedin.com/in/mrjameshunter
James Moore - linkedin.com/in/james-moore-7a04775

21. © Copyright IBM Corporation 2018. All rights reserved. The information
contained in these materials is provided for informational purposes only, and
is provided AS IS without warranty of any kind, express or implied. Any
statement of direction represents IBM's current intent, is subject to change or
withdrawal, and represents only goals and objectives. IBM, the IBM logo, and
other IBM products and services are trademarks of the International Business
Machines Corporation, in the United States, other countries or both. Other
company, product, or service names may be trademarks or service marks of
others.

22. Thank you