The document discusses the need for enterprise agile development to utilize service virtualization and virtual environments. It notes that increasing complexity from interconnected systems and components has made achieving agile goals like rapid iterations and releases difficult due to realities like schedule conflicts between teams. Service virtualization provides simulated services that allow development to proceed independently of dependencies, avoiding delays. This allows teams to shift testing activities earlier in the development cycle for faster delivery and fewer defects. Examples of how service virtualization has helped customers reduce infrastructure costs and development cycles are also provided.
4. Change and Complexity Increasing
CRM Routing Help
App Collaboration Web Service Engine
Portal Virtual Web/WAP BI Tools
App Interface Service Interface
External Partners Cloud
Content
Database
Business EJB
SOAP Rules
ESB
Data Internal
Warehouse
Legacy BPMS File
Products System
Infrastructure
Messaging
Financials
Service RMI Objects
Mainframe
# of Interconnected # of Heterogeneous
# of Interdependent Teams Rate of Change
Components Technologies
6. Agile goals move out of reach due to reality
Agile Goal: Faster iterations and releases
Dev 1 (Goal: rapid releases and
Integration check-ins, faster delivery)
Dev 2 Performance
UAT
Dev 3
Reality: Schedule conflicts make Agile become Waterfall
Dev 1 Dev 1a
Dev 2 Integration Performance UAT
Dev 3
New Dev 33
New Dev Waiting for
Waiting for Conflicts
Conflicts Teams
Teams
release
release Dev 22to
Dev to appear at
appear at waiting for
waiting for
affects Dev 11
affects Dev complete
complete Integration
Integration environments
environments
9. Meditation: Service Virtualization is like…
The Holodeck in Star Trek
A fake Wild West Town
Complete with stuntmen to shoot at
An Electronics Test Harness
But our favorite is…
Patagonia, Argentina 2008. Photo: Jason English
18. customer successes
Large US Telco – Popular cell phone launch
Reduced software release cycle time by 33%
400% increase in defects identified
4 weeks to achieve 100%+ ROI – $1.6M
Major US Financial Services Company – 3rd Party Access
Avoided $700k investment in additional hardware on 1st project
Avoided 95% of non-production 3rd party access fees
Eliminated delays related to 3rd party dependencies from SDLC
8 weeks to 100%+ ROI
Major US Bank – Performance Engineering
8 days to replace 2 years of custom-coded stubs
Avoided $30M Y1 in lab upgrades, >$90M to date
Increased quality from 3.7 to 5.1 Sigma in single release.
Reduced outsourced testing headcount from 45 to 7.
Increased team scalability from supporting 5 apps to 140.
19. Nirvana: Agile, continuous delivery has to be application
lifecycle oriented
App1-Dev
App1-Dev App1-ST
App1-ST
SIT
SIT
App2-Dev
App2-Dev App2-ST
App2-ST PROD
PROD
PERF
PERF
App3-Dev
App3-Dev App3-ST
App3-ST
Follows the customer’s development cycle (Dev, SysTest, Integration, Prod)
Supports Environment contents that are different by stage and by Team
Allows for Environment Refresh and Environment Promotion
Allows for coordination/synchronization of promotions
Provides full auditability, rollback, reproduction, and redeployment
Deploys to any/all possible targets: existing, Cloud Provisioning, Run Book
We know how complex enterprise application architectures have become. This is what motivates us... What drove our thinking to create LISA. More complex and changing your architecture, the better for us. Main Point: Do you have an IT architecture like this? IT architectures are becoming more distributed, more heterogeneous, and more complex. There are several moving parts behind enterprise apps today. Each point of connection becomes a potential point of failure in production, and we don’t always have all of the systems that impact our business under control. This can create significant problems in ensuring application quality. ------------------