Skip to main content

​
A–D

AI Agent — An automated software process deployed within the SEOP platform to perform specific engineering tasks such as QA automation, code review, analytics generation, or sprint monitoring. AI Agents operate within defined governance controls. AI Agent Gateway — Scrums.com’s orchestration layer for deploying, managing, and governing AI agents across engineering workflows. The AI Agent Gateway integrates with tools like Jira, GitHub, and Azure to automate work and surface insights. AI Agent Harness — The context, tools, authority guardrails, runtime, and evaluations that surround an AI model and make an agent operable. AI Catalog — The catalog of deployable agents, models, MCP servers, skills, APIs, and infrastructure at scrums.com/catalog. Augmentation (Staff Augmentation) — A delivery model where individual Scrums.com engineers are embedded into a client’s existing team. The client manages day-to-day work; Scrums.com handles vetting, contracting, and HR. Backlog — A prioritised list of features, bugs, and tasks to be delivered in future sprints. DORA Metrics — A set of four industry-standard engineering performance indicators: Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Mean Time to Recovery (MTTR). DDT (Dedicated Development Team) — A subscription-based model where Scrums.com assembles and manages a dedicated engineering team deployed against a client’s roadmap.

​
E–M

Enablement Partner — A Scrums.com team member responsible for onboarding clients, facilitating kickoffs, and supporting ongoing delivery success. Engagement — An active working relationship between Scrums.com and a client, encompassing a defined scope of engineering work. Managed Delivery (MAN) — A subscription-based delivery model where Scrums.com takes fractional ownership of engineering outcomes across QA, product development, or platform maintenance. MCP Gateway — A governed control plane that scopes connections, credentials, tools, policies, approvals, and audit records for Model Context Protocol clients.

​
O–S

Outcome-Driven Sprint (ODS) — A time-boxed execution model for a defined AI Development scope. Orchestration — The coordination of people, tools, workflows, and AI within a unified delivery system to produce predictable software outcomes. PDaaS (Product Development as a Service) — A managed service where Scrums.com takes full end-to-end responsibility for product development from concept to deployment. SEOP (Software Engineering Orchestration Platform) — Scrums.com’s core platform that coordinates talent, delivery, and systems to help organisations build and operate software at scale. Scope — A purchasable unit of engineering work with a defined outcome, constraints, deliverables, and acceptance criteria. Service Line — The operational unit through which a capability or engagement runs within a workspace. SKU — Stock Keeping Unit. A unique identifier for each Scrums.com product or service, used in order forms and billing. Sprint — A fixed-length (typically two-week) delivery cycle in which a defined set of work items is completed. Subscription — A plan that provides access to the Scrums.com platform. Current plans are Free, Access, Business, and Enterprise.

​
T–Z

Talent Seat — A full-time dedicated engineer role (e.g. Engineering Seat, QA Seat, DevOps Seat) providing up to 160 hours of capacity per month, billed at a fixed monthly rate. Tech Stack — The set of programming languages, frameworks, and infrastructure tools used to build a software product. Tier — A subscription level that determines deployment access, governance controls, support, and environment options. Velocity — A measure of how much work a team completes in a sprint, typically expressed in story points. Workspace — A client’s dedicated environment within the Scrums.com platform, containing their teams, projects, analytics, and settings.
Last modified on September 15, 2026