Evaluating the Deployment of New Technology

1. Survey the current environment:
   1. What are the current organizational rules and processes?

   2. What technology is currently used in the organization?

   3. What needs are not being met by the current set of rules, processes, or technologies?

   4. What are the current technology support structures and training levels?

2. Evaluate the new technology:
   1. Does it require the organization to change its rules or processes?

   2. Does it require a different set of support structures, changes in the infrastructure, or training levels?

   3. Will it be able to meet the needs specified in 1c?

   4. Is it a brand new technology, a major upgrade, or a minor upgrade?

3. Make the decision:
   1. If the technology doesn't require a change in the rules, processes, infrastructure, or support required and is a minor upgrade -- test and then release wide scale.

   2. If the technology doesn't require a change in the rules, processes, infrastructure, or support required and is a major upgrade -- test, release in limited production, and then release wide scale.

   3. If the technology doesn't require a change in the rules, processes, infrastructure, or support required and is a new release -- test, pilot, release in limited production, wait for the first revision or patch kit to be released, and then release wide scale.

   4. If the technology requires a change in the rules, processes, infrastructure or support required -- make the changes in those areas first and then proceed with a, b, or c based on whether it is a minor or major upgrade or brand new release.