4.2. Create a Rollout

To create a rollout, go to Rollout Dashboard and click on "Add Rollout" button
Add New Rollout

Figure 4.4. Add New Rollout

 
Adding a new rollout has 4 distinct steps
Rollout Steps

Figure 4.5. Rollout Steps

Project Details : Enter core rollout details as prompted by the form fields. 
Once details of this page are entered, the rollout is immediately created and a rollout number is associated with this rollout. This rollout number will uniquely identify this rollout and cannot be changed. 
All the following steps are only to add more information to the rollout and can be done at a later point as well. 
Choose Applications: Choose all the applications involved with the rollout. rolloutMan is designed to be able to support rollouts for multiple applications. Sometimes, its just for one application, while other times the change will include steps for other platforms / applications as well. 
Choose Groups: Choose list of user groups who would be participating in the rollout. This is crucial to be able to assign tasks to relevant team members.
Add Project Tasks: Finally, start adding tasks to the rollout. Refer Add task chapter to find out more ways to add tasks.
 
Go through further pages to understand each of these sections in detail.
Project Details
This is one of the first forms while adding a new rollout. 
Rollout - Add Project Details

Figure 4.6. Rollout - Add Project Details

 
The following are the form fields:
Rollout Name Name of the rollout. 
Change Number List of all change numbers to associate this rollout with. Usually one rollout is associated with only one change numbers, however sometmes, it might make business sense (or) is economical to combine multiple changes in a single rollout -for e.g. for maximising rollout window availability during a change freeze etc.
Environment
This is the "Project Environment" under Configuration > Applications > Environments. This Environment should be the the logical environment of the rollout. for e.g. System Test or UAT.
Each of the participating applications might have different environments, which is added in the next "Choose Application" Section following this page. 
Short Description Add a short description of the project rollout.
Detailed Description
Detailed description for the rollout. Usually contents of this field is of the format:
  • why is this rollout being done? what is the business benefit ?
  • which team is performing this rollout.
  • Any other details / text 
 
Rollout Type Refer rollout Type for more information on this field.
Service Type
Refer Business Service type for more informaiton on this field.
Rollout start window 
Start window of the rollout - date and time.
This can usually be obtained from the change management system (if there is a change covering this rollout.) However, this doesnt have to strictly match the change window. For e.g. if there are preparation tasks which can be performed before the change window and not impacting the applications, then that can be planned in as well after the rollout start date.
For non-production environments, where there might not be a change process implemented, this is the start datetime of the window when this change is expected to be executed.
Do note that all the "Rollout Tasks" will fall under after this rollout start window.
Rollout End window
Time when the rollout window will end.
Risk Perception
Risk Perception for this rollout. Refer risk perception chapter for more information.
Risk Description
Capture details of the risk involved with this rollout.
 
Click on "Next" button to contine to the next page in the wizard. This button also saves the contents added as a rollout and assigns it a rollout number.
All further steps can be added later as well (or) the user can decide to continue with the wizard.
Choose Application
Choose the applications that are involved in the rollout.
Do note that an application in this context doesnt have to be a software application, but is a generic term used for any software that undergoes a change, and hence is participating in the rollout.
For e.g. these could be Custom Software applications, COTS software's, Database's, Operating systems, Disks, loadbalancers, etc.
Rollout - Add Application

Figure 4.7. Rollout - Add Application

 
Form fields:
Application Name
Choose application from the dropdown.
Refer "Applications" for more information in adding and managing applications.
Environment
This is the "Application Environment" under Configuration > Applications > Environments. This Environment should be the the logical environment of the rollout. for e.g. System Test or UAT. 
Also refer to Application - Environment relationship for understanding which one will come in dropdown.
Each of the participating applications might have different environments, which is added in the next "Choose Application" Section following this page. 
 
Clicking on "Save" will show them in the table below. 
These could be removed, if needed using the, bin icon next to each of the lines.
Only one environment for an application can be added to one rollout.
 
Click on "Next" button below to go to the next page. 
Assign Groups
Assign the list of all user groups involved with the rollout. This association allows users to be selected (from a dropdown) while assigning rollout tasks. 
All user groups/ interested parties should be assigned under this section.  Only users belonging to one of the added groups will be available for task assignment. 
Assigning a group of users allows to change users for a given task in cases when a user is not available to perform a planned task in rollout.
User groups could be added or removed as needed under a rollout.
Rollout - Assign Groups

Figure 4.8. Rollout - Assign Groups

 
This page could be reached from the following paths:
  • As part of the "Add New Rollout" wizard flow
  • From the left menu > Rollouts > [Select Interested Rollout] > Assign Groups 
  • From Rollout Dashboard > [ Select Interested Rollout ] > Assign Groups button
 
Create Task
This is the last step of a Create new rollout Wizard.  This step automatically directs the flow of a rollout definition into a task creation, allowing users to create tasks in the rollout. 
Follow Task Management section > Add New Task  for more information around adding new tasks.
Follow Task Management section for more information around tasks.