The Transition Phase

The Transition phase focuses on delivering the system into production. There may be extensive testing that takes place during this phase, including beta testing. Fine-tuning of the product takes place here as well as rework to address significant defects (your stakeholders may choose to accept the existence of some known defects in the current release).

The time and effort spent in Transition varies from project to project. Shrink-wrapped software entails the manufacturing and distribution of software and documentation. Internal systems are generally simpler to deploy than external systems. High visibility systems may require extensive beta testing by small groups before release to the larger population. The release of a brand new system may entail hardware purchase and setup while updating an existing system may entail data conversions and extensive coordination with the user community. Every project is different.

To exit the Transition phase your team must pass the Product Release (PR) milestone. The primary issue here is whether the system can be safely and effectively deployed into production.  If the team passes this milestone the project moves to production. If the project fails in any area above, the project may be re-directed or cancelled (some projects are such disasters that you don't want to even install them).

 

Work By Discipline

Discipline Major Activities
Model
Implementation
  • Fix defects
Test
  • Validate the system
  • Validate the documentation
  • Finalize your test model
Deployment
  • Finalize the deployment package
  • Finalize documentation
  • Announce the deployment
  • Train people
  • Deploy the system into production
Configuration Management
  • Put all work products under CM control
Project Management
Environment
  • Setup operations and/or support environments
  • Recover software licenses


Page last updated: May 13, 2006

This page is tailored with permission from Ambysoft Inc.'s Agile UP Product

Original page is Copyright © 2005-2006 Ambysoft Inc.