BABOK V2 describes Transition Requirements as “capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to a desired future state, but that will not be needed once that transition is complete. They are differentiated from other requirements types because they are always temporary in nature and because they cannot be developed until both an existing and new solution are defined.”

In simpler terms, transition requirements are what needs to be done to transition to the solution. Below is a list of various types of transition requirements.

• Data Conversion and Migration
  • Data conversions
  • Temporary interfaces
• User Access and Security Rights
  • Security privileges
  • User access
• User Acceptance Testing
  • Test case development
  • Test facility
• Production Turnover and Transition
• • User support and help desk
  • Operations
  • Application support
• User Preparation and Transition
• • Skill enhancements
  • Training delivery
  • One-on-one support
  • Super user programs
• Customer and Supplier Preparation and Transition
• • Communications and notifications
  • Data interchange
• Pilot Testing
• • Model office
  • Pilot test
• Organizational Changes
• • Temporary staffing for backfill
  • New hires
  • Transfers
  • Outplacements
• Infrastructure Transition
• • Servers
  • Storage
  • Network
  • Personal computing devices
• Changes to Policies, Procedures and Forms
• • Policies
  • Procedures
  • Workflow
  • Forms
• Business Continuity
  • BC contracts
  • DR Testing

No matter how good the code, with out attention to transition requirements, stakeholder won’t be satisfied with the result.

[cta id=”7426″]