Leave a great legacy by not leaving the legacy behind.

1. Leave a great legacy by
not leaving the legacy behind

2. 2
“CHANGE IS THE ONLY THING
THAT IS CONSTANT”
“DON’T TOUCH IT IF
IT AINT BROKEN”

3. 3
Arun N
Senior Engineering Manager - Cloud, DevTools & Platform
@indfo linkedin.com/in/arun-n
14 years in Dev ‘&’ Ops
Entrepreneur, Student, Photographer & Traveller
linkedin.com/company/tesco-bengaluru

4. 4
“rarely, if ever,
we live in the present”
if we create an exciting path to the future, the past stays as past...

5. 5
a part of history that you carry forward

6. 6
software that’s hard to replace!

7. 7
Maybe…
• Still making money!
… resisting change & dragging others down?
• High domain knowledge, great employees
… are they sitting on past laurels?
… is it driving low motivation levels
• Is it a problem?

8. 8
Enterprise DevOps Adoption
In Business units
31%
In Small projects
29%
Org Wide
Adoption
21%
Not Adopting
12%
Don’t Know
7%
DEVOPS ADOPTION
WQR2016 State of DevOps 2016

9. 9
What constitutes legacy?
In Business units
31%
In Small projects
29%
Org Wide
Adoption
21%
Not Adopting
12%
Don’t Know
7%
DEVOPS ADOPTION
WQR2016 State of DevOps 2016

10. 10
What does this data lead to?
• Are there more legacy projects than we think?
• Large pockets enterprise not automated
• No focus on old projects
• Do they drive value
• Do they leak money

11. 11
What is Legacy?
Highly
coupled
environment
Monolithic
Low test
coverage
Slow change
management

12. 12
Strategies
Ignore!IncrementalBig Bang!
• High Risk
• Rewrite, adopt new
• Adoption issues
• Introduce layer of abstraction
• Pilot small projects
• Any value?
• Is there a future?
• Both at product and component
level

13. 13
Case studies
Highly
coupled
environment
Monolithic
Low test
coverage
Slow change
management
Ignore!IncrementalBig Bang!Problems
Strategies

14. 14
Case 1
Highly
coupled
environment
Monolithic
Low test
coverage
Slow change
management
Large revenue generator
e-commerce platform
4 Weeks of manual testing
2 Releases a year
People dependent Low risk appetite
Data dependency on older systems Adoption to new is a challenge
Ignore!IncrementalBig Bang!
10+ years of development

15. 15
Case 1: Starting point
• Build a core team - Passionate
• Most important ingredient - domain knowledge
• Supplement team with technology superstars
• Take people along
• Leadership - eye on old and new
• Don’t drift back

16. 16
Case 1: Start small
• Look inwards (non dependent changes)
• Incremental changes
• Rebase frequently
• Reduce the risks
• Fail cheap
• Focus on external interfaces later

17. 17
Case 1: Approach
• Testing automation
• Strategically increase test coverage
• Focus more on ‘end to end’ testing
• Run a parallel scrum team to automate
• BDD driven >> Smoke test >> Regression pack
• CI/CD
• Infra automation, pass ownership to developers
• Culture change happens in parallel

18. 18
Case 1: Where are they now?
• On the cloud (literally!)
• Happy, motivated, agile, culturally open
• Heavily automated
• Chat-Ops
• Visualize everything
• Canary deployments
• MTTR - release anytime

19. 19
“Legacy is never a point of time state”
Anyone who does not change becomes a legacy

20. 20
Case 2
Highly
coupled
environment
Monolithic
Low test
coverage
Slow change
management
Large number of interfaces
e-commerce platform
Overly customised packaged solution
Very few releases a year
People dependent Large customer sentiments
Loads of manual processes
Ignore!IncrementalBig Bang!
500+ Developers (at peak)

21. 21
Case 2: Starting point
• Don’t sit on past laurels
• How to make this place exciting for all
• Customers and Developer's
• Customer first approach
• Co-creating the product along with tech & business
• Low time to market

22. 22
Case 2: Don’t ignore Technology
• Follow industry standards (to the least)
• Don’t attempt moonshots, find the sweet spot
• Automate everything
• Continuous Delivery
• Agile

23. 23
Case 2: Approach
• Classify work into (and create champions)
• Process
• Technology
• People changes
• Flexible to change
• SOA based architecture
• Test quickly – shift left
• Zero touch deployment

24. 24
“Slow down,
only to run faster…”

25. 25
Case 2: Where are they now?
• Fully automated
• Highly motivated
• Super fast time to market
• Monitoring everything
• Ready for production anytime

26. 26
Learnings
• Break the monoliths
• Service-oriented architectures
• Abstract legacy systems
• Duplication of data in/outside legacy system
• Automating parts of the lifecycle – testing, infra

27. 27
Learnings
• DevOps is everyone's responsibility
• Leverage existing capabilities, invest in resources
• Always take it to the next level
• Track the industry trends
• Adapt, change, evolve

28. 28
“It’s about creating a future that
is so far more exciting, lucrative
& compelling that one doesn't
have to look back”

29. 29
“What brought you here,
won’t take you anywhere”
Create new legacies!

30. 30
Thank you.
@indfo linkedin.com/in/arun-n