Definition of done

As explained in Effective Platform Engineering

A definition of done is an agreed set of conditions that must be met for a software task to be complete.

A definition of done is an agreed set of conditions that must be met before a software task is complete. It prevents teams from treating implementation as the finish line: operational readiness, including observability configuration, is part of completion. section 2.2.1

For platform engineering, completion extends through running in production. A task is not fully done if its dashboards, monitors, or alerts still require manual setup after deployment. section 2.2.1

Operational readiness

A feature change reaches done only when its operational configuration is automated alongside the change, allowing the team to observe its behavior and detect unexpected problems after release. section 2.2.1

Figure 2.7 The software delivery lifecycle covers all stages from feature planning through running in production.

Use the delivery lifecycle to locate completion criteria across planning, implementation, observation, and production operation. section 2.2.1

How Effective Platform Engineering covers it

How deep it goes

Defines the principle and applies it to observability configuration, without supplying a complete checklist or governance process.

Examples

Uses automated dashboards, monitors, and alerts as concrete completion artifacts for a change.

What you can do after

Apply it by automating observability configuration as part of every task rather than postponing it until operation.

How it connects

Connects software delivery lifecycle, observability, monitoring, dashboards, alerts, and production operation.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Related concepts

• acceptance criteriauses · Acceptance criteria are verifiable conditions that a requirement, feature, or deliverable must satisfy to be considered acceptable or complete.
• load testinghas part · Load testing evaluates a system’s behavior, performance, and capacity under specified levels or patterns of workload.
• performancehas part · Performance is the measurable effectiveness or operational behavior of a system under specified conditions, assessed through relevant qualities such as task results, speed, responsiveness, throughput, or resource use.
• observabilityhas part · Observability is the ability to infer a system’s internal state and behavior from its externally available outputs, such as logs, metrics, and traces.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.