Difference between revisions of "Release"
(→Definitions) |
(→Practices) |
||
| Line 7: | Line 7: | ||
:[[Release]]. A version of a service or other configuration item, or a collection of configuration items, that is made available for use. | :[[Release]]. A version of a service or other configuration item, or a collection of configuration items, that is made available for use. | ||
| − | == | + | ==Management practice== |
| − | + | :''Main wikipage: [[Release management practice]]'' | |
[[Category: Information Technology]][[Category: Business Analysis]][[Category: Agile]][[Category: Articles]] | [[Category: Information Technology]][[Category: Business Analysis]][[Category: Agile]][[Category: Articles]] | ||
Latest revision as of 02:56, 29 December 2020
Release is the transition of an increment of potentially shippable product from the development team into routine use by customers. Releases typically happen when one or more sprints has resulted in the product having enough value to outweigh the cost to deploy it.
Definitions
According to the Agile Extension to the BABOK Guide (preview),
- Release. The transition of an increment of potentially shippable product from the development team into routine use by customers. Releases typically happen when one or more sprints has resulted in the product having enough value to outweigh the cost to deploy it.
According to the ITIL Foundation 4e by Axelos,
- Release. A version of a service or other configuration item, or a collection of configuration items, that is made available for use.
Management practice
- Main wikipage: Release management practice
