Adopting the Rational Unified Process : success with the RUPUpplaga 1

Preface. About the Authors. 1. How to Adopt RUP in Your Organization. Before the Implementation. Create Awareness of RUP. Assess the Current Situation. Motivate with a Business Case. Set Adoption Goals, Identify Risks and Opportunities. Make a High-Level Adoption Plan and Develop a Communication Plan. Identify Software Development Projects to Support (Pilot Projects). During the Implementation. Make a Detailed Plan for the Implementation Effort. Support Projects with Mentoring (Among Other Things). Software Projects Adopt Particular RUP Subsets. Decide upon Your Process and Document It. Adapt to the Unexpected (Handle Risks, Opportunities, and Goals). Evaluate the Implementation Effort. After the Implementation. When Is the Implementation Done? Perform Ongoing Process Improvements. Conclusion. 2. The First Meeting with RUP. Packaged Common Sense. Presented through a Product. What Is the RUP Product? The Structure of RUP. Knowledge Base. Common Language. Examples of the New Language. A Way to Help Project Teams Develop Products More Efficiently. Conclusion. 3. What Is a RUP Project? Essential Concepts in RUP. RUP Is Iterative. Planning in RUP Is Driven by Risks. RUP Is Architecture Centric. RUP Is Driven by Use Cases. The Spirit of RUP. RUP Project Team Members Share Their Wisdom. The Seven Sins of a RUP Project. Planning to Death. Detailing Too Much. Skipping Problem Analysis. Letting End Dates of Iterations Slip. Starting Construction before Fulfilling the Exit Criteria of Elaboration. Testing Only at the End of the Project. Failing to Move the Product to Maintenance. Conclusion. 4. Assessing Your Organization. Who Wants the Assessment and Why? Kicking Off the Assessment. How to Assess. Interviewing People. Reading Process Documentation. Comparing with Other Organizations. What to Assess. People. The Organization. Types of Products and Projects. Supporting Tools. The Current Process. The Current Process Description. Compiling the Material. Identifying Problems. Drawing Conclusions. Formulating Recommendations. The Assessment Report. Presentation of the Findings. Conclusion. 5. Motivating the RUP Adoption. Motivating the Decision to Adopt RUP. Reducing the Productivity Dip. Increasing the Improvement. Comparing the Initial Investment and the Dip with the Improvement. Other Aspects to Cover in a Business Case. Motivating the People. Reactions to Change. Keep Moving between the Four Rooms of Change. Following Up the Business Case and People's Attitudes. Examples of Goals and Measurements. Conclusion. 6. Planning the RUP Adoption. Creating the Implementation Team. Setting Adoption Goals. Identifying Risks and Opportunities. Making a High-Level RUP Adoption Plan. What Should the RUP Adoption Plan Cover? Why Use a Documented Formal Plan? On What Level Should Planning Occur? Who Owns the Plan? Developing a Communication Plan. Identifying Software Development Projects to Support. Choosing a Strategy for the RUP Adoption. Wide and Shallow or Narrow and Deep? Just One Project at a Time or the Whole Organization at Once? How Much Time? Conclusion. 7. Obtaining Support from the Organization. The Implementation Team and Project. Supporting Projects When Adopting a RUP Subset. Harvesting Experiences and Updating the Organization's RUP Adaptation. Documenting Your Project Implementation Plan. Stand By for Changes. Communicating with People in the Organization. Building Competence Among the Employees. Training Sessions. Workshops. Performing Reviews. Artifact Reviews. Milestone Reviews. Performing Mentoring. Training the Mentors. Conclusion. 8. How to Adopt RUP in Your Project. Assessing Your Project. Is RUP a Good Idea? What Are the Characteristics of the Project? How Do the Project Members Usually Develop Software? Documenting the Project Assessment. Selecting from RUP and Planning the Implementation. Deciding upon and Documenting Your Process, Part 1. Planning the Process Support. Documenting the Process Support. Running Your Project and Getting Support on RUP. Getting Support Down to the Activity Lists in the Project's Iteration Plans. Deciding upon and Documenting Your Process, Part 2. Sharing Your Experiences. What Will Happen after the Project? Conclusion. 9. Deciding upon Your Process. Selecting Parts of RUP. Disciplines. Artifacts. Activities. Tools. Best Practices. Going beyond the RUP Base: RUP Plug-Ins. How RUP Builder Can Help You Select a Subset. Other Ways to Get Help for the Selection Process. Things to Not Exclude. Adding Process Information. Adding Guidelines and Examples. Adding Disciplines, Roles, Activities, and Artifacts. Adding a Project Management Method. Changing RUP. Changing Activities. Changing Templates. Changing the Lifecycle. How Can a Mentor Help You Decide upon Your Process? Conclusion. 10. Documenting Your Process. Documentation Tools. Word Processor. HTML Editor. RUP Builder. MyRUP. RUP Organizer. RUP Modeler. What the RUP Practitioner Will See (Documentation Results) Development Process, Development Case, and Iteration Plans. Guidelines and Checklists-Easy and Valuable. Templates and Examples-People Love Them. Roadmaps and Process Views-Help People Find Their Way. Building Your Process Documentation in Stages. Stage 0: The Development Process Before the Adoption Starts. Stage 1: The Development Case for the First Project. Stage 2: The First Draft of the Organizational Development Process. Stage 3: The Next Project Using the Organizational Development Process. How Can a Mentor Help You Document Your Process? Conclusion. 11. A Guide to Successful Mentoring. Knowledge Transfer. How Is Knowledge Created? What Knowledge Is Needed? What Does a Good Mentor Do? Walk Around and Be Present. Encourage People. Never Criticize. Practice What You Preach. Be Prepared to Conduct a Workshop. Know Your RUP. Know Your Limits. Worry, but Be Happy. Keep Up the Speed. Let People Make Mistakes. Typical RUP Adopter Personalities. The Long-Time Employee. The Architectural Guru. The Code Lover or Hacker. The Test Person. The Process Lover or Enthusiast. A Mentor Should Become Redundant. Conclusion. Appendix A. Experiences from Actual Implementations. Volvo Information Technology. Background. Timing/Effort. Long-Term Goals. Configuration. Strategy. Methods for Measuring Success. Challenges, Traps, and What Could Have Been Done Better. Biggest Achievements. Continuation. Covansys Corporation. Background. Timing/Effort. Long-Term Goals. Configuration. Strategy. Create, Maintain, and Enhance Internal Reusable RUP Assets. Methods for Measuring Success. Challenges, Traps, and What Could Have Been Done Better. Biggest Achievements. Continuation. Appendix B. Adding Another Project Management Method to RUP. PROPS. PPS. Glossary. Recommended Reading. Index.