1. DevOps: Start-up Speed, Enterprise Scale

2. Bernie Coyne DevOps Evangelist IBM Cloud Unit coyneb@us.ibm.com2

3. Technology trends & market shifts forcing a different approach
Big Data 521 Million consumer transactions every day
Collaboration
60M US households conducting P2P payments
Cloud
60% of banks process most transactions in cloud by 2016
Intelligent/ Connected Systems 7.9 million in U.S. adopted NFC e-Wallets
Mobile “apps”
20% of online financial transactions originate from mobile
Innovation
Agile, Collaborative, Iterative, Secure, Intuitive
This is significant, since current technology trends have the potential to change industry landscapes by offering entirely new ways for businesses to differentiate themselves:
Mobile device proliferation: Software applications for mobile devices can enable new customer relationships, help improve loyalty, increase cross-selling and upselling, introduce new channels and enhance productivity.
Collaboration across the ecosystem: Software can connect customers, partners and employees across boundaries, enabling innovative interactions.
Explosion of unstructured data – or “big data”: Through analytics software, organizations can better interpret the mass of unstructured data to gain actionable insights and new capabilities.
Cloud platforms and solutions: Cloud solutions allow for cost flexibility and reduced fixed IT costs by offering “as needed” services. However, the benefits extend beyond IT, as an increasing number organizations are applying cloud solutions to optimize, innovate and disrupt existing business models.
Intelligent/connected systems: Here software can integrate across complex systems and physical products, creating more intelligent competitive innovations. (NFC=near field communications)
We find that software development, reflected at the bottom of the slide, plays a critical role in powering each of the above innovations. Accordingly, organizations that can more effectively manage software development are more likely to successfully implement these technologies to drive innovation, thus boosting competitive advantage.
Brett King
In an exclusive interview about his newest book, Bank 3.0, Brett King discusses how change occurring in the banking industry is inevitable, speeding up and disruptive. From the mobile wallet wars to the impact of social media, tablets and the 'de-banked' and digital consumer, Bank 3.0 shows why banking is no longer a place you go to, but something you do.
Application Maintenance
Software Development
Dev
Test
Deploy
“If it takes just months now for new emergent technologies to insert themselves into the mainstream and change behavior, and you’ve got a month development and deployment cycle (typical of most banks' IT) – you’ll be at least three to four years behind if you want to wait to see someone else’s ROI demonstrated before you commit.” – Brett King, Banking 3.0
Customers
Line of Business

4. Inefficient software development impacts the entire business4
Inefficient software development impacts the entire business
LINE-OF-BUSINESS Takes too long to introduce or make changes to mobile apps and services
OPERATIONS
Rapid app releases impact system stability and compliance
>70%
>45%
Systems of Interaction
of budgets devoted to maintenance and operations
Systems of Engagement
Systems of Record
of customers experience production delays
CRM HR DB
ERP
4-6 weeks
>50%
Cloud-based Services
to deliver even minor application changes to customers
Want to: Experiment in the market to judge success of products and services
LOB: Cannot iterate quickly with market based on IT timelines want to: Maintain system stability Ops: Cannot keep up with the pace of change pushed into the system
Want to: Quickly iterate on functionality Dev: Cannot access production-like environments to validate application changes
Continuous client experience
Partner value chain
of outsourced projects fail to meet objectives
DEVELOPMENT/TEST
Speed mismatch between faster moving front office and slower moving back office systems, delaying time to obtain feedback
SUPPLIERS
Delivery in the context of agile

5. Application development realities Two speed IT
Rapid iterations
Production
Deploy
Develop
Build
Test
API Catalog
Systems of Engagement
Slower iterations
Slower iterations
But even with optimized DevOps solutions to cater for these differences, the reality of a two speed IT makes the delivery of these integrated systems complicated multi-team projects.
Why do we talk about two speed?
- SoR teams typically release software in cycles measured in months, commonly 3-6 months with very distinct phases, dedicated teams (e.g. testing).
- SoE teams typically deliver new versions of their software in days or weeks.
These differences in speed, culture, and priorities create lots of challenges to manage dependencies. Typical issues include:
Lack of clarity on Services requirements
Mis-alignment of schedules and priorities
Different tools and infrastructures render rollout of entire stack complex
How do we solve this?
Deploy
Production
Develop
Build
Test
Systems of Record 5

6. Software development through the ages
4/15/2017
Software development through the ages
IBM DevOps
Steer
Develop / Test
Deploy
Operate
Classic scope of the Software Development Life Cycle
Business
Dev Team
Operations
Customer
Design
Develop/Code
Test
Planning
Deploy
Feedback
Waterfall
4 mo.
12 mo.
1 mo.
18 mo.
Now let’s compare a DevOps approach to the way software is traditionally developed.
Identify the roles: business, dev team, ops, customer
Identify the steps: planning, design/dev/code/test, deploy, feedback
Review the methods: waterfall, agile, IBM DevOps and note the typical timeframe for each step
Review the scope of SDLC: classic, DevOps competitors, IBM DevOps
Agile
4 mo.
1 mo.
7 mo.
DevOps
1-3 mo.

7. DevOps builds on Agile/ Lean initiatives ….across the enterprise
Develop / Test
Deploy
Steer
Operate
Collaborative Development
Continuous Release and Deployment
Continuous Testing
Business Owner
Service
Developer/Tester
Operations
Target Customer
Idea
Market
Continuous Business Planning
Continuous Monitoring
Lean and Agile principles
Continuous Feedback and Optimization
To be successful at software delivery we need to take a new approach that gets more folks in the organization on the same page
DevOps is such an approach that changes the status-quo and focuses on the end-to-end delivery of products and services
We can do this by taking a lean (reducing overhead and waste) and agile approach that is broadened AND automated across an expanded lifecycle that includes customers, LOB / business owners, development / test and operations / production.
Defn of lean: Some overhead is a necessity, but excessive overhead, excessive rework, overproduction of unneeded functions and time wasted in waiting
IBM has identified 4 “adoption paths” in GREEN that target specific areas that organizations may want to consider starting with on their transition to DevOps….
Within these 4 adoption paths, IBM has also identified 6 best “practices” to a successful DevOops transition
Steer– Continuous planning helps prioritize application portfolio decisions, measure results, and keep investments aligned with business strategy and customer input.
Develop / Test – Collaborative development and continuous testing support the rapid progression of a business idea or requirement into a high quality software solution by applying agile principles, facilitating collaboration among stakeholders, and striking the optimal balance between quality and time to market.
Deploy – Helps customers continuously release and deploy complex mobile, cloud, web-based, traditional applications and hybrid applications.
Operate (or “run”) – Helps customers better understand and improve the customer experience through continuous monitoring and continuous feedback and optimization. We can help our clients meet and exceed service level agreements for app performance and availability. And improve their customer engagement experiences with mobile and web apps through sentiment analysis and other digital analytics.

8. DevOps Continuous Feedback
Enterprise capability for continuous software delivery that enables organizations to seize market opportunities and reduce time to customer feedback
Accelerate software delivery –
for faster time to value
Continuous Business Planning
Operate
Develop/ Test
Deploy
Steer
DevOps Continuous Feedback
Continuous Customer Feedback & Optimization
Collaborative Development
Reduce time to customer feedback – for improved customer experience
Continuous Monitoring
Continuous Testing
Balance speed, cost, quality and risk –
for increased capacity to innovate
Main point: DevOps is an enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback (the following are the three themes of the launch which form “chapters” of his presentation)
DevOps has emerged as the new enterprise capability for continuous software delivery, it enables organizations to reduce time to customer feedback and seize market opportunities
Here is the IBM definition of DevOps. It is a set of practices/approach, end-to-end tooling capabilities, and know-hows that enables clients to
Accelerate software delivery ( - by enabling collaboration between customers and enterprises and eliminating organizational silos)
Balance speed, cost, quality and risk- (By automating manual processes and eliminating waste)
Improve client experience - (By speeding the customer feedback loop)
Two key aspects here:
End-to-end software delivery lifecycle: DevOps extends lean/agile principles across the broader lifecycle and across the enterprise with collaborative development, continuous testing and integration, continuous release and deployment, continuous monitoring and optimization
(Line-of-business analysts, developers, operators, maintainers, clients and field support staff. Everyone must be a stakeholder in an open lifecycle platform with consistent integration, collaboration, and optimization patterns)
Feedback loop: continuous feedback across software lifecycle, across stakeholders, from customers to business, from operations to development and test, from test to development etc.
We see four general adoption paths on the road to DevOps ( Four areas where we see clients can incrmentally adopt DevOps practices) These are:
·Steer - Be able to plan new versions and release, to make the tradeoffs required, to measure experiments that have been made to improve the product.
·Develop and Test - This is all about collaborative development with continuous testing and integration.
·Deploy - This is all about being able to release and deploy in a consistent and efficient manner. It may be to release many times in a week or it may be to make sure that monthly release to production is a reliable and high quality release.
·Operate - This is all about being able to get feedback from the client and application. This may be performance information, it many be sentiment analysis on how clients are doing with the app or it may be actually understanding the navigation paths that clients are taking - not what you think they are taking )
Continuous Release and Deployment
“The agile, "devops" culture will move from the software development lab to the front office. That will be required of sales and marketing, customer service, HR, product development… customers will expect you to behave differently. Rapid response, iterative, fast with quality. It is a rare front office today that is ready for this.” – Ginni Rometty

