2.8. What is an Agile UP?
The UP was not meant by its creators to be heavy or un-agile, although its large optional set of activities and artifacts have understandably led some to that impression. Rather, it was meant to be adopted and applied in the spirit of adaptability and lightnessan agile UP . Some examples of how this applies:
- Prefer a small set of UP activities and artifacts. Some projects will benefit more than others, but, in general, keep it simple. Remember that all UP artifacts are optional, and avoid creating them unless they add value. Focus on early programming, not early documenting.customizing UP p. 37
- Since the UP is iterative and evolutionary, requirements and designs are not completed before implementation. They adaptively emerge through a series of iterations, based on feedback.evolutionary A&D p. 25
- Apply the UML with agile modeling practices.agile models p. 30
- There isn't a detailed plan for the entire project. There is a high-level plan (called the Phase Plan ) that estimates the project end date and other major milestones, but it does not detail the fine-grained steps to those milestones. A detailed plan (called the Iteration Plan ) only plans with greater detail one iteration in advance. Detailed planning is done adaptively from iteration to iteration.
agile PM p. 673 The case studies emphasize a relatively small number of artifacts, and iterative development, in the spirit of an agile UP.