The new or changed service is deployed to all user areas in one operation. This will often be used when introducing an application change and consistency of service across the organization is considered important.
The negative aspect of the Big Bang approach is that it increases the risk and impact of a failed Release.
The service is deployed to a part of the user base initially, and then this operation is repeated for subsequent parts of the user base via a scheduled rollout plan.
This will be the case in many scenarios such as in retail organizations for new services being introduced into the stores’ environment in manageable phases.
The Push Approach:
Used where the service component is deployed from the centre and pushed out to the target locations.
In terms of service deployment, delivering updated service components to all users, either in big bang or phased form is using the push approach, since the new or changed service is delivered into the users’ environment at a time not of their choosing.
The Pull Approach:
Used for software releases where the software is made available in a central location but users are free to pull the software down to their own location at a time of their choosing or when a workstation restarts.
The use of technology to automate Releases. This helps to ensure repeatability and consistency. The time required to provide a well-designed and efficient automated mechanism may not always be available or viable.
Using manual activities to distribute a Release. It is important to monitor and measure the impact of many repeated manual activities as they are likely to be inefficient and error prone.