A Typical Program for Major Change

In our second 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 and tools for the full lifecycle. The organization has no previous experience with the RUP, and they have very specific needs forcing them to make a fair amount of customization to the RUP before it fits their needs. Many are new to iterative development, but quite a few have used other structured approaches. They have limited experience with the tools they plan to roll out, and they also need to build RUP Plug-Ins to address specific process needs.

They decide to roll out the RUP and associated tools in two increments , where iterative development, the internally built RUP Plug-Ins, requirements management, and Configuration and Change Management disciplines with associated tools are rolled out in the first increment, and all of the RUP and associated tools are rolled out in the second increment. Based on this, they choose the program profile shown in Figure 11.4.

  • PTEPs. They need one PTEP project for each increment. In the first PTEP, they develop the RUP Plug-Ins and tailor the RUP to make it fit with their existing process for Analysis & Design, Implementation, Testing, and Configuration and Change Management. In the second PTEP, they add RUP disciplines for Analysis & Design, Implementation, and Testing, as well as supporting tools. (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 projects can successfully adopt the RUP, tools for requirements management and Configuration and Change Management, and associated process guidance. Therefore they need to run a pilot project early in Elaboration of PTEP. We highly recommend that the same people who do the customizations in the pilot projects act as mentors; in this way, the team not only learns what customizations are needed, but also sees the ideas behind the customizations tried out in the process. As the customizations have been formalized and draft RUP Plug-Ins have been produced, they initiate a second pilot project toward the end of the Construction phase of the PTEP. A third pilot is launched as they wind up the customizations of the second PTEP toward the end of the Construction phase to get feedback on the customizations.

  • Software development projects. As soon as the first PTEP is done, the target process and tools are rolled out to a series of projects. As soon as the second PTEP is completed, the full (customized) RUP and associated tools are rolled out to all projects.

Figure 11.4. A Typical Approach to Implementing Major Change. When supporting tools present a major change to your organization as you implement the RUP , you often need to do an incremental adoption of the RUP and supporting tools. This can be done by having two PTEPs, each supported by one or several pilot projects. At the end of each PTEP , you roll out the current process and tool environment.

graphics/11fig04.gif



The Rational Unified Process Made Easy(c) A Practitioner's Guide to Rational Unified Process
Programming Microsoft Visual C++
ISBN: N/A
EAN: 2147483647
Year: 2005
Pages: 173

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net