9. A prescription for DevOps transformation
A progression starting with a business objective
Identify actions to address wait-time / unplanned- & re-work
Execute on the actions / Measure results
Iterate for continuous improvement
Establish Business Objectives
Execute/Measure improvement actions to reduce or eliminate pain points
Assess current capabilities using the DevOps maturity model
Identify pain points and sources of friction that impede capabilities
DevOps
Steer
Dev &
Test
Deploy
Operate
Improve
Main point: One size doesn’t fit all and DevOps adoption must be tailored based on organizations current gaps and business needs.
The IBM DevOps maturity model is the communication tool to develop an strategy for improvements in software delivery. This model transcends organizations, practice areas, and technologies. Our practice-based model reflects the broader context of an enterprise adoption framework. It defines best practices for executing a strategy for adopting new solutions iteratively and enables clients to assess, plan, define, and deploy improvements that achieve measurable outcomes for their business. The adoption framework prescribes the steps to prepare, pilot, and release improvements into client’s business.
TRANSITION: Let’s now look at how DevOps can help support software delivery for systems of interactions, involving systems of engagement and traditional systems of records
Notes:
IT has traditionally struggled with organizational design. The main issue around productivity often revolves around these bottlenecks and silos that are optimizing a particular resource group almost at the expense of everybody else so what we found is that instead of managing work based on what’s best for the network guys or what’s best for the server guys or what’s best for the developers, we really need to manage work based on what's best for the company. That means that you have to take a flow-based approach where what is important is completing the project and hitting goals. The project is not complete until all of the groups are done, and this notion is hard to understand for many folks in IT.
It doesn't matter how fast the pilot or the flight attendants get on the plane, but it matters when the last passenger gets on the plane so you can shut the cabin door and actually take off . I often joke when I am on the airplane, saying we are all going to take off at the same time. Being first doesn't matter! This notion of managing constraints in IT organizations is really important.
-Kevin Behr Read more: 
One of the first steps in the adoption framework, shown here is to assess your current maturity level and decide on the scope, architecture, and roadmap for adoption or improving your enterprise DevOps capability.
Activity in the adoption framework
Assess and decide: Assess your current maturity and decide on the scope, architecture, and roadmap for adopting or improving your enterprise DevOps capability.
Establish a core team: Establish a leadership and mentoring group to drive the improvements/adoption and support a broader, virtual team of subject matter experts.
Define a working model: Define a usage model that addresses processes and activities for each role, as well as tool configurations and supporting architecture for the capabilities planned in the pilot. This will then be used for user acceptance test of the solution and by the pilot teams during the pilot.
Prepare for a pilot: Define pilot outcomes/objectives and measurements for validating the objectives. Using the usage model, produce assets to support introducing the solution to pilot teams. Assets may include training, job aids, plugins, reports, and queries.
Pilot the project(s): Use defined improvements with real data in a production project or initiative. Measure objectives, validate the usage model, and then improve the solution for the next pilot/release.
Execute the adoption strategy: Following the pilot, deploy the capability or capabilities piloted across organizations, technologies, and applications according to the roadmap. Release The release is a well-defined improvement that produces measurable outcomes for users, teams, projects, programs, departments, and the enterprise.
Continuous Improvement,
Identify actions, pain points, new milestones
Progress as an agile project
Second critical dimension:
Streamline the ‘production line’
Leverage tools for consistency, Scalability to other teams, Traceability/Metrics
Evolve the culture to continuously improving 9

