4.9.2013 continuous delivery - extending agile development; a lean approach

© 2009 IBM Corporation

Continuous Delivery - Extending Agile Development, A Lean Approach

Rob Cuddy - WW Sales Enablement Leader

09 April 2013


Agenda

Quick look at Agile today

Principles of Lean Agile

Applying principles to Continuous Delivery

Success Story: IBM Rational

2


Organization

The New NormalBalancing Speed, Complexity and Innovation

Team Member

Teams


Agile projects succeed 3x as often as Waterfall projects but… companies still need help

Sources: NIST, Planning Report 02-3. The Economic Impacts of Inadequate Infrastructure for Software Testing, May 2002; aThe Times of India, IT sector to get 12% average salary hike in 2011, TOI Tech & Agencies, Mar 8, 2011, Forrester

Research, 2012

26%Estimated number of organizations who use agile methodologies ONLY in development

78%Percentage of the organization who feel they can’t keep up with an agile development team

Water-Scrum-Fail

42%The percentage of people on agile project teams that believe team is successful

10%The number of projects that can actually prove why they were successful

Low Success Rates

77%Of all companies that report they need to monitor and measure mixed environments

65%The percentage of organizations that consider complex [tool] integrations as a key inhibitor

Increased Inhibitors

4


Why Lean Agile Five impediments agile developers face that ultimately slow delivery of innovative software

#1 Too much red tape

#2 Lost time due to task switching between tools or duplication of work

#3 Difficulty in coordinating different agile teams with conflicting priorities

#4 Inefficient and inconsistent continuous integration and deployment practices

#5 Being disconnected from customers and stakeholders

5

Instant Messages

Spreadsheets

Tools

MOBILEMAINFRAME

CUSTOMERS


Agile ALM

BusinessCollaboration

Portfolio Management

Agile Modeling

Requirements Management and

Envisioning

Multi-Platform Development

Continuous Integration and Test

Continuous Delivery

ProcessAuthoring

Enterprise Reporting

Scalable agile capabilities that adapt to a customer’s diverse needs“I need to

collaborate with my operations team and help them deploy

software more frequently”

“I need to assure testing can keep up with our agile development.”

“We are planning to deliver mobile apps

to our customers that extend our enterprise

solutions”

“I need to connect and prioritize projects with stakeholders”


dev·ops noun \'dev-äps\Enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback.

DevOps: A blueprint for continuous delivery of software innovation

7

Accelerated software delivery

Reduced time to gather and analyze customer

Improved governance across the lifecycle

Balanced quality, cost and speed

DevOps Lifecycle

Continuous Feedback and Improvements

Operations/ProductionDevelopment/TestCustomers Business Owners


Apply Principles of Lean Agile

Overall goal: Achieve quality, speed and customer alignment

8

Eliminate waste

Build Quality In

Create Knowledge

Defer Commitment

Deliver Fast

Respect People

Optimize the whole


Eliminate Waste

Common Causes of Waste:

–Manual handoffs between teams

–Wait times for environments

–Delays in test acceptance

–Tests against “wrong” environments

9


Eliminating Waste

10

Result: 15-35% reduction in

average delivery cycle time

Infrastructure and Environment Deliverables

Application-Under-Test Deliverable

• Automate smooth and error-free hand-overs of ready-use- deliverables

• Integrate testing with existing build processes


Build Quality In

Common Barriers:

–Mismatched environments between Dev, Test & Prod.

–No single source of truth

–Long times needed to reproduce, isolate and fix defects

–Ops has low confidence in deliverables received11


Building Quality In

12

Result:

30 - 40% reduction in outages

• Automate deployment and functional testing of dev changes on production-like environments

• Manage application and infrastructure changes together


Create Knowledge

Common Barriers

–Too much “tribal knowledge”

–Lack of meaningful metrics

–Lack of feedback loops

–Inconsistent toolsets

13


Creating Knowledge

14

• Leverage and share standardized definitions of environment patterns

• Provide reliable visibility and traceability to isolate and recreate defects

Result: Reproduce and

communicate defects 85% faster


Defer Commitment

Common Barriers

–Inflexible architectures

–Lack of integrated tools

–Poor visibility across teams

–Poor understanding of

application health

15


Deferring Commitment

16

• Integrate monitoring of applications for early identification of performance issues

• Raise visibility into delivery quality and tested configurations

Result: Up to 35%

improvement in development efficiency


Deliver Fast

Common barriers

–Different processes for

different teams

–Rollbacks in production

– Integration delays

–Too many requests for

environments

17


Delivering Fast

18

Result:

Deliver environments 3 times faster

