DOCSLIB.ORG

Devops Terms

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Devops Terms Important DevOps Terms Agile Software Development DevOps Group of software development methods in A cultural and professional movement that which requirements and solutions evolve stresses communication, collaboration and through collaboration between self-organizing, integration between software developers and cross-functional teams. IT operations professionals while automating the process of software delivery and infra- Velocity structure changes Measure of the quantity of work done in a pre- defined interval. CALMS DevOps Values Scrum Culture A simple framework for effective team collabo- Automation ration on complex projects. Scrum provides a Lean small set of rules that create “just enough” Measurement structure for teams to be able to focus their in- Sharing novation on solving what might otherwise be an insurmountable challenge. Organizational Culture DevOps The values and behaviors that contribute to the Product Backlog unique social and psychological environment of Prioritized list of requirements INSTITUTE an organization. Lean (production) Change Fatigue Philosophy that focuses on reducing waste General sense of apathy or passive resignation (muda) and improving the flow of processes to towards organizational changes by ndivii duals improve overall customer value or teams Lean IT High-trust Culture Appling the key ideas behind lean production to Organization that encourages good information the development and management of IT prod- flow, cross-functional collaboration, shared re- ucts and services ® sponsibilities, learning from failures and new DevOps Foundation Flow ideas REFERENCE CARD How people or products move through a pro- Collaboration cess People jointly working together towards a com- IT Service Management mon goal Implementation and management of quality IT Constraint (bottleneck) services that meet the needs of the business Step in a process that limits total capacity DevOps Institute. DevOps Foundation®, Certified Agile Service Manager (CASM)®, Certified Agile Process Owner (CAPO)® & Agile Service Management® are registered marks of DevOps Institute. ITIL® is a registered trade mark of AXELOS Limited © DevOps Institute 30Sept2020 The First Way – Understand and increase the The Second Way – Shorten and amplify feed- The Third Way – Continual experimentation flow of work (left to right) back loops (right to left) and learning Practices include: Practices include: Practices include: Continuous Integration Automated testing Experimentation and learning Development practice that requires developers Peer review of production changes Using feedback to answer the question to integrate code into a shared repository on a Monitoring “Should this product be built?” daily basis ‘At a glance’ dashboards Plan, Do, Check, Act (PDCA) Continuous Delivery Production logs Also known as the Deming Cycle Methodology that focuses on making sure Process measurements Methodology that enables incremental im- software is always in a releasable state through- Post-mortems provement out its lifecycle Shared on-call rotation Improvement Kata Continuous Deployment Change, Incident, Problem and Structured way to create a culture of continu- Practices where every change that passes auto- Knowledge Management data ous learning and improvement mated tests is automatically eplod yed 1. Understand the long-term vision Value Stream Mapping or direction Lean tool that depicts the flow of information, Understand and respond to the needs of all 2. Grasp the current condition materials and work across functional silos with customers – both internal and external. an emphasis on quantifying waste. 3. Establish the next target condition Create and embed knowledge where needed. Kanban 4. PDCA/experiment toward the Method of work that pulls the flow of work target condition through a process at a manageable pace ChatOps An approach to managing technical and busi- ness operations through a group chat room DevSecOps A mindset that "everyone is responsible for security" with the goal of safely distributing security decisions at speed and scale Theory of Constraints Methodology for identifying and then improving a limiting constraint Visit us at www.devopsinstitute.com Source: The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win Follow us on Twitter: @DEVOPSINST.
Load more

