O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

DevOps introduction

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Próximos SlideShares
Devops online training ppt
Devops online training ppt
Carregando em…3
×

Confira estes a seguir

1 de 177 Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Semelhante a DevOps introduction (20)

Anúncio

Mais recentes (20)

DevOps introduction

  1. 1. DevOps DevOps is a software engineering culture and practice that aims at unifying software development (Dev) and software operation (Ops). DevOps 01 Introduction DevOps Process M.M. Heegstra
  2. 2. DevOps DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases, in close alignment with business objectives. DevOps 01 Introduction DevOps Process M.M. Heegstra
  3. 3. DevOps The main characteristic of the DevOps movement is to strongly advocate automation and monitoring all the steps of software construction. From integration, testing, releasing to deployment and infrastructure management. DevOps 01 Introduction DevOps Process M.M. Heegstra
  4. 4. DevOps Questions 1. What aims DevOps? 2. What is the main characteristic of the DevOps movement? DevOps 01 Introduction DevOps Process M.M. Heegstra
  5. 5. DevOps Questions & Answers 1. What aims DevOps? • Unifying software development and software operation • Shorter development cycles • Increased deployment frequency • More dependable releases 2. What is the main characteristic of the DevOps movement? • Advocate automation and monitoring all the steps of software construction DevOps 01 Introduction DevOps Process M.M. Heegstra
  6. 6. The use of DevOps DevOps is not only for supporting IT, it can also be used to support the business strategy and to improve business processes. The intention of DevOps can be to establish the software and IT services supply chain to support the business and to manage the whole process to maturity. DevOps 01 Introduction DevOps Process M.M. Heegstra
  7. 7. The use of DevOps The DevOps framework should support business outcomes directly, not only collaboration with development and operation for IT services. The use of DevOps should be evaluated by business outcome, not by an IT project scope and IT outcome. DevOps 01 Introduction DevOps Process M.M. Heegstra
  8. 8. DevOps Process The use of DevOps DevOps is not a single tools, methodology, skill set or organization structure. DevOps is a framework combining all of these for organizations to establish stream-lined processes to enable the business to operate faster and react to changes more quickly. DevOps can also enable maturity by using the Plan-Do- Check-Act cycle. DevOps 01 Introduction M.M. Heegstra
  9. 9. The use of DevOps Questions 1. What can DevOps be used for? 2. What is an intention of DevOps? 3. What should the DevOps framework support? 4. By what should the DevOps use be evaluated? 5. What is DevOps? 5. By using which cycle can DevOps enable maturity? DevOps 01 Introduction DevOps Process M.M. Heegstra
  10. 10. The use of DevOps Questions & Answers 1. What can DevOps be used for? • Supporting IT • Supporting business strategy • Improve business processes 2. What is an intention of DevOps? • To establish software and IT services supply chain to support the business • To manage the whole process to maturity DevOps 01 Introduction DevOps Process M.M. Heegstra
  11. 11. The use of DevOps Questions & Answers 3. What should the DevOps framework support? • Business outcomes • Collaboration between development and operation 4. By what should the DevOps use be evaluated? • By business outcome DevOps 01 Introduction DevOps Process M.M. Heegstra
  12. 12. The use of DevOps Questions & Answers 5. What is DevOps? • A framework combining tools, methodology, skill sets and organization structures 6. By using which cycle can DevOps enable maturity? • The Plan-Do-Check-Act cycle DevOps 01 Introduction DevOps Process M.M. Heegstra
  13. 13. DevOps Culture DevOps initiatives can create cultural change in companies by transforming the way Operation, Developers and Testers collaborate during the development and delivery processes. Getting these groups to work cohesively is a critical challenge in DevOps adoption. DevOps 01 Introduction DevOps Process M.M. Heegstra
  14. 14. DevOps Culture DevOps principles demand strong interdepartmental communication. Team building and other employee engagement activities are often used to create an environment that fosters this communication and cultural change. DevOps 01 Introduction DevOps Process M.M. Heegstra
  15. 15. DevOps Culture Questions 1. What can be created by DevOps initiatives? 2. What is a critical challenge in DevOps adoption? 3. What can be done to create interdepartmental communication? DevOps 01 Introduction DevOps Process M.M. Heegstra
  16. 16. DevOps Culture Questions & Answers 1. What can be created by DevOps initiatives? • Cultural change 2. What is a critical challenge in DevOps adoption? • Getting Operation, Developers and Testers to work cohesively 3. What can be done to create interdepartmental communication? • Team building and other employee engagement DevOps 01 Introduction DevOps Process M.M. Heegstra
  17. 17. Goals The goals of DevOps span the entire delivery pipeline. They include: 1. Improved deployment frequency 2. Faster time to market 3. Lower failure rate of new releases 4. Shortened lead time between fixes 5. Faster mean time to recovery DevOps 01 Introduction DevOps Process M.M. Heegstra
  18. 18. Goals Simple processes become increasingly programmable and dynamic, using a DevOps approach. DevOps aims to maximize the predictability, efficiency, security, and maintainability of operational processes. Very often, automation supports this objective. DevOps 01 Introduction DevOps Process M.M. Heegstra
  19. 19. DevOps Process Goals DevOps integration targets product delivery, continuous testing, quality testing, feature development, and maintenance releases in order to improve reliability and security and provide faster development and deployment cycles. Many of the ideas (and people) involved in DevOps came from the enterprise systems management and agile software development movements. DevOps 01 Introduction M.M. Heegstra
  20. 20. Goals Questions 1. What is the span of the goals of DevOps? 2. What are five goals of DevOps? 3. What is an outcome of using a DevOps approach? 4. What aims DevOps to maximize? 5. What targets DevOps integration? DevOps 01 Introduction DevOps Process M.M. Heegstra
  21. 21. Goals Questions & Answers 1. What is the span of the goals of DevOps? • The entire delivery pipeline 2. What are five goals of DevOps? • Improved deployment frequency • Faster time to market • Lower failure rate of new releases • Shortened lead time between fixes • Faster mean time to recovery DevOps 01 Introduction DevOps Process M.M. Heegstra
  22. 22. Goals Questions & Answers 3. What is an outcome of using a DevOps approach? • Simple processes become increasingly programmable and dynamic 4. What aims DevOps to maximize? • Predictability • Efficiency • Security • Maintainability of operational processes DevOps 01 Introduction DevOps Process M.M. Heegstra
  23. 23. Goals Questions & Answers 5. What targets DevOps integration? • Product delivery • Continuous testing • Quality testing • Feature development • Maintenance releases DevOps 01 Introduction DevOps Process M.M. Heegstra
  24. 24. Benefits Benefits when using DevOps are: 1. Significantly shorter time to market 2. Improved customer satisfaction 3. Better product quality 4. More reliable releases 5. Improved productivity and efficiency 6. Increased ability to build the right product by fast experimentation DevOps 01 Introduction DevOps Process M.M. Heegstra
  25. 25. Benefits Questions 1. What are the benefits when using DevOps? DevOps 01 Introduction DevOps Process M.M. Heegstra
  26. 26. Benefits Questions & Answers 1. What are the benefits when using DevOps? • Significantly shorter time to market • Improved customer satisfaction • Better product quality • More reliable releases • Improved productivity and efficiency • Increased ability to build the right product by fast experimentation DevOps 01 Introduction DevOps Process M.M. Heegstra
  27. 27. DevOps WorkFlow DevOps 01 Introduction DevOps Process M.M. Heegstra
  28. 28. Toolchain stages The stages in a DevOps toolchain are: 1. Plan 2. Code 3. Build 4. Test 5. Release 6. Deploy 7. Operate 8. Monitor DevOps 01 Introduction DevOps Process M.M. Heegstra
  29. 29. Toolchain stages Questions 1. What are the stages in a DevOps toolchain? DevOps 01 Introduction DevOps Process M.M. Heegstra
  30. 30. Toolchain stages Questions & Answers 1. What are the stages in a DevOps toolchain? 1. Plan 2. Code 3. Build 4. Test 5. Release 6. Deploy 7. Operate 8. Monitor DevOps 01 Introduction DevOps Process M.M. Heegstra
  31. 31. Tools categories As DevOps is intended to be a cross- functional mode of working, rather than a single DevOps tool there are sets of multiple tools, the toolchains. DevOps 01 Introduction DevOps Process M.M. Heegstra
  32. 32. Tools categories The DevOps tools fit into the categories: 1. Code | Code development and review, source code management tools, code merging 2. Build | Continuous integration tools, build status 3. Test | Continuous testing tools that provide feedback on business risks 4. Package | Artefact repository, application pre-deployment staging 5. Release | Change management, release approvals, release automation 6. Configure | Infrastructure configuration and management, infrastructure as Code tools 7. Monitor | Applications performance monitoring, end-user experience DevOps 01 Introduction DevOps Process M.M. Heegstra
  33. 33. Tools categories Questions 1. What are the categories for DevOps tools? DevOps 01 Introduction DevOps Process M.M. Heegstra
  34. 34. Tools categories Questions & Answers 1. What are the categories for DevOps tools? 1. Code 2. Build 3. Test 4. Package 5. Release 6. Configure 7. Monitor DevOps 01 Introduction DevOps Process M.M. Heegstra
  35. 35. The enterprise system The enterprise holds both the System of Engagement (SoE) and the System of Record (SoR). The SoE is focused on speed and the SoR is focused on business continuity. The problem is how the SoR can adapt quickly to changes to the SoE to maintain business continuity. DevOps 01 Introduction DevOps Process M.M. Heegstra
  36. 36. The enterprise system The SoR in most enterprises is struggling with the use of legacy applications/systems and can be helped through the use of DevOps building stream-lined processes with just-in-time (JIT) concepts. DevOps 01 Introduction DevOps Process M.M. Heegstra
  37. 37. DevOps Process The enterprise system Enterprise DevOps is not only an enhancement of Agile development and continuous delivery but also IT service management and application management to enable growth of the business and to maintain business continuity. DevOps 01 Introduction M.M. Heegstra
  38. 38. The enterprise system Questions 1. Where stands SoE for? 2. Where stands SoR for? 3. What is the focus of SoE? 4. What is the focus of SoR? 5. What is the problem of SoE and SoR? 6. What is the struggling of SoR? 7. Where stand JIT for? 8. What are the enhancements of DevOps? DevOps 01 Introduction DevOps Process M.M. Heegstra
  39. 39. The enterprise system Questions 1. Where stands SoE for? • System of Engagement 2. Where stands SoR for? • System of Record 3. What is the focus of SoE? • Speed 4. What is the focus of SoR? • Business continuity DevOps 01 Introduction DevOps Process M.M. Heegstra
  40. 40. The enterprise system Questions 5. What is the problem of SoE and SoR? • How the SoR can adapt quickly to changes to the SoE to maintain business continuity 6. What is the struggle of SoR in most enterprises? • The use of legacy applications 7. Where stands JIT for? • Just In Time DevOps 01 Introduction DevOps Process M.M. Heegstra
  41. 41. The enterprise system Questions 8. What are the enhancements of DevOps? • Agile development • Continuous delivery • The growth of IT service management and Application management • To maintain business continuity DevOps 01 Introduction DevOps Process M.M. Heegstra
  42. 42. Just In Time JIT is an inventory management method whereby materials, goods, and labour are scheduled to arrive or be replenished exactly when needed in the production process. DevOps 01 Introduction DevOps Process M.M. Heegstra
  43. 43. Just In Time The goal of DevOps is to establish stream-lined just-in- time (JIT) business processes. DevOps aims to maximize business outcomes, such as increasing sales and profitability, enhancing business speed, or minimizing operating cost, by aligning just-in-time business processes. DevOps 01 Introduction DevOps Process M.M. Heegstra
  44. 44. Just In Time Questions 1. What is JIT? 2. What is the outcome of establish a streamlined JIT business processes? DevOps 01 Introduction DevOps Process M.M. Heegstra
  45. 45. Just In Time Questions & Answers 1. What is JIT? • An inventory management method • Materials, goods and labour are scheduled exactly when needed 2. What is the outcome of establish a streamlined JIT business processes? • Increasing sales and profitability • Enhancing business speed • Minimizing operating cost DevOps 01 Introduction DevOps Process M.M. Heegstra
  46. 46. DevOps Process Supply Chain DevOps means establishing the IT service supply chain in the business in the same way as the supply chain for other products is embedded within the business. It is a big paradigm shift from software delivery to providing IT services. DevOps 01 Introduction M.M. Heegstra
  47. 47. Supply Chain Questions 1. What is a big paradigm shift? DevOps 01 Introduction DevOps Process M.M. Heegstra
  48. 48. Supply Chain Questions & Answers 1. What is a big paradigm shift? • Establishing the IT service supply chain in the same way as the supply chain for other products are embedded within the business • Software delivery to providing IT services DevOps 01 Introduction DevOps Process M.M. Heegstra
  49. 49. DevOps Process Architecture From an architecture perspective, DevOps needs to establish an automated quick deployment system. There are many methodologies and tools which can be utilized. Each organization has to think and build up their own DevOps process to improve the business. DevOps 01 Introduction M.M. Heegstra
  50. 50. Architecture Questions 1. What does DevOps needs to establish? 2. How can DevOps do that? DevOps 01 Introduction DevOps Process M.M. Heegstra
  51. 51. Architecture Questions & Answers 1. What does DevOps needs to establish? • An automated quick deployment system 2. How can DevOps do that? • With methodologies and tools DevOps 01 Introduction DevOps Process M.M. Heegstra
  52. 52. Understanding the concepts When implementing DevOps, there are many sources of knowledge, methodologies, practices, and tools to choose from. Understanding the concepts of DevOps is important for the staff to carry out the processes efficiently by following the right processes. DevOps 01 Introduction DevOps Process M.M. Heegstra
  53. 53. Architecture Questions 1. Which sources can be used when implementing DevOps? 2. Why is understanding the concepts of DevOps important? DevOps 01 Introduction DevOps Process M.M. Heegstra
  54. 54. Architecture Questions & Answers 1. Which sources can be used when implementing DevOps? • Knowledge • Methodologies • Practices • Tools 2. Why is understanding the concepts of DevOps important? • The staff can carry out the processes more efficiently when following the right processes DevOps 01 Introduction DevOps Process M.M. Heegstra
  55. 55. The pillars and foundation DevOps consists of 3 pillars and a foundation 1. Disciplined Agile 2. Continuous Delivery 3. IT Service Management 4. TPS (lean) concept as foundation DevOps 01 Introduction DevOps Process M.M. Heegstra
  56. 56. Architecture Questions 1. Of which pillars consists DevOps? 2. Of which foundation consists DevOps? DevOps 01 Introduction DevOps Process M.M. Heegstra
  57. 57. Architecture Questions & Answers 1. Of which pillars consists DevOps? • Discipline Agile • Continuous Delivery • IT Service Management 2. Of which foundation consists DevOps? • TPS (lean) concept as foundation DevOps 01 Introduction DevOps Process M.M. Heegstra
  58. 58. The pillars and foundation | Disciplined Agile A disciplined Agile development team is a key to the success of a DevOps implementation. Disciplined Agile means: 1. Stabilized Velocity 2. Adaptability for change 3. Always release high quality bug free code DevOps 01 Introduction DevOps Process M.M. Heegstra
  59. 59. The pillars and foundation | Disciplined Agile A more frequent and faster release cycle of IT services to react to business changes depends on the speed of development. The quality of work is the most important item and this can be supported by splitting work into small tasks. DevOps 01 Introduction DevOps Process M.M. Heegstra
  60. 60. The pillars and foundation | Disciplined Agile The concept of JKK (Ji-Koutei-Kanketsu) helps keep a high quality of work. JKK means 100% completion of an item. DevOps 01 Introduction DevOps Process M.M. Heegstra
  61. 61. The pillars and foundation | Disciplined Agile The Definition of Done or completion must be defined clearly for everybody. The product owner may change the mission from not only managing product backlogs but also by planning the operating cost of IT service. DevOps 01 Introduction DevOps Process M.M. Heegstra
  62. 62. The pillars and foundation | Disciplined Agile Questions 1. What is a key to success of a DevOps implementation? 2. What does Disciplined Agile means? 3. Frequent and faster release cycle to react to business changes depends on? 4. What is the most important item? 5. And how it be supported? 6. What means JKK? 7. What has to be defined clearly for everybody? 8. What may the product owner change? DevOps 01 Introduction DevOps Process M.M. Heegstra
  63. 63. The pillars and foundation | Disciplined Agile Questions & Answers 1. What is a key to success of a DevOps implementation? • A disciplined Agile development team 2. What does Disciplined Agile means? • Stabilized Velocity • Adaptability for change • Always release high quality bug free code DevOps 01 Introduction DevOps Process M.M. Heegstra
  64. 64. The pillars and foundation | Disciplined Agile Questions & Answers 3. Frequent and faster release cycle to react to business changes depends on? • The speed of development 4. What is the most important item? • The quality of work 5. And how can it be supported? • By splitting work into small tasks DevOps 01 Introduction DevOps Process M.M. Heegstra
  65. 65. The pillars and foundation | Disciplined Agile Questions & Answers 6. What means JKK? • 100% completion of an item 7. What has to be defined clearly for everybody? • The Definition of Done 8. What may the product owner change? • Managing product backlogs • Planning operation cost of IT service DevOps 01 Introduction DevOps Process M.M. Heegstra
  66. 66. The pillars and foundation | Continuous Delivery Continuous delivery is the automated implementation of the application build, deploy, test and release processes. A key focus is on testing such as acceptance testing and performance testing. DevOps 01 Introduction DevOps Process M.M. Heegstra
  67. 67. The pillars and foundation | Continuous Delivery Every organization will have differences in the implementation of their deployment pipeline depending on their value stream for releasing software. A key success factor is to establish only a single deployment pipeline for IT services. DevOps 01 Introduction DevOps Process M.M. Heegstra
  68. 68. The pillars and foundation | Continuous Delivery Questions 1. What is Continuous Delivery? 2. What is the key focus? 3. The differences in implementation of deployment pipelines is depended on? 4. What is the key success factor? DevOps 01 Introduction DevOps Process M.M. Heegstra
  69. 69. The pillars and foundation | Continuous Delivery Questions & Answers 1. What is Continuous Delivery? • The automated implementation of application build, deploy, test and release processes 2. What is the key focus? • Testing, acceptance and performance DevOps 01 Introduction DevOps Process M.M. Heegstra
  70. 70. The pillars and foundation | Continuous Delivery Questions & Answers 3. The differences in implementation of deployment pipelines is depended on? • The value stream for releasing software 4. What is a key success factor? • Establishing a single deployment pipeline for IT services DevOps 01 Introduction DevOps Process M.M. Heegstra
  71. 71. The pillars and foundation | IT service management As technology is a core component of most business processes, continuous or high availability of IT services is critical to the survival of the business as a whole. This is achieved by introducing risk reduction measures and recovery options. DevOps 01 Introduction DevOps Process M.M. Heegstra
  72. 72. The pillars and foundation | IT service management Like all elements of IT service management, successful implementation of the service continuity process can only be achieved with senior management commitment and the support of all members of the organization. Ongoing maintenance of the recovery capability is essential if it is to remain effective. DevOps 01 Introduction DevOps Process M.M. Heegstra
  73. 73. The pillars and foundation | IT service management Service continuity is an essential part of the warranty (fitness for purpose) of a service. If service continuity cannot be maintained and/or restored in accordance with the requirements of the business, then the business will not experience the value that has been promised. Without continuity the utility (fitness for purpose) of the service cannot be accessed. DevOps 01 Introduction DevOps Process M.M. Heegstra
  74. 74. The pillars and foundation | IT service management Traditional IT service management (ITSM) best practice such as ITIL looks heavyweight and not suited for the quick processes of DevOps. It is necessary to think about how to reduce management workload. DevOps 01 Introduction DevOps Process M.M. Heegstra
  75. 75. The pillars and foundation | IT service management It is necessary to realign ITSM for DevOps, creating light-weight ITSM which is strictly focuses on business continuity with a set of minimum required information MRI. The MRI set for each organization depends on their business DevOps 01 Introduction DevOps Process M.M. Heegstra
  76. 76. The pillars and foundation | IT service management Questions 1. What is critical to the survival of the business as a whole? 2. How is this achieved? 3. How can successful implementation of service continuity process be achieved? 4. How can it be remain effective? 5. What is an essential part of the warranty of a service? 6. What will happen if service continuity cannot be maintained and/or restored? 7. What cannot be accessed without continuity? 8. Warranty and utility is also called? DevOps 01 Introduction DevOps Process M.M. Heegstra
  77. 77. The pillars and foundation | IT service management Questions & Answers 1. What is critical to the survival of the business as a whole? • Continuous or high availability of IT services 2. How is this achieved? • By introducing risk reduction measures and recovery options 3. How can successful implementation of service continuity process be achieved? • With senior management commitment and support of the whole organization 4. How can it be remain effective? • With ongoing maintenance of the recovery capability. DevOps 01 Introduction DevOps Process M.M. Heegstra
  78. 78. The pillars and foundation | IT service management Questions & Answers 5. What is an essential part of the warranty of a service? • Service continuity 6. What will happen if service continuity cannot be maintained and/or restored? • The business will not experience the promised value 7. What cannot be accessed without continuity? • The utility of service 8. Warranty and utility is also called? • Fitness for purpose DevOps 01 Introduction DevOps Process M.M. Heegstra
  79. 79. The pillars and foundation | TPS concept as foundation Building a stream-lined supply chain of IT services is difficult because there are many items and it is necessary to change your mind-set from the familiar existing development cycle and its methodologies. DevOps 01 Introduction DevOps Process M.M. Heegstra
  80. 80. The pillars and foundation | TPS concept as foundation The concepts of TPS (Toyota Production System), which includes JIT and automation, can help. JIT means building up a stream-lined supply chain with one-piece flow. And automation means automating as much as possible and stopping the entire process when a defect occurs. DevOps 01 Introduction DevOps Process M.M. Heegstra
  81. 81. The pillars and foundation | TPS concept as foundation The process needs to be designed and staff educated for the above two concepts. The other key issue is the management cycle of Development and Operation. This needs to be changed to work in an Agile way including synchronization between development and operation on a weekly or daily basis. DevOps 01 Introduction DevOps Process M.M. Heegstra
  82. 82. The pillars and foundation | TPS concept as foundation Questions 1. Why is it difficult to build a stream-lined IT services supply chain? 2. Where stands TPS for? 3. What means JIT? 4. What means automation? 5. What is another key issue? 6. What needs to be changed to work in an Agile way? DevOps 01 Introduction DevOps Process M.M. Heegstra
  83. 83. The pillars and foundation | TPS concept as foundation Questions & Answers 1. Why is it difficult to build a stream-lined IT services supply chain? • There are many items • To need to change the mind-set 2. Where stands TPS for? • Toyota Production System 3. What means JIT? • Building up a stream-lined supply chain with one-piece flow DevOps 01 Introduction DevOps Process M.M. Heegstra
  84. 84. The pillars and foundation | TPS concept as foundation Questions & Answers 4. What means automation? • Automating as much as possible and stopping the entire process when a defect occurs 5. What is another key issue? • The management cycle of Development and Operation 6. What needs to be changed to work in an Agile way? • The synchronization between development and operation on a weekly or daily basis DevOps 01 Introduction DevOps Process M.M. Heegstra
  85. 85. Team roles It is recommended that a DevOps team is set up in the organization in order to commit to business continuity of the IT service. The team roles are: 1. Process Master / Scrum Master 2. Service Master / Product Owner 3. DevOps Engineer 4. Gatekeeper/Release coordinator 5. Reliability Engineer (Optional) 6. Development Team 7. Operation Team DevOps 01 Introduction DevOps Process M.M. Heegstra
  86. 86. Team roles Questions 1. What are the roles in a DevOps team? DevOps 01 Introduction DevOps Process M.M. Heegstra
  87. 87. Team roles Questions & Answers 1. What are the roles in a DevOps team? • Process Master / Scrum Master • Service Master / Product Owner • DevOps engineer • Gatekeeper/Release coordinator • Reliability Engineer • Development Team • Operation Team DevOps 01 Introduction DevOps Process M.M. Heegstra
  88. 88. Team roles | Process Master/Scrum Master Leads the team and facilitates. Implements visual control across the entire process and has a strong focus on establishing a stream-lined process with one-piece flow. DevOps 01 Introduction DevOps Process M.M. Heegstra
  89. 89. Team roles | Process Master/Scrum Master Visual control means ‘Does everybody easily understand the situation by just looking at the boards without explanation?’ It does not show the status. It can be expressed the problems occurred or not. DevOps 01 Introduction DevOps Process M.M. Heegstra
  90. 90. Team roles | Service Master/Product Owner Has all the responsibility for providing IT services JIT. Managing and prioritizing product backlogs and the new additional responsibility of cost planning for the IT service. DevOps 01 Introduction DevOps Process M.M. Heegstra
  91. 91. Team roles | Service Master/Product Owner Questions 1. What are the tasks of the Process Master/Scrum Master? 2. What does visual control means? 3. What doesn’t visual control show? 4. What is a responsibility of the Process Master? DevOps 01 Introduction DevOps Process M.M. Heegstra
  92. 92. Team roles | Service Master/Product Owner Questions & Answers 1. What are the tasks of the Process Master/Scrum Master? • Leads the team and facilitates • Implements visual control across the entire process • Focus on establishing a stream-lined process with one-piece flow • Managing and prioritizing product backlogs DevOps 01 Introduction DevOps Process M.M. Heegstra
  93. 93. Team roles | Service Master/Product Owner Questions & Answers 2. What does visual control means? • Everybody easily understand the situation by just looking at the boards without explanation 3. What doesn’t visual control show? • The status 4. What is a responsibility of the Process Master? • Providing IT services JIT • Cost planning for IT services DevOps 01 Introduction DevOps Process M.M. Heegstra
  94. 94. Team roles | DevOps Engineer Has a mission to improve and maintain automated process. The engineer will examine the whole automated process and tools. There are many tools required in the DevOps process. DevOps 01 Introduction DevOps Process M.M. Heegstra
  95. 95. Team roles | DevOps Engineer Questions 1. What is a mission of a DevOps Engineer? 2. What does he examine? DevOps 01 Introduction DevOps Process M.M. Heegstra
  96. 96. Team roles | DevOps Engineer Questions & Answers 1. What is a mission of a DevOps Engineer? • To improve and maintain automated process 2. What does he examine? • The whole automated process and tools DevOps 01 Introduction DevOps Process M.M. Heegstra
  97. 97. Team roles | Gatekeeper/Release coordinator Responsible for monitoring the operational status and progress of the next release of the IT service. Make go/no go decisions about deployment according to criteria including security, compliance, regulatory requirements, maturity of operation team and their process views. DevOps 01 Introduction DevOps Process M.M. Heegstra
  98. 98. Team roles | Gatekeeper/Release coordinator Questions 1. What is the responsibility of the Gatekeeper? 2. What are decisions criteria for the go/no go? DevOps 01 Introduction DevOps Process M.M. Heegstra
  99. 99. Team roles | Gatekeeper/Release coordinator Questions & Answers 1. What is the responsibility of the Gatekeeper? • Monitoring the operational status and progress of the next release of the IT service • Make go/no go decisions about deployment 2. What are decisions criteria for the go/no go? • Security • Compliance • Regulatory requirements • Maturity of operation ream and their process views DevOps 01 Introduction DevOps Process M.M. Heegstra
  100. 100. Team roles | Reliability Engineer (Optional) Monitors the services in the development process and deal with problems with the service during its execution. Monitors the process status to ensure that the development team are following the rules of CI (Continuous Integration) and CD (Continuous Delivery) strictly. Monitors and manage the flow of complex build pipeline. Have a mission to improve the test process. DevOps 01 Introduction DevOps Process M.M. Heegstra
  101. 101. Team roles | Reliability Engineer (Optional) Questions 1. What does the Reliability Engineer monitors? 2. What are tasks of the Reliability Engineer? DevOps 01 Introduction DevOps Process M.M. Heegstra
  102. 102. Team roles | Reliability Engineer (Optional) Questions & Answers 1. What does the Reliability Engineer monitors? • The services in the development process • The process status to ensure the rules of Continuous Integration and Continuous Delivery are followed • The flow build pipeline 2. What are tasks of the Reliability Engineer? • Deal with service problems during execution • Manage the flow of complex build pipeline • Improve test process DevOps 01 Introduction DevOps Process M.M. Heegstra
  103. 103. Team roles | Development team One of the key success factors for DevOps is building up a disciplined agile team. Disciplined agile teams commit to meet release plans and quality with sustainable pace. DevOps 01 Introduction DevOps Process M.M. Heegstra
  104. 104. Team roles | Development team Questions 1. What is a key success factor for DevOps? 2. What does the development team commit? DevOps 01 Introduction DevOps Process M.M. Heegstra
  105. 105. Team roles | Development team Questions & Answers 1. What is a key success factor for DevOps? • A disciplined agile team 2. What does the development team commit? • Meet release plans • Quality with sustainable pace DevOps 01 Introduction DevOps Process M.M. Heegstra
  106. 106. Team roles | Operation team Adopt light-weight ITSM and support the design, implementation, operation, and improvement of these services within the context of an overall strategy. DevOps 01 Introduction DevOps Process M.M. Heegstra
  107. 107. Team roles | Operation team Questions 1. What does the Operation team do? DevOps 01 Introduction DevOps Process M.M. Heegstra
  108. 108. Team roles | Operation team Questions & Answers 1. What does the Operation team do? • Adopt light-weight ITSM • Support the design, implementation & operation • Improvement of these services within the context of an overall strategy DevOps 01 Introduction DevOps Process M.M. Heegstra
  109. 109. Organization It is useful to organize the DevOps team in a Service Management Office to support the Service Master. There are two types of the organization structures: 1. Flat organization for small organizations 2. Matrix organization for large and complex organizations DevOps 01 Introduction DevOps Process M.M. Heegstra
  110. 110. Organization | Flat organization The basic structure for a small team DevOps 01 Introduction DevOps Process M.M. Heegstra
  111. 111. Organization | Matrix organization Pooling experts and assigning them to each service masters as a team DevOps 01 Introduction DevOps Process M.M. Heegstra
  112. 112. Team roles | Organization Questions 1. Which types of organization structures are there? DevOps 01 Introduction DevOps Process M.M. Heegstra
  113. 113. Team roles | Organization Questions & Answers 1. Which types of organization structures are there? • Flat organizations for small organizations • Matrix organizations for large and complex organizations DevOps 01 Introduction DevOps Process M.M. Heegstra
  114. 114. DevOps Process To build-up stream-lined processes, JKK is the most effective method to guide the behavior of the DevOps team. JKK is a way of working with quality which means clear understanding of the goals, understanding the right way to work, getting the work right for 100% completion and then maintaining the required quality without inspections. DevOps 01 Introduction DevOps Process M.M. Heegstra
  115. 115. DevOps Process Process Steps: 1. Business Strategy and Planning 2. Marketing and Sales 3. Administration 4. Project Planning 5. Requirements and Design 6. Development 7. Deployment 8. Operation 9. Maintenance 10. Customer Service 11. End of Life DevOps 01 Introduction DevOps Process M.M. Heegstra
  116. 116. Team roles | DevOps Process Questions 1. What is the most effective method to guide DevOps team behavior? 2. What is the JKK way of working? 3. What are the Process Steps? DevOps 01 Introduction DevOps Process M.M. Heegstra
  117. 117. Team roles | DevOps Process Questions & Answers 1. What is the most effective method to guide DevOps team behavior? • JKK for build-up stream-lined processes 2. What is the JKK way of working? • Clear understanding of the goals • Understanding the right way to work • Getting the work right for 100% completion • Maintaining the required quality without inspections DevOps 01 Introduction DevOps Process M.M. Heegstra
  118. 118. Team roles | DevOps Process Questions & Answers 3. What are the Process Steps? 1. Business Strategy and Planning 2. Marketing and Sales 3. Administration 4. Project Planning 5. Requirements and Design 6. Development 7. Deployment 8. Operation 9. Maintenance 10. Customer Service 11. End of Life DevOps 01 Introduction DevOps Process M.M. Heegstra
  119. 119. DevOps Process | Business Strategy and Planning IT service has a close relationship with the business strategy and planning. The service master should attend business planning sessions and make recommendations about how to gain business advantages from IT services. DevOps 01 Introduction DevOps Process M.M. Heegstra
  120. 120. DevOps Process | Business Strategy and Planning Questions 1. With what has IT service a close relationship? 2. What are tasks of the Service Master? DevOps 01 Introduction DevOps Process M.M. Heegstra
  121. 121. DevOps Process | Business Strategy and Planning Questions & Answers 1. With what has IT service a close relationship? • With the business strategy and planning 2. What are tasks of the Service Master? • Attend business planning sessions • Make recommendations about how to gain business advantages from IT services DevOps 01 Introduction DevOps Process M.M. Heegstra
  122. 122. DevOps Process | Marketing and Sales The service master should discuss with marketing how to gain advantages from IT services. The service master identifies customers of IT services, gathers requirements with business value and agrees a time frame. DevOps 01 Introduction DevOps Process M.M. Heegstra
  123. 123. DevOps Process | Marketing and Sales Questions 1. What are tasks of the Service Master? DevOps 01 Introduction DevOps Process M.M. Heegstra
  124. 124. DevOps Process | Marketing and Sales Questions & Answers 1. What are tasks of the Service Master? • Discuss with marketing how to gain advantages from IT services • Identify customers of IT services • Gather requirements with business value • Agrees a time frame DevOps 01 Introduction DevOps Process M.M. Heegstra
  125. 125. DevOps Process | Administration The process master agrees how to visualize the whole process. One method is to use Obeya which can be set up for the whole process. Obeya is a war room serves two purposes, information management and on-the-spot decision making. DevOps 01 Introduction DevOps Process M.M. Heegstra
  126. 126. DevOps Process | Administration There are many visual management tools in it and team members can quickly see where they are in every aspect of the program. When the cross-functional team works together, the Obeya system enables fast and accurate decision-making, improves communication, maintains alignment, speeds information gathering, and creates an important sense of team integration. DevOps 01 Introduction DevOps Process M.M. Heegstra
  127. 127. DevOps Process | Administration Questions 1. What are tasks of the Process Master? 2. What is Obeya? 3. What is the purposes of Obeya? DevOps 01 Introduction DevOps Process M.M. Heegstra
  128. 128. DevOps Process | Administration Questions & Answers 1. What are tasks of the Process Master? • Agrees how to visualize the whole process 2. What is Obeya? • A war room DevOps 01 Introduction DevOps Process M.M. Heegstra
  129. 129. DevOps Process | Administration Questions & Answers 3. What is the purposes of Obeya? • Information management • On-the-spot, fast and accurate decision making • Improving communication • Maintaining alignment • Speed up the gathering of information • Creating an important sense of team integration DevOps 01 Introduction DevOps Process M.M. Heegstra
  130. 130. DevOps Process | Project Planning The service master organizes the service management office (SMO) and defines ground rules for the team. The service master creates the vision, goal, and value of the project, and then puts together the DevOps team members. The run-time infrastructure are defined at this stage. A value stream map of the whole process is designed. DevOps 01 Introduction DevOps Process M.M. Heegstra
  131. 131. DevOps Process | Project Planning Questions 1. What are tasks of the Service Master? 2. What is defined is this stage? 3. What is designed in this stage? DevOps 01 Introduction DevOps Process M.M. Heegstra
  132. 132. DevOps Process | Project Planning Questions & Answers 1. What are tasks of the Service Master? • Organize the service management office • Defines ground rules for the team • Creates the vision, goal and value of the project • Puts together the DevOps team members 2. What is defined is this stage? • The run-time infrastructure 3. What is designed in this stage? • A value stream map of the whole process DevOps 01 Introduction DevOps Process M.M. Heegstra
  133. 133. DevOps Process | Requirements and Design The service master defines product backlogs and priorities. The DevOps team use the product backlogs to define stories: • User story: role, function, business value/reason, and conditions of operation. • Test story: acceptance test cases and service acceptance criteria. • Operation story: set priorities of IT services and conditions of operation for business continuity. DevOps 01 Introduction DevOps Process M.M. Heegstra
  134. 134. DevOps Process | Requirements and Design The DevOps engineer and operations team define the transition, test and development infrastructure. The Development team also creates release and iteration plans. Create service level and operational level agreements. DevOps 01 Introduction DevOps Process M.M. Heegstra
  135. 135. DevOps Process | Requirements and Design The gatekeeper studies compliance and regulatory requirements for the IT services. The reliability engineer defines the testing methodology and test cases. DevOps 01 Introduction DevOps Process M.M. Heegstra
  136. 136. DevOps Process | Requirements and Design Questions 1. What are tasks of the Service Master? 2. Which stories are in the backlog? 3. What are tasks of the Development Team? 4. What are tasks of the Gatekeeper? 5. What are tasks of the Reliability Engineer? DevOps 01 Introduction DevOps Process M.M. Heegstra
  137. 137. DevOps Process | Requirements and Design Questions & Answers 1. What are tasks of the Service Master? • Define and priority product backlog 2. Which stories are in the backlog? • User stories • Test stories • Operation stories DevOps 01 Introduction DevOps Process M.M. Heegstra
  138. 138. DevOps Process | Requirements and Design Questions & Answers 3. What are tasks of the Development Team? • Define stories • Define transition, test and development infrastructure • Create release and iteration plans • Create service and operational level agreements 4. What are tasks of the Gatekeeper? • Studies compliance • Regulatory requirements for IT services DevOps 01 Introduction DevOps Process M.M. Heegstra
  139. 139. DevOps Process | Requirements and Design Questions & Answers 5. What are tasks of the Reliability Engineer? • Define testing methodology • Define test cases DevOps 01 Introduction DevOps Process M.M. Heegstra
  140. 140. DevOps Process | Development Scrum is the most applicable methodology at this stage. The development team must commit to release plans and then work using disciplined agile approach. The period of each iteration (sprint) is agreed according to business need. DevOps 01 Introduction DevOps Process M.M. Heegstra
  141. 141. DevOps Process | Development From a quality point of view, XP (Extreme Programming) practices such as pair- programming, TDD, Refactoring, and 10 minutes build are effective. DevOps 01 Introduction DevOps Process M.M. Heegstra
  142. 142. DevOps Process | Development Questions 1. Which methodology is most applicable is this stage? 2. What does the development team commit? 3. According to what is the period of each iteration agreed? 4. What are XP (Extreme Programming) practices? DevOps 01 Introduction DevOps Process M.M. Heegstra
  143. 143. DevOps Process | Development Questions & Answers 1. Which methodology is most applicable is this stage? • Scrum 2. What does the development team commit? • Release 3. According to what is the period of each iteration agreed? • Business need DevOps 01 Introduction DevOps Process M.M. Heegstra
  144. 144. DevOps Process | Development Questions & Answers 4. What are XP (Extreme Programming) practices? • Pair programming • TDD (Test Driven Development) • Refactoring • 10 minutes build DevOps 01 Introduction DevOps Process M.M. Heegstra
  145. 145. DevOps Process | Deployment After completing continuous integration, the automated process starts for the acceptance test, performance test and deployment. The reliability engineer and DevOps engineer collaborate to improve the testing process. DevOps 01 Introduction DevOps Process M.M. Heegstra
  146. 146. DevOps Process | Deployment The DevOps engineer should build the single automated deployment pipeline as a One-piece flow. DevOps 01 Introduction DevOps Process M.M. Heegstra
  147. 147. DevOps Process | Deployment The gatekeeper monitors progress across the process and makes the go/no go decision about going live. The operations team studies how to maintain business continuity. DevOps 01 Introduction DevOps Process M.M. Heegstra
  148. 148. DevOps Process | Deployment Questions 1. What are tasks of the Reliability Engineer? 2. What are tasks of the DevOps Engineer? 3. What are tasks of the Gatekeeper? 4. What are tasks of the Operations Team? DevOps 01 Introduction DevOps Process M.M. Heegstra
  149. 149. DevOps Process | Deployment Questions & Answers 1. What are tasks of the Reliability Engineer? • Improve testing process 2. What are tasks of the DevOps Engineer? • Improve testing process • Build the single automated deployment pipeline as a One-piece flow DevOps 01 Introduction DevOps Process M.M. Heegstra
  150. 150. DevOps Process | Deployment Questions & Answers 3. What are tasks of the Gatekeeper? • Monitor progress across the process • Make go/no go decision about going live 4. What are tasks of the Operations Team? • Study how to maintain business continuity DevOps 01 Introduction DevOps Process M.M. Heegstra
  151. 151. DevOps Process | Operation The operations team is responsible for monitoring the status of IT services during operation using light weight ITSM process. Keeping vital services operational in the event of a disaster is critical. The team should involve the reliability engineer and pay attention to two key parameters, Recovery point objective and Recovery time objective. DevOps 01 Introduction DevOps Process M.M. Heegstra
  152. 152. DevOps Process | Operation Questions 1. What are responsibilities of the Operations Team responsible for? DevOps 01 Introduction DevOps Process M.M. Heegstra
  153. 153. DevOps Process | Operation Questions & Answers 1. What are responsibilities of the Operations Team responsible for? • Monitoring status of IT services during operation • Keeping vital services operational • Involve the Reliability Engineer • Pay attention to Recovery point objective and Recovery time objective DevOps 01 Introduction DevOps Process M.M. Heegstra
  154. 154. DevOps Process | Maintenance The service master and reliability engineer decide whether to approve maintenance activities. If approved, they are added to the product backlog as requests for change. DevOps 01 Introduction DevOps Process M.M. Heegstra
  155. 155. DevOps Process | Maintenance Questions 1. Who decide whether to approve maintenance activities? 2. Where are they added when approved? DevOps 01 Introduction DevOps Process M.M. Heegstra
  156. 156. DevOps Process | Maintenance Questions & Answers 1. Who decide whether to approve maintenance activities? • Service Master and Reliability Engineer 2. Where are they added when approved? • Product backlog as requests for change DevOps 01 Introduction DevOps Process M.M. Heegstra
  157. 157. DevOps Process | Customer service The service master and reliability engineer are responsible for collecting customer’s feedback such as, operational problems including user experience and quality issues. If approved, these items are added to the product backlog as request for change. DevOps 01 Introduction DevOps Process M.M. Heegstra
  158. 158. DevOps Process | Customer service Questions 1. For what are the Service Master and Reliability Engineer responsible? DevOps 01 Introduction DevOps Process M.M. Heegstra
  159. 159. DevOps Process | Customer service Questions & Answers 1. For what are the Service Master and Reliability Engineer responsible? • Collecting customer’s feedback • Operational problems • User experience • Quality issues DevOps 01 Introduction DevOps Process M.M. Heegstra
  160. 160. DevOps Process | End of life The service master decides the end of life of the IT service including conditions for when and how this will happen. DevOps 01 Introduction DevOps Process M.M. Heegstra
  161. 161. DevOps Process | End of life Questions 1. What will the service master decide? DevOps 01 Introduction DevOps Process M.M. Heegstra
  162. 162. DevOps Process | End of life Questions & Answers 1. What will the service master decide? • The end of life of the IT service • Conditions for when and how end of life will happen DevOps 01 Introduction DevOps Process M.M. Heegstra
  163. 163. Light-weight ITSM example DevOps 01 Introduction DevOps Process M.M. Heegstra
  164. 164. Light-weight ITSM example Questions 1. What means ITSM? DevOps 01 Introduction DevOps Process M.M. Heegstra
  165. 165. Light-weight ITSM example Questions & Answers 1. What means ITSM? • IT Service Management DevOps 01 Introduction DevOps Process M.M. Heegstra
  166. 166. DevOps Implementation There are 3 types of DevOps implementation which are dependent on the business model of the enterprise. 1. TOYOTA way | Complex and Advanced 2. Collaboration | Standard 3. Continuous Delivery | Basic DevOps 01 Introduction DevOps Process M.M. Heegstra
  167. 167. DevOps Implementation Questions 1. Which types of DevOps implementation are there? 2. On what are they dependent? DevOps 01 Introduction DevOps Process M.M. Heegstra
  168. 168. DevOps Implementation Questions & Answers 1. Which types of DevOps implementation are there? • TOYOTA way • Collaboration • Continuous Delivery 2. On what are they dependent? • The business model of the enterprise • Complex and Advanced • Standard • Basic DevOps 01 Introduction DevOps Process M.M. Heegstra
  169. 169. DevOps Implementation | TOYOTA way This focuses on strategic IT services and gives strategic advantage for the business. It is led by business owner or service master. It is preferable to implement a matrix organization in a large enterprise and to maintain a close relationship between IT strategy and business strategy. This structure is most suited to IT service providers. DevOps 01 Introduction DevOps Process M.M. Heegstra
  170. 170. DevOps Implementation | TOYOTA way Questions 1. What are elements of the TOYOTA implementation? DevOps 01 Introduction DevOps Process M.M. Heegstra
  171. 171. DevOps Implementation | TOYOTA way Questions & Answers 1. What are elements of the TOYOTA implementation? • Focus on strategic IT services • Strategic advantage for the business • Led by business owner or service master • Implement a matrix organization in a large enterprise • Maintain a close relationship between IT strategy and business strategy • Most suited to IT service providers DevOps 01 Introduction DevOps Process M.M. Heegstra
  172. 172. DevOps Implementation | Collaboration This focuses on just providing quick and frequent IT services and reliable operation and is led by the service master. It is most suited for SoE and SoR. DevOps 01 Introduction DevOps Process M.M. Heegstra
  173. 173. DevOps Implementation | Collaboration Questions 1. What are elements of the collaboration implementation? DevOps 01 Introduction DevOps Process M.M. Heegstra
  174. 174. DevOps Implementation | Collaboration Questions & Answers 1. What are elements of the collaboration implementation? • Focus on just providing quick and frequent IT services • Focus on reliable operation • Led by the service master • Most suited for SoE and SoR DevOps 01 Introduction DevOps Process M.M. Heegstra
  175. 175. DevOps Implementation | Continuous Delivery This focuses on quick and frequent releases of software and is led by the product owner. It is most suited to Digital Product Vendors DevOps 01 Introduction DevOps Process M.M. Heegstra
  176. 176. DevOps Implementation | Continuous Delivery Questions 1. What are elements of the Continuous Delivery implementation? DevOps 01 Introduction DevOps Process M.M. Heegstra
  177. 177. DevOps Implementation | Continuous Delivery Questions & Answers 1. What are elements of the Continuous Delivery implementation? • Focus on quick and frequent releases of software • Led by product owner • Most suited to Digital Product Vendors DevOps 01 Introduction DevOps Process M.M. Heegstra

×