A rollout is the distribution of the final version of an application. This could be a software project rollout or a software implementation.
A rollout is executed within a execution window (or) a change window. A rollout execution involves a collection of tasks, each of them to be executed within a pre-planned time window and assigned to a user.
Thus the following are a part of a rollout.
- Participants or Users
Refer create and manage a rollout section for more information.
Every rollout carries some amount of risk. This risk can be captured along with the rollout.
This is one of the most powerful feature of rolloutMan. The ability to clone entire rollouts into newer rollouts for different reasons explained below. This allows the user to reset the rollout and start the implementation again without having to deal with complex details of re-entering/ managing the rollout details and participants.
rollout Cloning is available only in the "Table view" of the rollout Dashboard. For more details refer - Define & Manage Rollouts > rollout Dashboard chapter .
Figure 2.1. Rollout Cloning
Description / Use case
|i||Clone rollout for Next Iteration||
Each rollout keeps track of its iteration, starting with 1. If a rollout fails, then the same rollout will need to be repeated at a later date which will in most cases carry exactly the same steps and properties.
Cloning a rollout for a newer iteration, helps to avoid effort around repeating and organizing the same functionality / steps.
This feature is helpful in both "Waterfall" & "Agile" based SDLC projects.
|e||Clone rollout for a environment||
Once a rollout has been done for one environment, the same rollout needs to be carried out to the next environment.
Simply cloning the same rollout to another environments, gives a good starting point with exactly the same steps. This feature is extremely useful in moving a project from UAT deployments to Pre-production or Live Deployments.
This is particularly helpful in "Waterfall" based SDLC projects.
|p||Clone rollout for newer Project||
This feature is available, when there are repeated rollouts with minor changes between each rollout, in which case a "Rollout template" should be created, which could be cloned into new projects with every iteration.
This is particularly helpful in "Agile" based SDLC projects.