Transition Phase

The purpose of the Transition Phase is to build a solid foundation for the full-service definition. Activities in the Transition Phase involve improving the system and software development processes and delivering hot fixes and change requests as part of any potential new release. The focus is on delivering the highest quality in line with expected parameters.

Activities & Deliverables

Activity	Deliverable (description)
Improvements	Improvements defined in the Assessment Phase are implemented.
Team scale-up	Team scales up to incorporate all activities.
Hotfixes	Selected hotfixes deployed into production.
Change requests	Selected change requests implemented and delivered as part of a production release.
Contract	Full-service contract finalised unless already previously completed.
Full-service plan	Plan for the first iteration of full services is created in agreement with the client.

Schedule

The Transition Phase schedule is delivered as part of the Assessment Phase and can last anything from weeks to months depending on the effort required.

Effort

The effort required for the Transition Phase is defined as part of the Assessment Phase, with the contract based on a Time & Material (T&M) model.

Expected Collaboration

The Transition Phase depends on collaboration with the client, specifically team members with knowledge of the system. System-based requirements are specified; collaboration excludes work on hotfixes and change requests.