Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Enabling The DevOps Culture At Organization


Published on

DevOps is the most heard buzzword at this moment and also the confusing one. For many people the term means automation or a new job role. The primary characteristic of DevOps culture is increased collaboration between the roles of development and operations. There are some important cultural shifts, within teams and at an organizational level that is required to support this collaboration. Even with the best tools, DevOps is just another buzzword if you don’t have the right culture. As an organization how can you adopt the culture required for DevOps? How to start with the new cultural transformation? Are you creating another silo for the team? Are you ready to embrace the change of mindset? In this talk I am going to focus on what are the changes you need to welcome DevOps culture to your organization and what sort of benefits you can extract by doing that. We will discuss the challenges and also the solutions for the problems.

The session will be suitable for everyone who want to start the DevOps journey as well as those who already started but want to validate if they are doing it right or wrong.

Published in: Leadership & Management
  • Be the first to comment

Enabling The DevOps Culture At Organization

  1. 1. ENABLING THE DEVOPS CULTURE AT ORGANIZATION M. Mizanur Rahman 1st – 3rd December, 2017 | Westin, Hyderabad, INDIA
  2. 2. What is DevOps? © AgiVetta Consulting 2016
  3. 3. Remember this?
  4. 4. Dev-Ops • all the people involved in developing the product • Product manager • Developers • QA engineer • Software architects • Analysts • and other kinds of disciplines • Dev - Developers • Ops – Operations (IT) • Systems engineers • system administrators • operations staff • release engineers • DBAs • network engineers • security professionals • and various other sub-disciplines and job titles
  5. 5. The definition • DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.
  6. 6. Why DevOps matters?
  7. 7. Top 5 reasons to adopt DevOps • Improve deployment frequency • Achieve faster time to market • Lower failure rate of new releases • Shorten lead time between fixes • Improve mean time to recovery
  8. 8. Key DevOps Concepts • Bridge the skills gap • Share information • Consistency • Increased accountability • Embrace failure
  9. 9. DevOps is not NoOps • Some of us thinks that DevOps means that developers are taking over operations and doing it themselves. So no need of Ops – NoOps • Since we are more on cloud infrastructure, we do not need any in house IT operations team or previously known as system guys ??!!! • We have to remember that some parts of operations need to be automated, that means that either we ops people do some automation development, or developers are writing “operations” code, or both
  10. 10. DevOps is Not (Just) Tools • It is not just implementing set of automation tools. • Tools are required but they should not be called DevOps • But it also does not mean that we do not need any tools for DevOps.
  11. 11. DevOps is Not (Just) Culture • Culture can not be grown or changed overnight. • The resistance is higher when we try to push something to existing culture • It is more about the Mind Set
  12. 12. DevOps is Not (Just) Devs and Ops • It is about everyone who is participating in the delivery of the software or service
  13. 13. DevOps is Not (Just) A Job Title • We just can not give anyone the title of DevOps just for no reason • The skills and goal is important than having a nice job title. • If we don’t adopt the values and principles of DevOps, which require change at an overall system level not simply within a given team, we won’t get all the benefits.
  14. 14. DevOps is Not Everything
  15. 15. DevOps vs Traditional approach • Collaboration Oriented • Structured and Substantially (or Wholly) Automated • Self-Service Oriented • Business Focused • Designed for Change • Silo Driven • Snowflake Driven and Mostly Manual • “IT Ticket” Oriented • Function Focused • Change Averse
  16. 16. DevOps – principles
  17. 17. DevOps tools set - infrastructure
  18. 18. Continuous delivery and releases
  19. 19. Culture of collaboration
  20. 20. 3 principles for DevOps
  21. 21. Four cornerstones of DevOps • Agile • Collaborate • Standardize • Automation
  22. 22. Is DevOps Agile? • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan
  23. 23. Summary • It’s about mindset • It’s about customer • It’s about flow • It’s about collaboration • It’s about taking pride of delivered services or works. • It’s about being agile
  24. 24. Enabling DevOps at organizations • Transformation • Product over Process • High-performance teams • Futureproof
  25. 25. M. Mizanur Rahman CSM, CSPO, CSD, CSP, REP, CAL 1, SA +8801709651003 Thank You