Release

A release is an identifiable product version that a team makes available to customers or users.

It combines selected requirements, implemented functions, documentation, configuration items, and related test results. Therefore, it represents a defined and stable product state.

Teams choose the included scope according to value, urgency, risk, legal duties, dependencies, and available resources. Moreover, they should include complete and usable workflows instead of incomplete features.

A Release attribute can link each requirement to its planned delivery version. In addition, traceability connects the included requirements with their sources, components, and test cases.

Version numbers, labels, and configuration management identify the exact package. Consequently, teams can reproduce, test, compare, maintain, or restore that version.

Before delivery, teams verify stability and confirm that the package meets its acceptance criteria. They should also communicate its scope, limitations, and delivery date clearly.

Well-planned versions support transparent scope decisions, reliable delivery, effective risk control, and clear stakeholder expectations.