敏捷是 XP、Scrum、Crystal、DSDM、FDD 等方法的总称，它们共享共同原则。 统一流程是一个可用于描述开发流程的框架，RUP 是基于 Rational 工具的 UP 实例之一。 UP 早于大多数敏捷方法，并且可能被视为敏捷，也可能不被视为敏捷。 它们的共同点是敏捷方法和UP都是迭代增量开发（IID）方法。
Agile in an umbrella term for methods like XP, Scrum, Crystal, DSDM, FDD,... that share common principles. The Unified Process is a framework that can be used to describe a development process, RUP being one instantiation of UP based on Rational's tools. UP predates most Agile methods and may or may not be considered as Agile. What they have in common is that both Agile methods and UP are Iterative and Incremental Development (IID) methods.
RUP is a comprehensive iterative and incremental process template. You create a "Development Case" that informs you about what process components you will need in your instance of a development process. You then pull the required process components you need from RUP, like picking items from a menu.
"Agile" is an umbrella term that describes the set of processes that are based on the proposition that software development is a learning process rather than a defined process, and that most high-ceremony artifacts and practices impede the learning process.
SCRUM is a specific Agile project management process. It makes no provisions for how to actually design and develop the system being built.
In the late 1990’s several methodologies began to get increasing public attention. Each had a different combination of old ideas, new ideas, and transmuted old ideas. But they all emphasized close collaboration between the programmer team and business experts; face-to-face communication (as more efficient than written documentation); frequent delivery of new deployable business value; tight, self-organizing teams; and ways to craft the code and the team such that the inevitable requirements churn was not a crisis.
Scrum and RUP are specific software development methods that can enable Agile software development. These methods (and others, such as XP) are not mutually exclusive, and can be combined in many ways to tailor an Agile process suitable for a particular project. This is a good article describing how these methods can be combined.
敏捷和 RUP 分别发展，RUP 建立在 UML 的基础上，现在 IBM 正在努力追赶敏捷浪潮，因为 RUP 没有[更多]大的关注。
Agile and RUP grew separately, RUP on the foundation of UML, and now IBM is trying to catch up the agile wave cause there is no [more] big buzz on RUP.
Well, RUP is a "soup" of practices... You should customize it to drink your "own" soup... Otherwise it will "kill" your project...
In Agile project management, practices adapted from Complex Adaptive Dynamic Systems theory... It has a gentle touch with "human"... RUP does not say much about "peopleware" of project management...
Agile methods talk about "emergent" architecture... Where RUP is architecture-centric... Wants from you first establish stable architecture.
But you can apply RUP in an agile manner...Or you can barrow/steal many technical practices(soup incredents/recipes) from it...
They are both iterative models which seem similar, but both of them are vastly different. RUP is a framework for organizations and teams while Scrum is intended for a product team with stringent guidelines.
发布评论
评论（6）
敏捷是 XP、Scrum、Crystal、DSDM、FDD 等方法的总称，它们共享共同原则。 统一流程是一个可用于描述开发流程的框架，RUP 是基于 Rational 工具的 UP 实例之一。 UP 早于大多数敏捷方法，并且可能被视为敏捷，也可能不被视为敏捷。 它们的共同点是敏捷方法和UP都是迭代增量开发（IID）方法。
Agile in an umbrella term for methods like XP, Scrum, Crystal, DSDM, FDD,... that share common principles. The Unified Process is a framework that can be used to describe a development process, RUP being one instantiation of UP based on Rational's tools. UP predates most Agile methods and may or may not be considered as Agile. What they have in common is that both Agile methods and UP are Iterative and Incremental Development (IID) methods.
RUP 是一个全面的迭代和增量过程模板。 您创建一个“开发案例”，告知您在开发流程实例中需要哪些流程组件。 然后，您可以从 RUP 中提取所需的流程组件，例如从菜单中选择项目。
“敏捷”是一个涵盖性术语，它描述了一系列流程，这些流程基于以下主张：软件开发是一个学习过程，而不是一个已定义的过程，并且大多数高仪式的工件和实践都阻碍了软件开发的发展。学习过程。
SCRUM 是一种特定的敏捷项目管理流程。 它没有规定如何实际设计和开发正在构建的系统。
RUP is a comprehensive iterative and incremental process template. You create a "Development Case" that informs you about what process components you will need in your instance of a development process. You then pull the required process components you need from RUP, like picking items from a menu.
"Agile" is an umbrella term that describes the set of processes that are based on the proposition that software development is a learning process rather than a defined process, and that most high-ceremony artifacts and practices impede the learning process.
SCRUM is a specific Agile project management process. It makes no provisions for how to actually design and develop the system being built.
敏捷是一种软件开发方法：（
引自敏捷联盟网站）
Scrum 和 RUP 是可以实现敏捷软件开发的特定软件开发方法。 这些方法（以及其他方法，例如 XP）并不相互排斥，并且可以通过多种方式组合来定制适合特定项目的敏捷流程。 这是一篇好文章，描述了如何组合这些方法。
Agile is an approach to software development:
(quoted from the Agile Alliance website)
Scrum and RUP are specific software development methods that can enable Agile software development. These methods (and others, such as XP) are not mutually exclusive, and can be combined in many ways to tailor an Agile process suitable for a particular project. This is a good article describing how these methods can be combined.
敏捷和 RUP 分别发展，RUP 建立在 UML 的基础上，现在 IBM 正在努力追赶敏捷浪潮，因为 RUP 没有[更多]大的关注。
Agile and RUP grew separately, RUP on the foundation of UML, and now IBM is trying to catch up the agile wave cause there is no [more] big buzz on RUP.
好吧，RUP 是实践“汤”...您应该定制它来喝您“自己的”汤...否则它将“杀死”您的项目...
但是您可以以敏捷的方式应用 RUP...或者您可以从中窃取/窃取许多技术实践（汤成分/食谱）...
Well, RUP is a "soup" of practices... You should customize it to drink your "own" soup... Otherwise it will "kill" your project...
But you can apply RUP in an agile manner...Or you can barrow/steal many technical practices(soup incredents/recipes) from it...
它们都是迭代模型，看起来很相似，但两者却有很大不同。 RUP 是组织和团队的框架，而 Scrum 是为具有严格指导方针的产品团队而设计的。
我建议你阅读这些：
SCRUM
RUP
They are both iterative models which seem similar, but both of them are vastly different. RUP is a framework for organizations and teams while Scrum is intended for a product team with stringent guidelines.
I'd suggest you read these:
SCRUM
RUP