A great book regarding Unified Process is: http://www.craiglarman.com/wiki/index.php?title=Book_Applying_UML_and_Patterns http://www.craiglarman.com/wiki/index

A great book regarding Unified Process is: http://www.craiglarman.com/wiki/index.php?title=Book_Applying_UML_and_Patterns http://www.craiglarman.com/wiki/index.php?title=Book_Applyin... I found its practical blending of UP with concepts traditionally associated with other processes quite illuminating. For example, here is a snippet from section 1.1: Iterative Development, Agile Modeling, and an Agile UP Given many possible activities from requirements through to implementation, how should a developer or team proceed? Requirements analysis and OOA/D needs to be presented and practiced in the context of some development process. In this case, an agile (light, flexible) approach to the well-known Unified Process (UP) is used as the sample iterative development process within which these topics are introduced. However, the analysis and design topics that are covered are common to many approaches, and learning them in the context of an agile UP does not invalidate their applicability to other methods, such as Scrum, Feature-Driven Development, Lean Development, Crystal Methods, and so on.