Recommended publications
  • Extension of the Lean 5S Methodology to 6S with an Additional Layer to Ensure Occupational Safety and Health Levels
    sustainability Article Extension of the Lean 5S Methodology to 6S with An Additional Layer to Ensure Occupational Safety and Health Levels Mariano Jiménez 1,2 , Luis Romero 2,* , Jon Fernández 2, María del Mar Espinosa 2 and Manuel Domínguez 2 1 Department of Mechanical Engineering, Technical School of Engineering—ICAI, Comillas Pontifical University, 25, 28015 Madrid, Spain 2 Design Engineering Area, Industrial Engineering School, National Distance Education University (UNED), 38, 28015 Madrid, Spain * Correspondence: [email protected] Received: 12 June 2019; Accepted: 11 July 2019; Published: 12 July 2019 Abstract: This paper proposes an expansion of the Lean 5S methodology, which includes the concept of Safety–Security as 6S. Implementation was done by a standardized process tested in a pilot area that is part of the Integrated Industrial Manufacturing System Laboratory at the Higher Technical School of Engineering (ICAI). The additional 6S phase (Safety-Security) thoroughly reviews all areas of an industrial plant by analyzing the risks at each workstation, which let employees be fitted out with protection resources depending on each of their personal characteristics and to guarantee the safety of the workstation by strictly complying with occupational safety and health and machinery use standards, which must hold a CE certificate of compliance. The main objective was to increase the scope of 5S methodology to respond to the occupational safety and health needs for machines required in optimizing production processes. It is important to remember that companies must guarantee that their employees use personal protection equipment (PPE) at their work posts or stations that protect them properly from risks to their health and safety and that cannot be prevented or sufficiently limited by using collective means of protection or by adopting work organization measures.
    [Show full text]
  • White Paper the PDCA Cycle and Management System Standards
    The PDCA cycle and Management System Standards ISO uses a very simple but powerful tool for quality system standards. This tool is the Plan- Do-Check-Act (PDCA) cycle shown in the figure below. It is also known as the Deming cycle after J.W. Deming, who proposed the concept in the 50s. The entire logic, structure, and sequence of standards like ISO 9001 and ISO 13485 are based on this cycle. Every process or activity needs to pass through these four phases. Plan Phase Perhaps, planning tasks are the most important ones in a management system. ISO recognizes this fact, as well as the fact that the plan phase should be the very first thing we do. To better understand this phase, activities like “establish” and “determine” should be associated to planning. Other words we can use instead are “identify” or “define”. Let´s see what an organization needs to plan. ACT PLAN First, the organization needs to establish its high- level planning. This will set direction and provide a framework for the entire system. We are talking about the organization´s purpose. And also, in CHECK DO terms of quality, about: policy, system´s scope, and objectives. The output of the high-level planning process will provide the necessary guide to the next step. The PDCA Cycle Next the organization needs to identify the processes that will be part of the quality system. It also needs to define how to apply or operate these processes, their sequence and how they interact. Also, the organization must identify risks related to the processes and how to control them according to those risks.
    [Show full text]
  • The Concept and Implementation of Kaizen in an Organization
    Global Journal of Management and Business Research: A Administration and Management Volume 19 Issue 1 Version 1.0 Year 201 Type: Double Blind Peer Reviewed International Research Journal Publisher: Global Journals Online ISSN: 2249-4588 & Print ISSN: 0975-5853 The Concept and Implementation of Kaizen in an Organization By Lubna Rahman Lina & Hafiz Ullah University of Dhaka Abstract- For continuous improvement in an organization, Japanese philosophy Kaizen is very popular. Flawless concepts of kaizen methodology and proper implementation of tools can lead to a successful kaizen program in a company. From the reviews of various case studies, it has revealed that most of the companies have implemented kaizen efficiently and observe better performance. Besides, some companies also failed to implement kaizen due to the lacking of proper knowledge about the concepts of kaizen. Keywords: kaizen, 5 why technique, 5s, 7 QC tools, 7 wastes, jidoka, PDCA cycle, poka-yoke. GJMBR-A Classification: JEL Code: M00 TheConceptandImplementationofKaizeninanOrganization Strictly as per the compliance and regulations of: © 2019. Lubna Rahman Lina & Hafiz Ullah. This is a research/review paper, distributed under the terms of the Creative Commons Attribution-Noncommercial 3.0 Unported License http://creativecommons.org/licenses/by-nc/3.0/), permitting all non-commercial use, distribution, and reproduction in any medium, provided the original work is properly cited. The Concept and Implementation of Kaizen in an Organization α σ Lubna Rahman Lina & Hafiz Ullah Abstract - For continuous improvement in an organization, over the longer term, without having to go through any Japanese philosophy Kaizen is very popular. Flawless radical innovation. It can be a much gentler and concepts of kaizen methodology and proper implementation employee-friendly way to institute the changes that must of tools can lead to a successful kaizen program in a occur as a business grows and adapts to its changing company.
    [Show full text]
  • Agile and Devops Overview for Business
    NELKINDA SOFTWARE CRAFT Ƅ TRAINING Agile and DevOps Overview for Business Duration: 2 Days Available Languages: English Audience Everyone who is steering or involved in software delivery: Business, Management, Operations, Development, for example: CxOs, managers, directors, team leads, systems administrators, development managers, business analysts, requirements engineers, architects, product owners, scrum masters, IT operations sta', IT stakeholders, developers, testers Goals Agile and DevOps are the big drivers of organizational transformation today. What do they mean? Where do they come from? What are their goals? How can they help my organization and my team? How can I use and implement them? And are there any side-e'ects or challenges to consider? Learn the answers to these questions in a holistic perspective from the CxO level to the code about what Agile and DevOps mean for organizations of all sizes. Contents • Business Case for Improving the Software Development Life Cycle ◦ Evolution of the Software Development Life Cycle (SDLC) ◦ Business Drivers of the SDLC Evolution ◦ Principles of Agile, DevOps, Extreme Programming (XP), and Software Craft ◦ Goals and Objectives of Agile, DevOps (Development Operations), XP, and Software Craft ◦ The Pipeline for Value Delivery • Essential Principles ◦ Manifesto for Agile Software Development ("Agile Manifesto") ◦ The Values and Principles of XP ◦ Manifesto of Software Craft ◦ The Two Values of Software ◦ The Deming (PDCA, plan-do-check-act) Cycle ◦ The XP Feedback Loops ◦ Parkinson's Law and Timeboxing ◦ Conway's Law, Organizational Structure and Cross-functional responsibility ◦ KPIs (Key Performance Indicators) and Drivers: Story-Point Velocity, Cycle Time, WIP (Work In Progress) limit ◦ Heisenberg's Uncertainty Principle of Agile Estimation 1/3 https://nelkinda.com/training/DevOps-Driven-Agile © Copyright 2015-2020 Nelkinda Software Craft Private Limited.
    [Show full text]
  • Implementation of Lean Tools in Apparel Industry to Improve Productivity and Quality
    Current Trends in Fashion Technology & Textile Engineering ISSN: 2577-2929 Review Article Curr Trends Fashion Technol Textile Eng Volume 4 - Issue 1 - July 2018 Copyright © All rights are reserved by Prakash C DOI: 10.19080/CTFTTE.2018.04.555628 Implementation of Lean Tools in Apparel Industry to Improve Productivity and Quality Mothilal B and Prakash C* Department of Fashion Technology, Sona College of Technology, India Submission: April 19, 2018; Published: July 02, 2018 *Corresponding author: Prakash C, Department of Fashion Technology, Sona College of Technology, India, Tel No: ; Fax: +91-427- 4099888; Email: Abstract The rapid change in apparel styles, deviation of order quantities and increasing quality levels at the lowest possible cut-rate, demand the market. To increase the productivity of the apparel industries we need to reduce the wastage of the manufacturing and time to manufacture the product.apparel manufacturing Lean is the tool industry to reduce to the be focusedwastage on in moreall process effective of apparel and efficient manufacturing, manufacturing reducing processes cost and for value survival added in anto theimmensely product. competitive This paper proposes the lean tool for the apparel industry to reduce the overall wastage of the industries. Keywords: Abbreviations:Apparel FMEA: industry; Failure Eco-efficiency; Mode and Effect Industrial Analysis; wastes; SFPS: Single Lean Failuretools Points; TPM: Total Productive Maintenance; OEE: Overall Equipment Effectiveness; PDCA: Plan-Do-Check-Act or Plan-Do-Check-Adjust; PDSA: Plan-Do-Study-Act Introduction Tapping D [1] observed that lean strategy is to eliminate wastes Lean tools from the process. Any excess in equipment’s, materials, parts, and working period beyond the requirement is generally referred as of waste (muda), the improvement of quality, and production waste.
    [Show full text]
  • Bringing Lean to Life: Making Processes Flow in Healthcare
    NH S Improving Quality BRINGING LEAN TO LIFE Making processes flow in healthcare IMPROVEMENT. PEOPLE. QUALITY. STAFF. DATA. SATcEknPoSw.leLdgEeAmNen. tsPATIENTS. PRODUCTIVITY. IDEAS. This document has been written in partnership by: RZEoë LDord ESIGN. MAPPING. SOLUTIONS. EXPERIENCE. Email: [email protected] Lisa Smith SEmHail:A [email protected] OCESSES. TOOLS. MEASURES. INVOLVEMENT. STRENGTH. SUPPORT. LEARN. CHANGE. TEST. IMPLEMENT. PREPARATION. KNOW-HOW. SCOPE. INNOVATION. FOCUS. ENGAGEMENT. DELIVERY. DIAGNOSIS. LAUNCH. RESOURCES. EVALUATION. NHS. PLANNING. TECHNIQUES. FRAMEWORK. AGREEMENT. UNDERSTAND. IMPLEMENTATION. SUSTAIN. Bringing Lean to Life - Making processes flow in healthcare Contents Introduction - what is the problem in healthcare? 4 Identifying waste 18 What is Lean? 6 Making value flow 21 A3 thinking 7 Understanding pull 22 An example A3 report 8 Understanding Takt time 23 The importance of data and measures 10 Using 5S to improve safety 24 Example statistical process control (SPC) charts 11 Plan, Do, Check, Adjust (PDCA) cycle 25 Current state value stream mapping 12 Continuous improvement 26 Analysing your current state and designing your 14 Value stream mapping symbols 27 future state value stream map Standard work to produce high quality every time 15 Visual management 16 3 4 Bringing Lean to Life - Making processes flow in healthcare Introduction - what is the problem in healthcare? We all come to work to do our very best - to The processes are to blame, not the people This booklet provides a basic introduction and achieve what we are capable of and to add real overview of Lean; the culture, principles and value for our patients and ensure clinical Often, there is ambiguity in how certain tasks tools to understand to enable you to tackle and expertise is supported by process excellence to should be performed – so people work it out for resolve issues within healthcare.
    [Show full text]
  • Review Paper on “Poka Yoke: the Revolutionary Idea in Total Productive Management” 1,Mr
    Research Inventy: International Journal Of Engineering And Science Issn: 2278-4721, Vol. 2, Issue 4 (February 2013), Pp 19-24 Www.Researchinventy.Com Review Paper On “Poka Yoke: The Revolutionary Idea In Total Productive Management” 1,Mr. Parikshit S. Patil, 2,Mr. Sangappa P. Parit, 3,Mr. Y.N. Burali 1,Final Year U.G. Students, Mechanical Engg. Department,Rajarambapu Institute of Technology Islampur (Sangli),Shivaji University, Kolhapur (India) 2,P.G. Student, Electronics Engg. Department, Rajarambapu Institute of Technology Islampur (Sangli), Shivaji University, Kolhapur (India) Abstract: Poka-yoke is a concept in total quality management which is related to restricting errors at source itself. It deals with "fail-safing" or "mistake-proofing". A poka-yoke is any idea generation or mechanism development in a total productive management process that helps operator to avoid (yokeru) mistakes (poka). The concept was generated, and developed by Shigeo Shingo for the Toyota Production System. Keywords— Mistake-proofing, Total quality management, Total productive management. I INTRODUCTION In today’s competitive world any organisation has to manufacture high quality, defect free products at optimum cost. The new culture of total quality management, total productive management in the manufacturing as well as service sector gave birth to new ways to improve quality of products. By using various tools of TQM like KAIZEN, 6 sigma, JIT, JIDCO, POKA YOKE, FMS etc. organisation is intended to develop quality culture.[2,6] The paper is intended to focus basic concept of poka yoke, types of poka yoke system, ways to achieve simple poka yoke mechanism. It also covers practical study work done by various researchers .
    [Show full text]
  • Lean Methodology and Its Derivates Usage for Production Systems in Modern Industry
    Applied Engineering Letters Vol.2, No.4, 144-148 (2017) e-ISSN: 2466-4847 LEAN METHODOLOGY AND ITS DERIVATES USAGE FOR PRODUCTION SYSTEMS IN MODERN INDUSTRY Marko Miletić1, Ivan Miletić1 1Faculty of Engineering, University of Kragujevac, Serbia Abstract: ARTICLE HISTORY With lean methodology usage being the only way to stay competitive on Received 15.11.2017. nowadays market, it is important to implement it and spread it through the Accepted 07.12.2017. organization. Available 15.12.2017. In this paper, purpose of lean is explained, the most important definition and tools are given and differences between problem solving approaches are explained. KEYWORDS It can be concluded that problem solving approaches are in first look Lean Manufacturing, World Class Manufacturing, Toyota different, having also different number of steps, but they are adapted to the Production System, Basic Tools, company in which they are used and that they depend on the size, Continuous Improvement complexity and expected closing time of project. 1. INTRODUCTION which is initiated by management and bottom-up initiated by people on shop floor. The concept of lean methodology is nowadays Therefore, TPS is used in many industries and widely used in companies around the world in companies, adapted to its products and needs and order to maximise production by minimising loses now defined as common used methodologies such at the same time. Roots of integration of entire as: Lean [1], Lean Six Sigma [2], World Class production system done in flow was made by Manufacturing, Toyota Production System [3], Ford Henry Ford in 1913. However, true usage of lean Production System, Bosch Production System, etc… concept was started by Toyota owner Kiischiro Purpose of this paper is to show tools widely Toyoda and engineer Kaiichi Ohno after WWII, and used in these methodologies and present their finally summarized in 1980s rebranding their TPS main foundations.
    [Show full text]
  • Master Glossary
    Master Glossary Term Definition Course Appearances 12-Factor App Design A methodology for building modern, scalable, maintainable software-as-a-service Continuous Delivery applications. Architecture 2-Factor or 2-Step Two-Factor Authentication, also known as 2FA or TFA or Two-Step Authentication is DevSecOps Engineering Authentication when a user provides two authentication factors; usually firstly a password and then a second layer of verification such as a code texted to their device, shared secret, physical token or biometrics. A/B Testing Deploy different versions of an EUT to different customers and let the customer Continuous Delivery feedback determine which is best. Architecture A3 Problem Solving A structured problem-solving approach that uses a lean tool called the A3 DevOps Foundation Problem-Solving Report. The term "A3" represents the paper size historically used for the report (a size roughly equivalent to 11" x 17"). Acceptance of a The "A" in the Magic Equation that represents acceptance by stakeholders. DevOps Leader Solution Access Management Granting an authenticated identity access to an authorized resource (e.g., data, DevSecOps Engineering service, environment) based on defined criteria (e.g., a mapped role), while preventing an unauthorized identity access to a resource. Access Provisioning Access provisioning is the process of coordinating the creation of user accounts, e-mail DevSecOps Engineering authorizations in the form of rules and roles, and other tasks such as provisioning of physical resources associated with enabling new users to systems or environments. Administration Testing The purpose of the test is to determine if an End User Test (EUT) is able to process Continuous Delivery administration tasks as expected.
    [Show full text]
  • Operations Management Made Simple
    Article OPERATIONS MANAGEMENT MADE SIMPLE implementconsultinggroup.com By Jan Erik Dahl In recent years, many organisations and management and Anders Bogason, [email protected], teams have achieved significant results by working in a Implement Consulting Group structured manner with operations management – both at an operational and tactical level. However, for many of the involved lead- another way, a balanced approach where ers this means that they suddenly find we cultivate skilled, business-oriented themselves in a very different leadership leaders of people who can add life and role in which they are also confronted intelligence to the rationally sound with a vast number of new methods and operations management tools. tools. Seeing that the leaders are the ones who drive operations management, and thus have the key to success, it is of great Operations management does importance that the leaders receive the not need to be complex necessary support to successfully get As specialists, we tend to make opera- through this transformation. The support tions management more complex than is to be found in the operations manage- necessary. An example of this is uncritical ment tools which should be based on a references to a vast number of different more rational operations management toolboxes and tools which all can help theory as well as the actual leadership the organisation’s leaders in relation skills which should be based on a to specific operations management humanistic perspective. Or put in challenges, e.g. implementconsultinggroup.com 1 Operations management made simple • The supply chain management toolbox, to make corrective actions before it is too which contains a number of planning late as well as gather learning based on tools such as Enterprise Resource the deviations from what was expected.
    [Show full text]
  • Glossary of Lean Terminology
    Glossary of Lean Terminology Lean Term Definition Use 6S: Used for improving organization of the Create a safe and workplace, the name comes from the six organized work area steps required to implement and the words (each starting with S) used to describe each step: sort, set in order, scrub, safety, standardize, and sustain. A3 thinking: Forces consensus building; unifies culture TPOC, VSA, RIE, around a simple, systematic problem solving methodology; also becomes a communication tool that follows a logical narrative and builds over years as organization learning; A3 = metric nomenclature for a paper size equal to 11”x17” Affinity A process to organize disparate language Problem solving, Diagram: info by placing it on cards and grouping brainstorming the cards that go together in a creative way. “header” cards are then used to summarize each group of cards Andon: A device that calls attention to defects, Visual management tool equipment abnormalities, other problems, or reports the status and needs of a system typically by means of lights – red light for failure mode, amber light to show marginal performance, and a green light for normal operation mode. Annual In Policy Deployment, those current year Strategic focus Objectives: objectives that will allow you to reach your 3-5 year breakthrough objectives Autonomation: Described as "intelligent automation" or On-demand, defect free "automation with a human touch.” If an abnormal situation arises the machine stops and the worker will stop the production line. Prevents the production of defective products, eliminates overproduction and focuses attention on understanding the problem and ensuring that it never recurs.
    [Show full text]
  • Continuous Improvement Toolkit PDCA (Plan – Do – Check
    Continuous Improvement Toolkit PDCA (Plan – Do – Check - Act) P D A C Continuous Improvement Toolkit . www.citoolkit.com The Continuous Improvement Map Managing Deciding & Selecting Planning & Project Management* Risk PDPC Decision Balance Sheet Importance-Urgency Mapping Daily Planning PERT/CPM FMEA RAID Log* Force Field Analysis Cost Benefit Analysis MOST RACI Matrix Activity Networks Risk Assessment* Break-even Analysis Voting TPN Analysis SWOT Analysis Stakeholder Analysis Decision Tree Pick Chart Four Field Matrix Fault Tree Analysis Project Charter Improvement Roadmaps Critical-to Tree QFD Portfolio Matrix Traffic Light Assessment PDCA Policy Deployment Gantt Charts DMAIC Kano Analysis Matrix Diagram Paired Comparison Lean Measures Kaizen Events Control Planning Cost of Quality* Pugh Matrix Prioritization Matrix Bottleneck Analysis** A3 Thinking Standard work Document control OEE KPIs Pareto Analysis C&E Matrix Process Yield Understanding Cross Training Implementing ANOVA Chi-Square Descriptive Statistics Value Analysis Solutions** Capability Indices Cause & Effect Probability Distributions Hypothesis Testing Design of Experiment Mistake Proofing Ergonomics Gap Analysis* Histograms & Boxplots Multi vari Studies Confidence Intervals Simulation TPM Automation Reliability Analysis Graphical Analysis Scatter Plots Correlation Pull Flow Just in Time Understanding Regression MSA Performance Run Charts 5 Whys Root Cause Analysis Data Snooping Visual Management 5S Benchmarking** Control Charts Fishbone Diagram Tree Diagram* SIPOC* Waste Analysis Quick Changeover Data collection planner* Sampling Morphological Analysis How-How Diagram** Process Redesign Time Value Map Value Stream Mapping Check Sheets Interviews Brainstorming SCAMPER** Attribute Analysis Spaghetti Diagram Affinity Diagram Relationship Mapping* Flow Process Charts Service Blueprints Questionnaires Focus Groups Data Mind Mapping* Lateral Thinking Flowcharting IDEF0 Process Mapping Observations Collection Suggestion systems Creating Ideas Designing & Analyzing Processes Continuous Improvement Toolkit .
    [Show full text]