Business Agility is a set of organizational capabilities, behaviors, and ways of working that affords your business the freedom, flexibility, and resilience to achieve its purpose. No matter what the future brings.
(Source: Business Agility Institute)

Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes, and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.
(Source: Book "Continuous Delivery")

Continuous Deployment means that every change goes through the pipeline and automatically gets put into production, resulting in many production deployments every day.
(Source: Martin Fowler)

Continuous Integration (CI) is a software development practice where members of a team integrate their work frequently, usually, each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.
(Source: Martin Fowler)

A deployment pipeline (CI/CD pipeline) is an automated manifestation of your process for getting software from version control into the hands of your users
(Source: Book "Continuous Delivery")

DevOps: Imagine a world where product owners, Development, QA, IT Operations, and Infosec work together, not only to help each other but also to ensure that the overall organization succeeds.
By working toward a common goal, they enable the fast flow of planned work into production (e.g., performing tens, hundreds or even thousands of code deploys per day), while achieving world-class stability, reliability, availability, and security.
(Source: Book "The DevOps Handbook")

Flow: The movement of potential value through a given process.
(Source: The Kanban Guide)

Flow: The smooth, uninterrupted movement of a product or service through a series of process steps.  In true flow, the work product (information, paperwork, material, etc.) passing through the series of steps never stops.
(Source: TKMG Lean Terminology)

Gemba: A Japanese word for the “real place” or the place where the work actually occurs.  To understand the real issues that affect a process it is critical to go to Gemba in order to see what is actually happening.
(Source: TKMG Lean Terminology)

Handoff: The act of giving control of something or responsibility for something to someone else. A handoff is when one person or group’s output is handed to the next person or group along the development chain.
(Source: Cambridge Dictionary)

Improvement Kata is a method where team leaders and members continually practice a kata routine that develops and channels their abilities to solve problems.
(Source: Book "Improvement Kata")

Kanban is a strategy for optimizing the flow of value through a process that uses a visual, pull-based system.
(Source; The Kanban Guide)

Lead Time: At a value stream level, lead time is the elapsed time from a customer request to delivering on that request.
At a process level, lead time is the elapsed time from when work is made available to on operation or work team until it’s been completed and passed on to the next operation or work team.
(Source: TKMG Course)

Lean: The core idea is to maximize customer value while minimizing waste. Simply, lean means creating more value for customers with fewer resources. A lean organization understands customer value and focuses its key processes to continuously increase it.

Outcome: an outcome is a change in human behavior that drives business results.
(Source: Book "Outcomes over Output")

Program logic model is defined as a picture of how your organization does its work – the theory and assumptions underlying the program. A program logic model links outcomes (both short- and long-term) with program activities/processes and the theoretical assumptions/principles of the program.
(Source: W.K. Kellogg Foundation Logic Model Development Guide)

Psychological safety is being able to show and employ one's self without fear of negative consequences of self-image, status or career (Kahn 1990, p. 708). It can be defined as a shared belief that the team is safe for interpersonal risk taking.

Reliability is the probability that [a system] will perform a required function without failure under stated conditions for a stated period of time.
(Source: Book "Practical Reliability Engineering")

SBOM (Software Bill of Materials): formal and machine-readable metadata that uniquely identifies a software component,
its dependencies, and license data.
(Source: The Linux Foundation Research)

SDLC: In systems engineering, information systems and software engineering, the software development life cycle (SDLC), also referred to as the application development life-cycle, is a process for planning, creating, testing, and deploying an information system.

SRE (Site Reliability Engineering) is what you get when you treat operations as if it’s a software problem.
(Source: Book "Google SRE")

A value stream is the sequence of activities an organization undertakes to deliver on a customer request.
(Source: Book "Value Stream Mapping")

Value Stream Map: A high-level, visual representation of all of the process steps required to transform a customer requirement into a delivered good or service. Value stream maps are used to document current state conditions as well as design a future state.
(Source: TKMG Lean Terminology)

Value Stream Management (VSM): a combination of people, processes, and technology that maps, optimizes, visualizes, and governs business value flow through heterogeneous enterprise software delivery pipelines.
(Source: Forrester Research)

Leave a Reply

Your email address will not be published. Required fields are marked *