Many organizations have adopted DevOps to accelerate software delivery and drive innovation, but scaling pilots up to full enterprise implementation remains a challenge. Join us for a panel discussion with Mark Peterson, SVP of Platform Service Architecture, Wells Fargo, Chris Nowak, CTO, Kingsmen Software and Sanjeev Sharma, Distinguished Engineer, IBM as they share their unique challenges and best practices in scaling-up DevOps adoption as well as steps you can take now to assess your own organization’s readiness.

1. Lessons Learned: Scaling DevOps @
Wells Fargo and Kingsmen Software
December 7th 2017

2. Speakers
Alan Shimel
Moderator, Editor-in-
Chief, DevOps.com
Mark Peterson
Senior Vice President
Platform Service
Architecture,
Wells Fargo
Chris Nowak
Chief Transformation
Officer, Kingsmen
Software
Sanjeev Sharma
CTO, DevOps Adoption,
IBM Distinguished
Engineer, IBM

3. Decouple application complexity
12 factor applications; Micro-
service architecture; Release
independently; Strangler
pattern
Decrease scope of release
Deliver minimal viable product;
Release new features more
frequently
Embrace modern technologies
Cloud (public &
private); Docker;
Kubernetes
Automate optimized processes
Continuous Integration; Continuous Delivery; Continuous
Testing; Continuous Monitoring
Development SCM Build Package
Repo
Deploy Test Stage Production
DevOps addresses a Business Problem: Time, Money, Quality

4. Idea/Feature/Bug Fix/
Enhancement
Production
Development Build QA SIT UAT Prod
PMO
Requirements/
Analyst
Developer
CustomersLine of Business
Build
Engineer
QA Team Integration Tester User/Tester Operations
Artifact Repository
Deployment Engineer
Release Management
Code Repository
Deploy
Get Feedback
Infrastructure as Code/
Cloud Patterns
Feedback
Customer or
Customer Surrogate
Metrics - Reporting/Dashboarding
Tasks
Artifacts
How long does a task take?
- In process vs. wait time?
What artifacts are being shared?
- Do they deliver value?
DevOps: Optimizing end-to-end delivery processes

5. Your Delivery Pipeline
will be as fast as the
slowest Delivery Pipeline
it is dependent on
Technical Debt and Process Debt

6. Developers are paid to
write code, not maintain
deployment and
configuration scripts
Deployment Automation

7. You are doing 2-week
Sprints, but it takes 3-
weeks to get a Test
Server, how long are
your Sprints?
Removing the Dev and Ops Silos

8. Moving from MTBF
to MTTR
Service Availability and Reliability is everyone’s responsibility

9. ibm.biz/devopslibraryibm.biz/devopsplaybook
IBM’s DevOps Library

10. Thank You!!!