Adopting the Rational Unified Process : Success with the RUP

Stefan Bergström, Lotta Råberg

Adopting the Rational Unified Process : Success with the RUP
  • 出版商: Addison Wesley
  • 出版日期: 2004-01-08
  • 售價: $1,400
  • 貴賓價: 9.5 折 $1,330
  • 語言: 英文
  • 頁數: 272
  • 裝訂: Paperback
  • ISBN: 0321202945
  • ISBN-13: 9780321202949
  • 相關分類: 專案管理 PM、軟體工程

    • 立即出貨(限量) (庫存=1)

買這商品的人也買了...

相關主題

商品描述

Table of Contents

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.

商品描述(中文翻譯)

目錄


前言。
關於作者。

1. 如何在組織中採用RUP。



實施前。



提高對RUP的認識。



評估目前的情況。



以商業案例激勵。



設定採用目標，確定風險和機會。



制定高層次的採用計劃並制定溝通計劃。



確定要支援的軟體開發專案（試點專案）。



實施期間。



制定詳細的實施計劃。



通過指導支援專案（以及其他方式）。



軟體專案採用特定的RUP子集。



決定您的流程並對其進行文檔化。



適應意外情況（處理風險、機會和目標）。



評估實施工作。



實施後。



實施何時完成？



進行持續的流程改進。



結論。




2. 與RUP的第一次會議。




打包的常識。



通過產品呈現。



什麼是RUP產品？



RUP的結構。



知識庫。



共同語言。



新語言的例子。



幫助專案團隊更有效地開發產品的方法。



結論。




3. 什麼是RUP專案？



RUP中的基本概念。



RUP是迭代的。



RUP的計劃由風險驅動。



RUP以架構為中心。



RUP由用例驅動。



RUP的精神。



RUP專案團隊成員分享他們的智慧。



RUP專案的七宗罪。



計劃過度。



過度細節化。



跳過問題分析。



讓迭代結束日期延遲。



在完成詳細說明前開始建構。



僅在專案結束時進行測試。



未能推動產品的移動

類似商品