DOES14 - Gary Gruver - Macy's - Transforming Traditional Enterprise Software Development Processes
Download as PPTX, PDF•7 likes•10,217 views
The document outlines how applying DevOps and agile principles at scale can significantly improve enterprise operations, indicating a reduction in development costs from $100 million to $55 million annually and a 140% increase in product development. It also emphasizes enhancing feedback quality, improving deployment repeatability, and the importance of executive engagement in driving organizational transformation. Overall, the approach aims to foster continuous improvement and increase innovation capacity from approximately 5% to 40%.
DOES14 - Gary Gruver - Macy's - Transforming Traditional Enterprise Software Development Processes
- 1. Making the Enterprise Agile “Applying DevOps and Agile Principles at Scale” Gary Gruver October 23, 2014
- 2. FW no longer a bottleneck for the business Development costs reduced from $100M/yr. to $55M/yr. 140% increase in the number of products under development Capacity for innovation increased from ~5% to ~40%
- 3. Planning & Prioritized Backlog Making the Enterprise Agile Applying DevOps Principles at Scale Business Objectives Enterprise Level Continuous Improvement
- 4. Business Objectives Increase the quality and frequency of feedback Testing in an Operational like environment as close to dev. as possible Reduce the time and resources between release branch & production Improve deployment repeatability/env. stability
- 5. Ensuring the Architecture/Build System is Ready Comp A v1 Comp B v1 v2 v12 Comp C v1 Comp D v2 v2 v2 v1 Comp E v1 Comp F v2 v1
- 6. Automated System Test Architecture Component based approach to the automated test architecture Data Magic Navigation Page Objects
- 7. Unique Considerations for Horses Cost of Failure Ease of Deployment Test Env = Production Architectural
- 8. Embedded SW/FW Simulators Emulators Packaged SW Upgrade Compatibility Patches Web/SaaS Continuous Delivery DevOps Unique Challenges
- 9. Finding the Offending Code What Code? When? Are you sure it wasn’t Gene?
- 10. Building Up a Large SW System Interface Test Simulator Agile Comp 1 Agile Comp 2 Agile Comp 3 Agile Comp 4 Agile Comp 5 Agile Comp 6 Legacy Waterfall IT 1 Legacy Waterfall IT 2 Legacy Waterfall IT 3 Agile Comp 1
- 12. Building up the Enterprise Gating at the Application or Artifact Gating at the SCM Interface Test Simulator Gating at the SCM Interface Test Simulator
- 13. CD - Picking the Right Tool for the Job Orchestrator Trigger Scripted Env Deploy ment EDD Auto Testing
- 14. Scripting Environments - Variances Dev/QA PRE-PROD PERFORMANCE PRODUCTION Environment descriptors Common Script Common Script Common ScriCpotmmon Script
- 15. Evolutionary Database Add deprecate Lazy instantiation Don’t alter or modify It is like crossing the beams
- 16. Finding the Offending Component Quickly Improves Productivity 1 Configure Servers/Routing Device : 2 Deploy Code : 3 Run a System Test : ? ? ? ? ? ? ? ? ? ? ? ?
- 17. Finding the Offending Component Quickly Improves Productivity Configure Servers/Routing 1 Device and Validate Data : Deploy Code & Validate 2 Successful Deployment : 3 Run a System Test : Code Validated
- 18. Release Branch
- 19. FW no longer a bottleneck for the business Development costs reduced from $100M/yr. to $55M/yr. 140% increase in the number of products under development Capacity for innovation increased from ~5% to ~40%
- 20. Where could I use help? • How do we get executives to engage and help lead the transformation of their organizations?
- 21. Making the Enterprise Agile “Applying DevOps and Agile Principles at Scale” E-mail: [email protected] Blog: largescaleagile.com Twitter: @GRUVERGary