DevOps, Managing Development + Operations & Release in Large Scale

Editor's Notes

• #7: After discussing the brief history of this approach, let us talk about the fundamentals of DevOps. DevOps relies mainly on the 1) alignment of goals, 2) collaboration, and 3) automation. In order to achieve these goals, DevOps employs various methods, practices and tools. Now, we are going to really quickly go through some of the mains points of DevOps, and we’ll also mention the relevant codeBeamer features and functions that help you implement this approach. Let me remind you that we will show how all this works in practice via a live demonstration right after this presentation. So there’s no need to go into the details. For now, we’re just going to go through these points real fast to help you better understand how DevOps works. For planning, tracking and monitoring processes, DevOps is supported by release planner tools. These are used to plan sprints and releases, assign tasks to each of these, and monitor the progress made against these plans. As you’ll see, codeBeamer’s release planner is an advanced tool that helps you plan and monitor as many releases as you need – Sándor will talk about release management in detail a little bit later. Our next topic is also an important one: collaboration. This necessitates communication between your team members, assigning tasks to members of your team, and the complete transparency of all processes so that all team members always know how the project is progressing. In codeBeamer, you have real-time collaboration, supported by comments, Wikis and Documents as well as team member activity feeds, e-mail notifications, and complete task management functionality. Next up, it’s automation and integration. Among the many tools and solutions usually mentioned in relation to DevOps, some of the most popular are Chef, Maven, JUnit, Ansible, Puppet and of course Jenkins. codeBeamer offers REST API to allow integration with other tools including Jenkins. codeBeamer’s own QA & Testing functionality includes test cases and test sets, which are all reusable through a library. This means you can simply save all your test-related information in a library (both test cases and test sets), you can browse this library any time, and just simply reuse the test cases you need in further projects. codeBeamer also offers manual test management and staging functionality. Also related to release management that we’ll talk about later, we have baselining. codeBeamer offers advanced baselining functionality which allows you to take a snapshot of the current state of all your artifacts, all your work items. These baselines contain all the relevant information as well as complete change history on all artifacts, and may be browsed any time later. What’s more, e-signatures may be added to them, helping you comply with industry regulations. Issue management is another important process of the Operations aspect of DevOps. codeBeamer comes with fully customizable Kanban boards that allow you to manage issues and escalations – Sándor will be talking about this in detail.
• #9: After discussing the brief history of this approach, let us talk about the fundamentals of DevOps. DevOps relies mainly on the 1) alignment of goals, 2) collaboration, and 3) automation. In order to achieve these goals, DevOps employs various methods, practices and tools. Now, we are going to really quickly go through some of the mains points of DevOps, and we’ll also mention the relevant codeBeamer features and functions that help you implement this approach. Let me remind you that we will show how all this works in practice via a live demonstration right after this presentation. So there’s no need to go into the details. For now, we’re just going to go through these points real fast to help you better understand how DevOps works. For planning, tracking and monitoring processes, DevOps is supported by release planner tools. These are used to plan sprints and releases, assign tasks to each of these, and monitor the progress made against these plans. As you’ll see, codeBeamer’s release planner is an advanced tool that helps you plan and monitor as many releases as you need – Sándor will talk about release management in detail a little bit later. Our next topic is also an important one: collaboration. This necessitates communication between your team members, assigning tasks to members of your team, and the complete transparency of all processes so that all team members always know how the project is progressing. In codeBeamer, you have real-time collaboration, supported by comments, Wikis and Documents as well as team member activity feeds, e-mail notifications, and complete task management functionality. Next up, it’s automation and integration. Among the many tools and solutions usually mentioned in relation to DevOps, some of the most popular are Chef, Maven, JUnit, Ansible, Puppet and of course Jenkins. codeBeamer offers REST API to allow integration with other tools including Jenkins. codeBeamer’s own QA & Testing functionality includes test cases and test sets, which are all reusable through a library. This means you can simply save all your test-related information in a library (both test cases and test sets), you can browse this library any time, and just simply reuse the test cases you need in further projects. codeBeamer also offers manual test management and staging functionality. Also related to release management that we’ll talk about later, we have baselining. codeBeamer offers advanced baselining functionality which allows you to take a snapshot of the current state of all your artifacts, all your work items. These baselines contain all the relevant information as well as complete change history on all artifacts, and may be browsed any time later. What’s more, e-signatures may be added to them, helping you comply with industry regulations. Issue management is another important process of the Operations aspect of DevOps. codeBeamer comes with fully customizable Kanban boards that allow you to manage issues and escalations – Sándor will be talking about this in detail.
• #12: Fokus on one example (e.g blue string which represents the epic for Electric City Car Prototype) In the portfolio level, the most valuable and winner epics are collected which shall be implemented by the teams. One epic can be interconnected with a release train in the program Level