The update of a product or its functionality must be planned, prepared, and released for use in the system.
The work involved in preparing and releasing new features occurs simultaneously across multiple apps:
- Release. A responsible development team employee plans the timeline for system updates, monitors release stages, and collects and publishes information about changes.
- Sprints. A responsible development team employee breaks down the release into periods for processing tickets. For example, a release may occur monthly, while a certain number of tickets must be completed each week. In this case, tickets planned for the release are assigned week sprints to help teams prioritize tasks.
- Tickets. The data in this app is used by product owners, developers, and testers. This is where tasks related to system component changes are reviewed, executed, and tracked.
Release stages
In the ServiceDesk workspace, creating and tracking updates is managed in the Release app. The following stages of release work are displayed as statuses in the app:
- Plan. This status is assigned by default to all new releases.
- In progress. Active work is being done to prepare the release: it is divided into task processing stages, and tickets are assigned to development teams.
- Freeze. At this stage, development of the new functionality is paused. Any unfinished tickets must be finalized and tested. The release page is checked for tickets with the Done status. This list should match the tickets planned for the current release. Product owners add information about the changes.
- Released. It is the final release status, indicating that the system update has been delivered to end users.
- Canceled. This status is assigned to releases that are decided against at any stage.
Each release stage corresponds to specific sprint execution stages and ticket processing. Below, we will explore the process of preparing, executing, and releasing a system update.
Was this helpful?
Found a typo? Select it and press Ctrl+Enter to send us feedback