| In our first scenario for a RUP adoption program, we assume that the adopting organization has roughly 10 project teams with an average of 10 project members , and it plans to adopt all of the RUP disciplines and introduce new tools to support requirements management and visual modeling. They already have good tools in place for automated testing and for Configuration and Change Management. Even though some people in their organization have experience with the RUP, most do not. Many are new to iterative development, but quite a few have used other structured approaches. Based on the size, objectives, and experience level described earlier, they choose the program profile shown in Figure 11.3. -
PTEP. They expect to be able to adopt the RUP and supporting tools with only minor customizations. They will produce three RUP configurations for stereotypical projects, customize some templates, produce stereotypical development cases, and set up a recommended mentoring and training program for projects. They do not plan to produce any RUP Plug-Ins or do any other major customizations to training material. They will use tools with a minimum of customization, so they need only one PTEP. (Of course, we still would recommend that the organization perform continuous process improvement ”see the section Continuous Process Improvement.) -
Pilots. They need to verify that project can successfully adopt both the RUP and the tools that are new to the organization, so they need to run a pilot project. Because they do not need to verify any major customizations, they initiate the pilot during early Elaboration of the PTEP. If they feel that the three configurations of the RUP are radically different from each other and that their adoption is associated with a lot of risk, they may instead want to run three pilot projects, allowing them to test and gain experience with each of the three configurations. -
Software development project. As soon as the PTEP is done, the RUP and associated tools are rolled out, project-by-project. Figure 11.3. A Typical Approach to Implementing Moderate Change. When implementing the RUP and supporting tools presents moderate change to your organization, it is normally sufficient to run one pilot project during your PTEP , and roll out the new process and tool environment to all projects at the end of the PTEP .  |
