Waterfall to Iterative

Iterative development requires a different way of thinking compared to the traditional waterfall model. It requires changes for several groups (Infrastructure, Management Review committees, Release, QA and Production support) supporting/enabling the development organizations. These groups need to get involved at every level rather than at the end and requires changes in the current processes. Often these groups are gatekeepers and resist change in the fear of losing control. While in fact, the controls are in place as a detection points at an earlier stage and still exists as enforcement at a later stage.
Communication and outreach program are important aspects of implementing a new software process at an organization level. Change in the process can be made more easily when the employee buys into the new process. This requires considerable effort to be put in reach out to the individuals and helping employees understand the benefits. A Transition Plan that contains different levels of adopting the new process avoids the big bang effect. Using an Itertative incremental model to implement itself is a good approach