Deliver 4 times more releases per year

• Provide 1-click deployment of environments for testing

• Apply infrastructure as code: deliver application and environment changes together


Respect People

Common barriers

–Disconnected teams

–Lack “one source of truth”

–Lack of understanding

across teams

–“Finger-pointing”

19


Respect People

20

Result:

98% improvement in meeting service level agreements (SLA)

• Incorporate self-service deployments of personal test sandboxes into IDE

• Provide common repositories & views all teams can leverage (single source of truth)


Optimize the Whole

Common barriers

–Cultural challenges

–Different views of “done with

quality”

–Narrow focus

–Technical debt

21


Optimize the Whole

22

Results: Setup test

environments 90% faster

Reduce testing cycle from 2 weeks to a few hours

• Use automated deployments of deliverables and test execution in production-like environments

• Enable early identification and instant feedback of issues

© 2009 IBM Corporation24

Deliver product 4x faster while keeping the cost down

Results: Predictable delivery every 4 months with cost avoidance of, at

least, 25%

Self-service availability of production-like environment – 75%+ improvement

Dev integrated testing reducing long test cycles -

Challenges Time: Reduce delivery cycle from 12 months to 12 weeks.

Scale: Coordinating release with 100’s of builds a day

Management: Release schedule spanning 25 components, 400 Developers and testers in 17 locations

Needs: Align delivery with fast changing market needs

Must deliver product updates every 4 months

Solution Leverage DevOps principles with Agile Development and Testing

Rational CLM and IBM SmartCloud Continuous Delivery

“Using Continuous Delivery approach, we were able to deliver 4X faster without sacrificing quality and with 25% cost savings—Scott Rich. IBM


DevOps Capabilities

Lifecycle Measurements

Before With DevOps

Total Improvement

Business Planning Project Initiation 10 days 2 days / release

2 days

Groomed Backlog 45 days 1 day / Release

42 days

Overall Time-to-Development 55 days 3 days / release

42 days

Collaborative Development

Iteration Length 8 weeks 4 weeks 4 weeks

Number of Iterations 8 3 N / A

Continuous Testing BVT Availability 18 hours < 1hour 17 hours

Iteration Test Time 2 days 4 hours 2 days

Continuous Deployment / Release

Total Deployment Time 8 hours 2 hours 6 hours

Overall Time-to-production 3 days 15 hours 2+days

Time Between Releases 12 Months 3 Months 9 Months

Observed lifecycle metrics


List of Deployment Configurations available for BVT, SVT, FVT


Learn about CLM and IBM SmartCloud Continuous Delivery

27

http://jazz.net/products/smartcloud-continuous-delivery

https://jazz.net/products/clm/


Summary: Continuous Delivery Extending Agile

28

Accelerate end-to-end software delivery lifecycle

Improve delivery efficiency, application quality and performance

Improve collaboration between development, test and operations

Development

Time to deliver new function

reduced by 66%

Test

IBM China Lab reduced testing

time from 2 weeks to 3 hours

Operations

Maintained flat costs with 35%

increase in dev/test services

Continuous Feedback and Improvements


Continuous Delivery Webcasts in 2013

Title Date Time (EST)

Overview Smart Cloud Continuous Delivery or Enterprise Continuous Delivery 2/12/2013 11-12pm

Who Uses Continuous Delivery and How They Look 3/12/2013 11-12pm(Today) Continuous Delivery - Extending Agile Development; A Lean Approach 4/9/2013 11-12pm

(Next up)Continuous Delivery - Agile Deployment for IT - More Efficiency 5/14/2013 11-12pm

Continuous Delivery - Testing for Agile Through Continuous Delivery 6/11/2013 11-12pm

Continuous Delivery - Deploy, Moderate, Manager Applications in Production Environment 7/9/2013 11-12pm

Continuous Delivery - Best Practices for Adoption of Continuous Delivery 8/13/2013 11-12pm

Continuous Delivery - System Z Testing (Mainframe) 9/10/2013 11-12pm

Continuous Delivery - System Z Testing (Mainframe) 9/10/2013 11-12pm

Continuous Delivery - Agile Testing with Green Hat - 9/18/2013 11-12pm

Continuous Delivery - Mobile Apps 10/8/2013 11-12pm

2013 - Continuous Delivery - Change/Defect Management 11/12/2013 11-12pm

2013 - Continuous Delivery - Arch Briefing on the Continuous Delivery Solution 12/10/2013 11-12pm

29

4.9.2013 continuous delivery - extending agile development; a lean approach

Technology

extending

continuous

deliver fast

continuous

build quality

lean approach

lean agile

agile development