TABLE OF CONTENTS In this chapter, we will consider how some of the agile techniques talked about thus far can fit with more traditional software engineering methods. In particular, we will focus on the Unified Process (also known as the Rational Unified Process or RUP) and PRINCE2.
The Unified Process is a design framework that guides the tasks, people and products of the design process. It is a framework because it provides the inputs and outputs of each activity, but does not restrict how each activity must be performed. Different activities can be used in different situations, some being left out, others being replaced or augmented. It was originally developed by Ivar Jacobson, Grady Booch and James Rumbaugh at Rational. They originally developed the Unified Modelling Language (or the UML) and then went on to create the Unified Process as the process side of their unification efforts (prior to the UML and Unified Process there were a number of competing but similar methods available including OMT, the Booch method and Objectory (Booch, 1994; Rumbaugh et al., 1991; Jacobson et al., 1992). All of these methods (which the authors were each heavily involved in) provided inspiration for UML and the Unified Process. For more details on the Unified Process, see Hunt (2003) and Jacobson et al. (1999).
PRINCE, which stands for Projects in Controlled Environments, is a project management method covering the organisation, management and control of projects. PRINCE was first developed by the Central Computer and Telecommunications Agency...