10. Scaled Agile Framework (SAFe) in a Continuous Delivery model
SAFe best practices and guidance based on lean and agile principles apply to all layers in a team-of-teams infrastructure to improve time-to-value and ensure business ROI for Enterprise organizations
End-to-end adoption of SAFe in all environments, including regulated
IBM uses SAFe - We guide customers through a full adoption of SAFe with tools and processes
Continuous Deployment across platforms and technologies
Rapid Feedback from Operations
Shift Left – Operation concerns fed back into Program/Portfolio level planning
DevOps services extended to Operations
IBM is unique in our ability to scale Agile to an enterprise level
Synchronizes alignment, collaboration and delivery for large teams-of-teams organizations
Customers that have already adopted agile and need to scale their current processes while also following a DevOps approach, have been turning to the Scaled Agile Framework (SAFe) as one of the more popular scaling agile frameworks to help them do that. SAFe is applicable in all IT environments including regulated or compliance industries.
IBM is a SAFe gold partner, and is unique in our ability to scale Agile to an enterprise level. IBM along with our partners can guide customers through a full adoption of SAFe with tools and processes to implement a DevOps approach. We use SAFe internally as well as Scrum, for our own development processes.
Continuous Business Planning
Continuous Customer Feedback & Optimization
Collaborative Development

