Ad hoc jobs - submitted by authorized users; run only once. e.g. reports, job re-runs, etc.
Scheduled jobs - always run at a certain day and time; initially setup when system is installed; system request submitted for changes; changes approved by management; changes done by production support group. e.g. update the G/L; run the payroll cheques, etc
The Need Today:
Application system implementations – new & releases
Server & workstation systems software updates/upgrades: e.g., operating systems; virus scanners; internet browser; systems mgmt software; MSOffice;
Production Test Plan
Document the tasks required to build, install and configure the system
Internally, it documents commitment of other departments
Externally, it commits vendors to the plan
Prepare a plan: who, what, when, checkpoints, precedents, sign-offs, etc.
Distribute the plan
Hold a final meeting just before the “Roll out”
Plan Deployment for Clients: Desktops and/or Browsers:
Setup users’ security
Build the production version
Develop setup scripts
Create a delivery package
Set version counter for registry
Migrate to production
Release desktop version
Begin installation testing during integration test phase
Your Turn (small groups):
You are a project manager working on the Urgent Care Health Clinic project in the consulting division at IBM that specializes in developing new systems for the Health Industry. The system you have developed for Kitchener will be used Canada wide in 28 locations.
What configurations will you initially test for deployment?
One year from now, how could this change?
What impact on IBM operations can this have?
Create a high level deployment plan.
The War Room
A location for the team to work and meet during deployment
You need: chairs, work surfaces, computers, telephones, flip charts, white boards, 24x7 access, etc.
Decorate the walls with project plans, database design, etc.
Maintain Focus on the Project
Be prepared for staff to panic
Know the personalities of your team
Be prepared to make decisions
Be prepared to “lighten up”
Remember to eat and sleep
Maintain a sense of humour
Environmental Impact Study “ Stuff happens!” Goal - minimize disruption Verify – schedules,server space,bandwidth/performance Check interaction with other systems – changes occur Update the Help Desk on your project Update your contact list of support staff Review the deployment plan one more time! CREATE FALLBACK/CONTINGENCY PLAN
As project deadline nears:
Triage the remaining functionality and analyse the impact of the removal of any functionality
NB: Leave time for testing
Full launch – incomplete and buggy
“ Soft launch” – e.g. a trial version
Don’t hide problems from your client or user
Cutover: Test the Production System
Happens after you have built the environment and before system is available in production
Prepare a test plan
Use “live” data
Involve the users
Do it outside normal business hours
If system fails, be prepared to rollback
Use company help desk, if possible
Document the problem formally
Inform user of progress
Track User’s Problems and Questions
Be ready for problems and questions
Document all occurrences of issues, bugs, anomalies, etc.
Have a Change Request form for users to submit problems
Review issues daily
Prepare a summary report at completion of deployment
From Development Mode to Maintenance Mode
Help Desks create a ticket for every incident
Developers will resist “tickets”
Need to track user requests – hand over support to Help Desk and systems support group
Capture project knowledge
Document all requests
Update test case database to include issues
Update user documentation
Your turn: You are a project manager working for Conestoga Consulting in Cambridge. You have a project to develop and implement a Web Based Course Enrollment system for Conestoga College. You are nearing the completion of the project and have to come up with a deployment strategy: What would your strategy be to deploy the system? Cover: Communications, training, client deployment, type: phased vs trial vs full cutover, production testing, & problem reporting.