The Unified Process (UP) has emerged as a popular
modern process for software development-and with good reason, as
it includes skillful best practices such as iterative development,
and early attention to high-risks. Furthermore, the UP process framework
encourages flexible adoption, providing a structure that can scale
up and down.
Contrary to some misperception, the UP encourages
an agile approach. In this tutorial you will learn the essential
and most useful UP concepts and practices, the keys to its successful
introduction in an organization, and how to apply the UP in an adaptive
and agile spirit.
Further, most Extreme Programming (XP) and Scrum
practices and values are either part of the UP, or specializations
of more general UP guidelines. What are these, and which may be
adopted consistent with and within a UP project? Nevertheless, this
tutorial motivates the need for more than pure XP on many projects,
and promotes the skillful capacity of the UP to provide a variety
of optional practices and artifacts on larger or higher-ceremony
projects. You will learn why a combination of primarily the UP with
some XP practices is an excellent process approach.
- The key UP ideas to know and apply.
- The motivation and business case for the UP.
- What UP artifacts are really worth creating?
- UP anti-patterns: common worst-practices in adoption and use.
- How to adopt the UP within an organization.
- XP practices within the UP.
- Challenges of pure XP.
- How to plan an iterative UP project.
- Tips for good UP artifacts and models.
- UP models and the UML.
- How to define a UP development case.
- How to do architectural analysis and describe architectures
in the UP.
- How to fail with the UP: You know you didn't understand it when