Many organizations are recognizing that faster application delivery leads to better business results, but they struggle with how to overcome their barriers to faster delivery. In this webinar, guest speaker Kurt Bittner, Principal Analyst at Forrester Research, Inc., discusses the most common barriers to faster delivery and how organizations work to remove those barriers.

1. Removing Barriers to
Continuous Delivery of Business Value
Kurt Bittner
Principal Analyst
@ksbittner
© 2014 Forrester Research, Inc. Reproduction Prohibited

2. The Half-Life Of Innovation Is Shrinking
7 years
Images copyright © 2014 Apple Inc. All rights reserved.
© 2014 Forrester Research, Inc. Reproduction Prohibited 2

3. Customer Demand Is Increasing Complexity
© 2014 Forrester Research, Inc. Reproduction Prohibited
“Navigate The Modern Application Delivery Landscape”, February 12, 2014

4. The Software-Powered Value Delivery Cycle
Fast Feedback Drives
Better Business Results
› Less waste
› Lower cost
› Happier customers
› Increased revenue
› Lost revenue avoidance
› Increased profitability
© 2014 Forrester Research, Inc. Reproduction Prohibited 4

5. The road to faster delivery is well-marked
and increasingly well-traveled
http://buckleysautorepair.com/wp-content/uploads/2012/03/iStock_Road-SignsSmall.jpg
© 2014 Forrester Research, Inc. Reproduction Prohibited 5

6. Lean Value Stream Mapping
http://en.wikipedia.org/wiki/Value_stream_mapping
© 2014 Forrester Research, Inc. Reproduction Prohibited 6

7. Value Stream Mapping Applied To Application
Delivery
Maximize Utilization ➔ Maximize Throughput
© 2014 Forrester Research, Inc. Reproduction Prohibited

8. Idea
proposed
Understand
Needs & Invent
Solutions
© 2014 Forrester Research, Inc. Reproduction Prohibited
• Lack of Effective
Build/Integration
Automation
• Manual Testing
• Design Complexity
Develop,
Commit & Build
UAT/Explorato
ry Testing
Functional
Testing
Deploy
Solution
Manual
environment
management
and
deployment
Customer
Value
Load,
Performance,
Security, …
Testing
Release
Decision
Typical Bottlenecks
Too Much WIP
Lack of access to Dev
& Test Environments
Lack of effective
API-driven test
automation
Lack of effective effective
release candidate quality
information
Lack of
Effective
Customer
Insight
Ever-present bottleneck” hand-offs and wait time

9. Idea
proposed
Understand
Needs & Invent
Solutions
© 2014 Forrester Research, Inc. Reproduction Prohibited
• Continuous
Integration
• Continuous Testing
• Loose Architectural
Coupling
Develop,
Commit & Build
UAT/Explorato
ry Testing
Functional
Testing
• Infrastructure
Deploy
Solution
Customer
Value
Load,
Performance,
Security, …
Testing
Release
Decision
Typical Enablers
Smaller
batches/payloa
d
Infrastructure As
Code, Environments
On Demand, Cloned/
Templated
Environments
Continuous
Testing
Sufficient Test Data to
make decisions
as Code
• Release
Automation
Application
analytics, CX
data
Everywhere: Cross-functional
teams, simplified roles

10. Continuous Testing
UI – Presentation Layer
API Layer
Resource Layer
(including other Applications)
Test
Harnesses
© 2014 Forrester Research, Inc. Reproduction Prohibited 10

11. Loose Architectural Coupling
Enables independent change,
removes bottlenecks
› Services are versioned to allow
interfaces to evolve
› Resources can be replaced without
affecting applications
› Risk is reduced by isolating and
eliminating dependencies
› The unit of release becomes an API
change, not an application
› Applications and services can choose
when they “upgrade” to a new
interface
UI Layer
API Layer
Resource Layer
(including other Applications)
© 2014 Forrester Research, Inc. Reproduction Prohibited 11

12. Submit
Sign In
“←
Infrastructure As Art”
→
Feedback
http://www.flickr.com/photos/38392483@N00/385912858
› Every environment unique
› Manually built and configured
› No auditability of changes
› Often, no control over change
access
› No repeatability
› “It works fine in my environment.”
© 2014 Forrester Research, Inc. Reproduction Prohibited 12

13. “Infrastructure As Code”
http://www.datacenterknowledge.com/wp-content/uploads/2011/05/ITPAC-Servers-470.jpg
› Standard VM/Container
configurations
› Configurations version
controlled
› Managed Change
authorization
› Changes automated,
repeatable, auditable
Environments on
demand
© 2014 Forrester Research, Inc. Reproduction Prohibited 13

14. Infrastructure As Code In Practice
• Configuration information (settings, users, permissions,
© 2014 Forrester Research, Inc. Reproduction Prohibited
accounts, installed software, properties, …) saved in SCM tool
• Scripts necessary to build new environments from
configurations saved in SCM tool
• Environments automatically created, configured and populated
with test data using automation

15. Environments On Demand
© 2014 Forrester Research, Inc. Reproduction Prohibited
• Self-service – no waiting for Ops, no
submitting requests, no “tickets”
• Typically cloud-based, sometimes VM-based
• No delay for even automated provisioning
(i.e. Infrastructure-as-Code) when using
standard configurations
http://www.postalproducts.com

16. Test Data Management
Key practices
› Reduce test data set size while
maximizing scenario coverage
› Anonymize data
Benefits realized
› Reduce time spent copying,
manipulating production data
› Eliminate privacy concerns
› Reduce cost of provisioning
testing environments
© 2014 Forrester Research, Inc. Reproduction Prohibited 16

17. Service Virtualization
Key practices
› Simplify creation of mocks and
stubs
› Manage mocks and stubs for
components and systems
› Simulate load and performance
characteristics
Benefits realized
› Reduce environment
provisioning complexity
› Test partial solutions earlier
› Eliminate component
dependency bottlenecks
© 2014 Forrester Research, Inc. Reproduction Prohibited 17

18. Benefits of Infrastructure As Code
Reduction in Production
Incidents
› Reduction in production
incidents due to environment
configuration errors
› Elimination of “it works fine in
my environment” excuses
Increase in Velocity, Reliability
› Eliminate wait-time for
environment provisioning
› “Clean” test environments
prevent false-positive and false-negative
results
A large corporation reported that 18% of their production incidents were caused
by configuration differences between environments. These were eliminated by
moving to an infrastructure-as-code approach.
© 2014 Forrester Research, Inc. Reproduction Prohibited 18

19. CD Practices increase speed, reduce risk
High
Continuous
Delivery
practices
© 2014 Forrester Research, Inc. Reproduction Prohibited
Traditional
practices
Delivery Speed
Risk of
Failed
Release
Low
Years Days

20. Thank you
Kurt Bittner
kbittner@forrester.com
@ksbittner
© 2014 Forrester Research, Inc. Reproduction Prohibited

21. Full On-Demand Webinar
Click Here:
http://bit.ly/1thVPuf
© 2014 Forrester Research, Inc. Reproduction Prohibited