Dev Ops for systems of record - Talk at Agile Australia 2015
3 likes992 views
Mirco Hering is a DevOps and Agile lead with over 10 years of experience improving IT delivery through automation, methodology, and innovation. The document discusses applying DevOps principles to systems of record like packaged software, non-custom code, and older custom code. It outlines challenges in automating builds, deployments, testing and integrating these systems. It provides examples of automating merges and traceability for a Siebel system to help systems of record adopt DevOps practices and continuous delivery.
![Our merges took way too long (~2 weeks) and took too much effort
We did get the results we were hoping for
113
826
1357
394
273
1135
309
2
82 60
0 11 8 50
0
200
400
600
800
1000
1200
1400
1600
Oct '12 Nov '12 Jan '13 Feb '13 Mar '13 Apr '13 May '13
No. of files merged
With tool
With resource support
[Conflict resolution]
from 100% manual at
start3.83%
3.56%
2.86%
1.92%
0.00%
0.50%
1.00%
1.50%
2.00%
2.50%
3.00%
3.50%
4.00%
4.50%
FY12-Q4 FY13-Q1 FY13-Q2 FY13-Q3
% of Merge & Retrofit Effort [on total effort]
The result: 2 weeks -> 3 days](https://image.slidesharecdn.com/devopsforsystemsofrecord-150629064645-lva1-app6892/85/Dev-Ops-for-systems-of-record-Talk-at-Agile-Australia-2015-23-320.jpg)
Dev Ops for systems of record - Talk at Agile Australia 2015
- 1. DevOps for Systems of Record An experience Report
- 2. Mirco Hering This is me… Follow me on Twitter: @mircohering Or read my blog: http://notafactoryanymore.com • DevOps and Agile Lead in APAC • Over 10 years of experience improving IT delivery through automation, methodology and innovation • Mainly worked on very large clients • Certified CSM, SAFe Agilist, Master Technology Architect • Conference Speaker and Blogger • Massive football (European) fan • Outside of work: Travel, Tennis, Triathlon
- 3. • The importance of COTS and other systems of record for your DevOps journey • Initial Discovery – look under the covers to see whether there is code • Challenges along the way – How to react when the system does not play along • Find the right balance between one tool to rule them all and every team for themselves • A typical automation journey and why this is especially problematic for COTS/Systems of record What you will hopefully learn today
- 4. Systems of Record Or shall we call it: Legacy Or be nice about it and call it: Enterprise It doesn’t matter – I mean those systems that don’t play nicely: Packaged Software, Non-Custom code or older custom code that behaves like a package,… Think – Siebel, SAP, Mainframe,… Systems of Record – what is that?
- 5. Is this your world….
- 6. Business today is increasingly high velocity and software driven What’s needed is a new way to build software One that is faster, flexible and more liquid. No longer can applications be “built” as one distinct activity and “maintained” as another. Engineering innovations such as Agile and DevOps enable software to be continuously delivered and evolve as business needs change. - Accenture Future of Applications, 2014
- 7. Both digital and enterprise applications must move faster to keep pace Two-Speed IT is an intermediate step, but you should not forget the enterprise applications Enterprise Applications Digital Applications Read more on my blog: http://notafactoryanymore.com/2015/01/28/how-to-support-multi-speed-it-with-devops-and-agile/
- 8. Channels & Customer Experience “High Speed Agility” DECOUPLING Core Services “Low Speed Stability” Partners Channels & Customer Experience Core Services Typical project Front Back - Today - - Tomorrow - The Legacy Complication…
- 9. What is DevOps ? DevOps uses automation techniques to optimize collaboration across development and operations, enabling faster, more predictable and more frequent deployments to market
- 10. DevOps is a direction, not a goal! My view of DevOps
- 11. So what can we do with systems of record Project Management Tooling Software Configuration Management Build & Deployment Automation Test Automation Environment Management & Monitoring Cloud Environment Provisioning Continuous Delivery Cultural Change & Organization Alignment: Agile Business Mindset
- 12. Is it technology or culture that holds us back?
- 13. Culture - A word of warning about maturity models Dunning Kruger Effect - Illusory superiority • In a survey of faculty at the University of Nebraska, 68% rated themselves in the top 25% for teaching ability. - Wikipedia • In a similar survey, 87% of MBA students at Stanford University rated their academic performance as above the median. - Wikipedia • For driving skill, 93% of the US sample and 69% of the Swedish sample put themselves in the top 50% - Wikipedia • How do you think people would rate you as a leader?” It turns out that 74% of the respondents think they’re either above average or the best leader their people have ever had. – SmartBrief on Leadership
- 14. Maturity models and what we can learn from Computer Games Read more on my blog: http://notafactoryanymore.com/2015/03/26/what-computer-games-can-teach-us-about-maturity- models-choose-your-own-devops-adventure/
- 15. My Simplified View of the DevOps Software Supply Chain Check-in SCM Dev Team Packa ge DeploymentTailor to Env Work Management Process Env 1 Env 2 Env 3 CMDB Compile & Package Automation orchestrated • Sourecode • Deployment Scripts • DB scripts • Documentation • Test automation Ingredients Ikea Manual Operations
- 16. It won’t be easy, but the rewards are worth it! Only a tool buys a tool to solve this problem… 3 Steps for your Systems of Record DevOps Journey 1. Look under the hood 2. Recreate the IKEA manual 3. Understand the path to production
- 17. Let’s quickly compare your favourite web language with the usual COTS world Code Hidden files Industry standard tools Proprietary Modular Monolithic Fast build Long cycle times Unit Test Not made for unit testing Developers Configurators Web-based Test Automation ?!?!?!? The role of DevOps is to understand how to find the moving pieces. Why is COTS software is different
- 18. Now that we got code – what next 1. Get it out of the proprietary SCM solution 2. Tightly integrate it with your IDE 3. Solve for Merges
- 19. a Each developer should be able to work in the best IDE for his specific technology Many frontends, but a common platform Integrations RTC
- 20. Make it easy to do the right thing Username & Password for RTC Location in RTC Search Window to find Work Items Check-In Comments Close the loop by refreshing the environments
- 21. Merge/Retrofit Automation Process Retrofit WI Tasks Change sets MANUAL EFFORT RETROFIT AUTOMATION Auto Merges Merge Logs Attached to Retrofit Assisted Merges Trivial Merges Automated Merges
- 22. 3 Types of Merges are being adressed A B C D A B C D E A B C D A B C D E False Positive Can be auto resolved using 3rd Party Tool Complex Cannot be auto resolved Trivial A B C D AA B C D AB B C D AA or AB B C D Old World 528 Objects manually merged New World 318 Trivial Merges 91 Auto Merges 119 Assisted Merges
- 23. Our merges took way too long (~2 weeks) and took too much effort We did get the results we were hoping for 113 826 1357 394 273 1135 309 2 82 60 0 11 8 50 0 200 400 600 800 1000 1200 1400 1600 Oct '12 Nov '12 Jan '13 Feb '13 Mar '13 Apr '13 May '13 No. of files merged With tool With resource support [Conflict resolution] from 100% manual at start3.83% 3.56% 2.86% 1.92% 0.00% 0.50% 1.00% 1.50% 2.00% 2.50% 3.00% 3.50% 4.00% 4.50% FY12-Q4 FY13-Q1 FY13-Q2 FY13-Q3 % of Merge & Retrofit Effort [on total effort] The result: 2 weeks -> 3 days
- 24. Traceability and our ability to cherry-pick Story/Defect/Retrofit /LUW Tasks Changesets Developer Developer Developer Story 12 Story 13 Story 14
- 25. Traceability and our ability to cherry-pick Build Workspace (Product Test) Build Workspace (Integration Test) Story 11 Story 12 Story 13 Story 14 Story 12 Story 13 Create a package & Deploy it Create a package & Deploy it
- 26. An Example IKEA manual: The Siebel Build Process Build Server RTC Server Storage Server Sif1* Sif2* Sif3 Sif4 1. Identify Files that have changed in current release (includes sif’s, workflows, DDL, Ref Data files) 2. Bulk Import Sifs 1. Full Compile Package 1. Store compiled SRF Sif1* Sif2* SRF 1. Store workflows 2. Static content
- 27. An Example IKEA manual: Siebel Deployment Target Server Storage Server SRF/Workflow deployment 1. Lock Siebel Project 2. SIF import a) Bulk import of Sifs 3. Workflows a) Import Workflows b) Deploy Workflows c) Activate Workflows 4. Stop Server 5. Deploy DDL 6. SRF deploy a) Install new SRF b) Generate Browser script 7. Start Server Ref Data Deployment Package Sif1 Sif2 WF1 WF2
- 28. While we made lots of progress, there are still a few work in progress item • Unit test automation • Unsupported activities or no API • Performance • Configuration Management skills – the curse of the configurators • Common Objects • Operations – the last mile… All is good then with Systems of Record?!? …This is where it comes undone (so far…)
- 29. Some thoughts on the usual adoption curve Read more on my blog: http://notafactoryanymore.com/2015/01/09/the-winding-road-to-devops-maturity/
- 30. There is not one “right” tooling solution The search for the right tooling Technology Mix Skills Existing Licenses Need for Support
- 31. But at some level you need to integrate
- 32. Environment BuildReporting Delivery Environments Requirements Management Data Warehouse Status of Project Health of Build Defect Rate Duration of Deployment Workflow Management Source Control Build Server Build Scheduler Build Store Initiate Initiate Initiate Extract Store Test Management Automated Manual Defect Retrofit Requirement Design Tooling Integrated Development Environment Environment Configuration Environment Design Environment Build Scheduler Environment Monitoring Functional Technical Build Deploy Deploy Deploy Requirement Implementation Design Development Test Production Virtual Server Provisioning Build Governance Source Code Build Version Technology Documentation PromotionPath Automated Regression Cycle Automated Regression Cycle Automated Regression Cycle Deploy Scheduler Portfolio, Program and Project Management Agile Lifecycle Management Portfolio Management Service Management / Kanban Application Lifecycle Management Project Management (Risk, Issue, etc.) Enterprise Planning Idea Generation Demand Management Idea Prioritisation Mirco’s more detailed Reference Model
- 33. Read more on DevOps • Accenture’s DevOps offering and reference material: – http://www.accenture.com/devops • Mirco’s blogs: – http://notafactoryanymore.com – http://notafactoryanymore.com/2015/01/09/the-winding-road-to-devops-maturity/ – http://notafactoryanymore.com/2015/01/28/how-to-support-multi-speed-it-with-devops- and-agile/ – http://notafactoryanymore.com/2015/03/26/what-computer-games-can-teach-us-about- maturity-models-choose-your-own-devops-adventure/ Further References