Project Implementation Task Sheet

Seq # Date & Time Task Description

100 25-May 11:00 AM Send communcation to stakeholders

110 25-May 11:10 AM Install server config and desktop config for CR078
120 25-May 11:30 AM Reboot Server
130 25-May 11:50 AM Reinstall package
140 25-May 12:00 PM Test CR078
150 25-May 12:30 PM Start Implementation of CR090
160 25-May 1:20 PM Shutdown all systems
170 25-May 1:40 PM Backup all systems
180 25-May 2:00 PM Run build deplyment script
190 25-May 2:20 PM Capture and output to verify
200 25-May 2:55 PM Implement CR09 and CR45 config changes
210 25-May 3:15 PM Implement CR67 website changes
220 25-May 3:35 PM Reboot all systems
230 25-May 4:20 PM Perform basic testing of all changes - CR078, CR090, CR09, CR45 and CR67.
240 25-May 4:45 PM Send communcation to stakeholders
250 25-May 5:10 PM Verify Logs for on billing system
260 25-May 5:35 PM Delete all backup and install scripts form server
 Duration
Phase Owner Status Notes
(mins)
Pre Neel 10 Done Some email bounced back.
Pre Neel 20 Done
Pre Raj 20 Hold Network connectivty issue
Pre Raj 10 Hold Delayed because of Task 102
Core Raj 30 Hold Delayed because of Task 103
Core Raj 50 Hold Delayed because of Task 104
Core Raj 20 To do
Core Raj 20 To do
Core Raj 20 To do
Core Raj 35 To do
Core Sam 20 To do
Core Sam 20 To do
Core Sam 45 To do
Core Sam 25 To do
Post Sam 25 To do
Post Sam 25 To do
Post Sam 25 To do
1. The implementation plan should contain all the tasks to be done before, during and after the release.
2. Each step must have a number, duration and owner assigned.
3. The plan should be updated and circulated at least a few days before the release. Ideally, feedback should be sort from eve
4. The status of the tasks should be updated as the release progresses to keep track of tasks.
5. Release manager is responsible to get updates from the team - it can be via a call or emial.
release.

dback should be sort from everyone a week before the actual implementation.
Release Phase Status
Pre Done
Post Hold
Core To do