Process changes are difficult and it may take time to see their true effects. It is relatively easy and fast to adopt a new tool- you install it, read the user's guide, go through an example, and maybe attend a training course. This transition can last from a few hours to several weeks, however, changing the software development process often means affecting the fundamental beliefs and values of the individuals involved, changing the way they perceive their work, and how they perceive its value. It is a cultural change that's almost political or philosophical in nature.
A process change affects the individuals and the organization more deeply than changing technology or tools. It must be carefully planned and managed. The adopting organization must identify the opportunity and the benefits, convey them clearly to the interested parties, raise their level of awareness, and then gradually change from the current practice to a new one. Ivar Jacobson describes this as "reengineering your software engineering process".
The following areas must be addressed when implementing a process:
There are other areas in addition to those mentioned above that affect the way people work. For example, the physical working environment, organizational culture and politics, and the reward structure.
In addition to those people inside the software development organization, you must also take into consideration the people outside of that organization who will be affected by these changes, such as: