Yashasree barve power of dev ops - ai 2012 - 1.0-share


Published on

My presentation at Agile India 2012 about how we deployed DevOps in our Agile Enterprise.

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Yashasree barve power of dev ops - ai 2012 - 1.0-share

  1. 1. The power of DevOps Transforming a big Enterprise group into a super agile one Yashasree Barve Tata Consultancy Services
  2. 2. About Me Technologist @ TCS since last 14 years An Agile Developer & Architect since 2007 & I'm lovin' it
  3. 3. Not so long ago <ul><li>There lived an Enterprise </li></ul>
  4. 4. An Enterprise with <ul><li>Well Established Development Group </li></ul>
  5. 6. An Enterprise with <ul><li>A well established Operations Group </li></ul><ul><li>with Well set processes </li></ul>
  6. 8. An Enterprise with <ul><li>Well defined Environments </li></ul>
  7. 11. Brought us many advantages <ul><li>Happy Sponsors </li></ul><ul><li>Great Return on Investment </li></ul><ul><li>Reduced Time to Market </li></ul>
  8. 13. <ul><li>agile = to be able to move quickly </li></ul>
  9. 14. Being agile for Dev Team Test Match Release Once in 3 months One Day T 20 Release Once per month Release Many times a week
  10. 15. Being agile for Ops team Some Tickets More Tickets Many Many More Tickets
  11. 16. Being agile <ul><li>Really brought in its own </li></ul><ul><li>Challenges </li></ul>
  12. 17. We faced challenges such as High time to take changes to production Overhead of processes to move code across environments Discomfort With frequent releases & ~zero documentation Longer time to debug issues in production Low confidence in deployments
  13. 18. It all often ended in
  14. 19. Main Reasons for This Divide <ul><li>Not to forget </li></ul><ul><li>Different Hierarchies & Departments </li></ul>
  15. 20. For us DevOps started as
  16. 21. & Building Relationship
  17. 22. What is DevOps? <ul><li>Well I think </li></ul><ul><li>It is </li></ul><ul><li>What we can make out of it </li></ul>
  18. 23. What DevOps meant to us
  19. 24. Piloting DevOps <ul><li>The most widely used Application </li></ul><ul><li>in the Enterprise </li></ul>
  20. 25. Structure of our team
  21. 26. Thinking out aloud <ul><li>How we aligned ourselves to DevOps </li></ul>Process Technology People
  22. 27. The People Challenges <ul><li>“ WE ” don’t know how “ THEY ” function </li></ul>
  23. 28. Face Time – It Matters <ul><li>Sitting Together </li></ul><ul><li>Video Conference </li></ul><ul><li>Tele Conference </li></ul><ul><li>WebEx </li></ul>
  24. 29. Collaborate <ul><li>Deploy / Debug production issues together </li></ul><ul><li>Testing Party Together </li></ul><ul><li>Proactively Inform issues to one another </li></ul>
  25. 30. Dare to Share <ul><li>Agile </li></ul><ul><li>Functionality </li></ul><ul><li>Deployment </li></ul><ul><li>Monitoring Tools </li></ul><ul><li>Most troublesome modules </li></ul>Dev Team Ops Team
  26. 31. Optimal Documentation <ul><li>Ops team now accesses the story board </li></ul><ul><li>Dev Team updates a Wiki page to detail deployment requests for production </li></ul><ul><ul><li>Date of deployment </li></ul></ul><ul><ul><li>Tag number </li></ul></ul><ul><ul><li>Functional changes that go in the release </li></ul></ul>
  27. 32. Process Challenges <ul><li>Heavy processes to move code to production </li></ul><ul><li>Debugging production issues </li></ul><ul><li>Ops team did not appreciate Agile </li></ul>
  28. 33. Getting Engaged
  29. 34. Opening doors to Ops
  30. 35. Opened doors for Dev also Read only access to app directory Access to Error Logs Access to Execute Tasks
  31. 36. Engineering Practices <ul><li>Automated deployment scripts </li></ul><ul><li>Continuous Integration </li></ul>AUTOMATION
  32. 37. Less Tickets Movement <ul><li>No more tickets for Deployments till QA </li></ul><ul><li>Just drop an email with a CC to a group </li></ul><ul><li>Ticket auto-generated for tracking purpose </li></ul>
  33. 38. Led us to Ticketless travel
  34. 39. Ticket Busters <ul><li>Identify the most troublesome tickets through Support teams </li></ul><ul><li>Bust those through Do It Yourself screens </li></ul>
  35. 40. Technology Enablers <ul><li>Virtualization: Spin off servers on the fly </li></ul><ul><li>Hoptoad – The Error App </li></ul><ul><ul><li>Debug prod issues faster </li></ul></ul><ul><ul><li>Analyze a trend of issues proactively </li></ul></ul>
  36. 41. How it helped <ul><li>Frictionless Teams and Deployments </li></ul><ul><li>Light processes </li></ul><ul><li>Ops team felt belonged to a product </li></ul><ul><li>Ops team now prepared to cater to frequent releases </li></ul><ul><li>More confidence about the product </li></ul><ul><li>Open and Approachable Environment </li></ul>
  37. 42. Challenges we faced <ul><li>Resistance to change and being open </li></ul><ul><li>Security concerns </li></ul><ul><li>Working shifts </li></ul><ul><li>Extra work! </li></ul>
  38. 43. Road Ahead <ul><li>Ticketless travel to production </li></ul><ul><li>Expanding to other technologies </li></ul><ul><li>Continue Collaboration </li></ul><ul><li>Extend to other Agile teams as well as Ops teams </li></ul><ul><li>So Wish us Luck! </li></ul>
  39. 44. <ul><li>Happy to take Questions </li></ul><ul><li>Hope This Session Helps! </li></ul><ul><li>Thank you </li></ul>?