Planning:

Planning is an important phase of migration. This phase involves

1. Determining HP ALM artifacts that need to be migrated

2. Reviewing production, stage environments of HP ALM and Zephyr

3. Optimizing stage environments

• Determine HP ALM artifacts that need to be migrated

  It is important to acknowledge that not all the data you have in legacy system remains good to be transferred. We review with you, how your testing methodologies, practices have changed over the years and determine the right HP ALM artifacts we suggest transferring to Zephyr. This is typically one or two days of effort where we engage in a dialog with all the project leads and managers.

• Review Production, Stage environments

  Not all HP ALM environments are configured the same. We undertake end to end analysis of hardware, memory allocation for processes, API throttling configurations, network topology etc. We engage with system administrators, network administrators and database administrators.

• Optimize stage environment

  We determine which style of migration is most suitable for your needs. Typically, we follow big bang migration or trickle migration. Big bang migration is conducted over a weekend when both HP ALM and Zephyr are shut down for users. With this approach, we suggest at least one dry run of the migration in the stage environment before the live event. With trickle migration, we take an incremental approach to migrating data. We run both the systems in parallel and move projects based on business needs. With this approach a thorough analysis of data dependency is conducted in a stage environment.

  With either approach, we undertake at least one week of review, preparation and optimization of stage environment; this includes optimization of system that has Zephyr HP ALM Migration adapter installed. Full access to stage environment is required.