Glossary | DX Complete

A

Actual Cost Cost and benefit: The cost measured after launch, when the data is available.
Admin Role: The role that manages users, permissions, and service settings.

Benefit Estimate Cost and benefit: The expected value before work begins.
Benefit Measurement Cost and benefit: The value measured after launch, when the data is available.
Build Delivery: Turning committed requirements into tasks, working changes, and verification.
Business Case Business context: The reason for doing the work, including expected cost, value, and decision to commit, pause, or stop.

Change Request Delivery: A proposed change that needs review, approval, release, or deployment.
Checkpoint Risk and decisions: A confirmation point that reduces risk without stopping progress by itself.
Client/User Role: The person or group that uses the service and provides requests, approvals, feedback, or issue reports.
Coder Role: The role that builds assigned work under Engineering direction.
Commit Business context: Deciding to move forward after cost, value, risk, and confidence are understood.
Complete Engineering Delivery: The delivery part of DX Complete: build, check, validate, and put the change into use.
Constraints Business context: Limits that affect the work, such as time, access, policy, budget, or risk.
Control Risk and decisions: A rule, check, or approval used to reduce risk.
Cost Baseline Cost and benefit: What the current state costs now, when known.
Cost Estimate Cost and benefit: What the proposed future state is expected to cost.

Decision Risk and decisions: The recorded choice, who made it, the reason given, and the points considered.
Dependencies Business context: People, systems, data, or decisions the work depends on.
Deployment Delivery: Putting a release or change into use.
Director Role: The role that sets authority, priority, and escalation direction.

Elicit Business context: Turning expectations into requirements, dependencies, unknowns, and risk before estimating the work.
Engineering Role: The role that turns committed requirements into tasks, working changes, and delivery direction.
Estimate Refinement Cost and benefit: Using real results to improve future cost and benefit estimates.
Evidence Risk and decisions: A record that supports a decision, check, release, or measurement.
Expectation Business context: The result a person or group expects, including how success will be recognized, confirmed where possible.

Feedback Run and support: A signal from a user, support interaction, service issue, or observed result.

Go Live Delivery: Putting a change into use after readiness is confirmed.
Greenfield Business context: Work that starts from a new idea rather than an existing service.

Handoff Delivery: The point where a phase has enough clarity to move into the next phase.

Incident Run and support: An event that affects, or may affect, the service and needs a response.
Initiative Business context: A request or opportunity being considered through DX Complete.
Intake Item Business context: A private item used to keep a loose report, request, observation, correction, feedback, or follow-up at the front door before triage.

Limited Disclosure Business context: A situation where some information is unavailable or cannot be shared.

Measure Cost and benefit: Compare expected and actual cost or benefit when data is available.
Measurement Cost and benefit: Comparing expected and actual cost or benefit when data is available.

Operate Run and support: Run the service, support users, and respond to issues.
Operations Role: The role that monitors and keeps the service running.
Outcome Business context: The result the work is meant to create or improve.

Problem Run and support: An underlying or repeated issue that may need deeper improvement work.
Product Role: The role that defines outcomes and requirements.
Product Validation Delivery: Confirming that the completed work achieves the intended outcome.

QA Role: The role that checks completed work against requirements and success criteria.
QA Verification Delivery: Checking that completed work meets the requirements and success criteria.

Readiness Checks Delivery: The checks used before Go Live to confirm that a change is prepared, supportable, and safe enough to put into use.
Record Business context: Information kept so decisions, work, service issues, and measurements can be followed over time.
Release Delivery: A set of changes prepared to be put into use.
Requirement Delivery: A commitment to make something true in a buildable and checkable way.
Requirement Detail Delivery: Optional behavior, edge cases, or check notes kept with a requirement.
Requirement Set Business context: The group of requirements being estimated, committed, built, or stopped together.
Risk Risk and decisions: Something uncertain that could affect value, delivery, service, or compliance.
Rollback Delivery: Returning from a change when it should not remain in use.

Service Charter Business context: A short statement of the service name, description, problem, and goal.
Success Criteria Delivery: The conditions used to decide whether completed work satisfies the need.
Support Role: The role that helps users and routes issues to the right team.
Support Ticket Run and support: A user request, question, or issue report.

Task Delivery: A piece of work needed to satisfy a requirement.
Transformation Business context: Improving an existing service or way of working.

Voice Business context: A person's own words before they are interpreted or translated.

Workspace Business context: The container for one service and the work connected to it.