Content

  1. Overview
    1. Phases of UP
  2. Planning
  3. Standard UP

Overview

The most popular and influential iterative and incremental process framework.

There are 4 phases, each phase with several iterations and has its own objectives. All iterations in all phases are driven by use cases and focus on risk reduction.

  • Inception: understand what to build
    • Vision, high-level requirements, business case
    • Addresses business risks
  • Elaboration: understand how to build
    • Verified baseline architecture, most requirements detailed
    • Addresses architectural/technical risks
  • Construction: build
    • Working product, system test complete
    • Addresses logistical risks
  • Transition: validate solution
    • Stakeholder acceptance
    • Addresses delivery and roll-out risks

Phases of UP

  • UP invariants - phase gates: commitment & progress checkpoint
    • Go/non-go decision points
    • Detect failure early

Planning

  1. Coarse-grained project plan
    • Overall profile of the project
    • Big milestones
    • Default effort/schedule distributions & profile
  2. Phase plan
    • Iterations within & their objective
  3. Fine-grained iteration plans
    • Within time-boxed iteration
      • Gives a series of close, achievable deadlines
      • Allows for tighter control, better decisions
      • Good for team, good for client
      • Too long: complexity; late feedback
      • Too short: no time to finish sufficient new work; management overhead
    • Strictly fixed length, adjust scope accordingly

Standard UP

Description
Inception 0 for maintenance release; more (1-2) if need to elicit and develop requirements/build UI prototype; demonstrate a proof of concept; make the business case and find funding
Elaboration Min. 1 for building on well-established architectural framework; 2 for achieving a good architectural baseline ; 3 for more risks and factors
Construction Min. 1 leading to beta release; 2 for partially complete system before beta; 3 for larger projects
Transition 1 for beta to final release; 2 for allowing more feedback and rework
  • Typical deliverables
    • 1 exploratory prototype (inception)
    • 2 (elaboration) - an architectural prototype and a baseline
    • 2 (construction) – partial or alpha, and beta releases
    • 1 (transition) – the final product release

results matching ""

    No results matching ""