11. IBM DevOps as a Managed Service
Addressing bottlenecks across the application delivery lifecycle
Develop / Test
Steer
Deploy
Operate
Continuous Business Planning
Collaborative Development
Continuous Release and Deployment
Continuous Monitoring
IBM UrbanCode Release
IBM UrbanCode Deploy
SmartCloud Orchestrator
GBS Cont Rel & Deploy Services
Rational DOORS NG
Rational Team Concert
GBS Assessment & Benchmarking Services
Rational Team Concert
Rational Lifecycle Adapters
GBS Collaborative Dev Services
SmartCloud Application Performance Management
SmartCloud Control Desk
GBS Continuous Monitoring Services
Continuous Testing
“IBM has a more comprehensive end-to-end DevOps and ALM testing integration tool strategy, and the strongest market momentum.” – Diego Lo Giudice, Forrester Research, January 27, 2014
Continuous Customer Feedback & Optimization
Rational Quality Manager
Rational Test Workbench
Rational Test Virtualization Server
InfoSphere Optim Test Data Management
GBS Continuous Testing Services
IBM provides the most comprehensive set of DevOps capabilities -- this allows us to help our clients address bottlenecks across the application development and delivery lifecycle, with particular focus on development, testing, and deployment.
IBM leadership:
#1 vendor in Gartner market share for Application Development software for 13 consecutive years, and #1 in Evans Data Corporation User's Choice Survey for Software Development Platforms for 6th time in 7 years.
Tier 1 analysts like Gartner and Forrester recognize the breadth and category leadership of the IBM portfolio. <reference Diego Lo Guidice quote from Forrester Research>
IBM is a leader in Gartner Magic Quadrants and Forrester Waves across all key app dev segments, PLUS we have independent analyst-authored ROI studies supporting key segments.
DevOps – four adoption paths (or entry points), with defined practices, comprise DevOps approach and scope:
Plan & Measure – Continuous planning helps prioritize application portfolio decisions, measure results, and keep investments aligned with business strategy and customer input.
Develop & Test – Collaborative development and continuous testing support the rapid progression of a business idea or requirement into a high quality software solution by applying agile principles, facilitating collaboration among stakeholders, and striking the optimal balance between quality and time to market.
Release & Deploy – Helps client continuously release and deploy complex mobile, cloud, web-based and traditional applications. Client gain visibility across software releases and ensure accurate and consistent application stacks across the delivery lifecycle (development, test and operations) that results in reduced cost and risk and improved quality.
Monitor & Optimize – We help clients better understand and improve the customer experience through continuous monitoring and continuous feedback and optimization. We can help our clients meet and exceed service level agreements for app performance and availability. And improve their customer engagement experiences with mobile and web apps through sentiment analysis and other digital analytics.
IBM delivers DevOps capabilities on-prem, in the cloud, and hybrid.
The product names noted are largely on-prem solutions and hybrid solutions. Many of these capabilities are delivered as services in the cloud.
IBM Bluemix DevOps Services optimized for BlueMix provide an essential set of developer tools to get teams up and running quickly without the hassles of software installations, configurations and maintenance.
IBM Bluemix DevOps Services include: app auto-scaling, monitoring & analytics, mobile quality assurance, Git hosting, web IDE, continuous integration, agile planning & tracking, plus various third-party offerings – with lots more to follow.
IBM Tealeaf
IBM Digital Analytics
IBM MobileFirst Quality Assurance
IBM DevOps as a Managed Service

12. Lifecycle Measurements
Internal IBM SW improvements using a DevOps approach
Lifecycle Measurements
2008
2010
2012 – 2014
Total Improvement
Project Initiation
30 days
10 days
2 days
28 days
Groomed Backlog
90 days
45 days
On-going
89 days
Overall Time To Development
120 days
55 days
3 days
117 days
Composite Build Time
36 hours
12 hours
5 hours
700 %
BVT Availability
N / A
18 hours
< 1hour
17 hours
Iteration Test Time
5 days
14 hours
4 days
Total Deployment Time
8 hours
4 hours -> 20 minutes
Overall Time To Production
9 days
7 days
Time Between Releases
12 Months
3 Months
9 Months
Innovation / Maintenance
58% / 42%
64% / 36%
78% / 22%
+20% / -20%
Number of projects, active projects,
- instrumentation
Double-digit revenue growth, increased client adoption, improved client satisfaction

13. We are here to help with your DevOps transition
4/15/2017
We are here to help with your DevOps transition
DevOps on IBM.com
DevOps on developerWorks
DevOps For Dummies
Pickup your FREE copy of DevOps For Dummies today
Or visit ibm.co/devopsfordummies

14. Thank you for coming today ….and welcome to the Austin Symposium!