Delivery Glossary

Browse 34 delivery terms defined in plain English, from the cultural dictionary of computing.

34 Delivery Terms

Build Culture
The shared norms and habits around how a team builds software, including attitudes toward quality, speed, testing, release discipline, and ownership. Build...
Code Complete
A milestone indicating that planned coding work for a release or feature is considered finished, even if testing, documentation, and polish may still remain....
Code Deployment
The act of releasing code into a live or testing environment where it becomes active. In team culture, code deployment is as much about process confidence and...
Code Marathon
A long sustained stretch of coding, debugging, or shipping effort that requires endurance more than quick cleverness. In engineering slang, code marathons can...
Code Ship
An informal phrase meaning to ship or release code into a real environment. It reflects the everyday delivery mindset of teams that think in terms of moving...
Code Submission
The act of submitting code for review, assessment, integration, or publication. In practice, code submission processes shape team velocity, review quality, and...
Content Delivery
The process of distributing application assets, media, documents, or pages efficiently to users across different locations and devices. Content delivery often...
Continuous Delivery
A Continuous Delivery is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Continuous Deployment
Continuous Deployment (CD) is a practice where every code change that passes automated testing is automatically released to production without manual approval....
Continuous Integration
Continuous Integration (CI) is a development practice where developers merge their code changes into a shared repository frequently, ideally multiple times per...
CPU Pipeline
A CPU Pipeline is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
Critical Path Slang
Informal talk around whatever work directly controls whether a project or release can complete on time. In engineering slang, 'critical path' is often used...
Deadline
A fixed point in time by which work is expected to be completed. In tech culture deadlines can create focus and coordination, but they also become destructive...
Deadline Driven Development
A mode of software work where a fixed date dominates tradeoffs, often pushing scope cuts or quality compromises.
Deployment Slot
A Deployment Slot is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Deployment Strategy
A Deployment Strategy is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Deploy Pipeline
A Deploy Pipeline is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Execution
The ability to turn plans, ideas, and priorities into actual results through disciplined follow-through. In tech culture, execution is often admired more than...
Good Enough
Adequate for the actual need even if not perfect by every possible standard. In engineering culture, recognizing when something is good enough is a mark of...
Integration
An Integration is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
Just Ship It
A push to stop debating and release the thing, often because further polishing is seen as lower value than getting real feedback. It can reflect healthy...
Landed
Merged, deployed, or otherwise successfully applied in the target environment. Engineers use it for code changes, features, fixes, and sometimes policy...
Last Mile
The final part of getting a system or feature into real use, where the remaining issues are often small individually but still decisive collectively. In...
Lead Time
The time it takes for work to move from request or code change to production or user delivery, often used as an engineering effectiveness metric.
Payload
The component of malware or an exploit that performs the actual malicious action — data exfiltration, encryption, backdoor installation — as opposed to the...
Product Velocity
The speed at which a product team can ship meaningful improvements without collapsing quality or strategic coherence. Product velocity matters only if it is...
Scope Creep Culture
A work environment where requirements and expectations constantly expand without corresponding changes to time, staffing, or priorities. It describes an...
Service Model
The overall way a company delivers and supports its offering, including what is automated, what is human-driven, and how responsibility is divided. Service...
Shipping
The act of actually releasing a feature, product, or update to users rather than only planning or prototyping it. In product and engineering culture,...
Shipping Cadence
The rhythm or frequency with which a team releases changes, features, or updates.
Terror-Driven Development
A joking phrase for shipping work mainly under fear, panic, or deadline pressure rather than calm planning.
Trunk-Based Development Culture
A team norm built around integrating changes into the main branch frequently and avoiding long-lived feature branches.
Unplanned Work
Interrupt-driven tasks such as outages, support escalations, and urgent fixes that were not on the original plan.
Zipline
A fast direct path that gets something from point A to point B with minimal delay or ceremony. In engineering slang, a zipline is the route people wish every...

Related Topics