Saturday, August 19, 2006

Software Development Transition to Support Plan

In this template, instructions are included in italics. When you have completed the template and no longer need the instructions, delete them.

Provide a brief overview of the transition goals, any assumptions that the plan is based on, and any risks that have been identified that could severely limit your ability to complete the transition on schedule.

Goals:
Assumptions:
Risks:
Other:

Transition Team
List the members of the transition team, providing the name of the person who fulfills each role.
The Transition roles typically include the following:
• Transition Leader
• Project Leader
• Transition Specialist
• Project Team
• DBA
• Systems and Networking
• Production Support
• Desktop Support
• Help Desk
• OPS
• Platform Support
• Project Development

Transition Phases
The typical transition lifecycle is given below:
• Initiation
• Ramp-up
• Transition
• Go-Live
• Shakedown
• Steady State

Transition Process Tasks
List the tasks that must be accomplished during the transition process. Some tasks will be repeated for each deliverable—be sure to include each task for each deliverable. This list of tasks can then be given to the project manager to be included in the MS Project plan for the development project. The following table suggests tasks, roles for who is responsible for each task, and a general timeframe for when the task is due. You should replace the role names with actual names, and the general time with a specific due date, and change the text formatting back to regular text. You will probably also have additional tasks to add to the list.

The transition tasks include:
Initiation

• Identify project activities to be completed before transition can start
• Determine timeline
• Establish transition milestones

Ramp-up
• Assign support staff to the application
• Determine actual training needed,based on gap analysis
• Determine roles and responsibilities (such as collect, review, accept deliverables, resolve variances, etc.)
• Assign evaluator for each transition deliverable
• Establish support expectations for IS
• Obtain access/privileges
• Acquire software license agreements for production support
Main Transition
• Develop training plans
• Notify business area(s) of production support procedures
Go-Live
• Notify C&C units of transition to production status
Shakedown
• Establish new on-call lists
Steady-state
• Move development documentation and code to production repository
• Transfer user group/steering committee leadership to production support

2 Comments:

Anonymous Anonymous said...

I really love your site.. Great colors & theme.
Did you develop this website yourself? Please reply back as I'm hoping to create my own personal blog and would like to learn where you got this from or what the theme is called. Appreciate it!
Feel free to surf my blog funnymariogames

11:46 PM  
Blogger Harley Watts said...

custom software development

8:28 PM  

Post a Comment

<< Home