Delivery Process: OpenUP/Basic Lifecycle
Aimed to support small projects, this delivery process for iterative software development is based on risk management, driven by use cases and architecture centric. Development is based on iterations, use-case scenarios driven. Up-front thinking is invested on doing design and architecture, but capturing design and architectural decisions in visual models is optional.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Purpose
  • To offer process guidance for small scale projects
  • To allow project managers to create project plans based on the proposed work breakdown structures
  • To allow project managers to assign work and track status based on goals
  • To allow team members to understand how to perform their work to achieve project goals
Relationships
Description

OpenUP/Basic is an iterative process with iterations distributed throughout 4 phases: Inception, Elaboration, Construction and Transition.

Each phase may have as many iterations as needed, depending on degree of novelty of the business domain, technology being used, architectural complexity and project size, to name a few factors.

In order to offer a quick-start for teams to plan their iterations, OpenUP/Basic provides templates of Work Breakdown Structures (WBS) for each iteration and a template of WBS for an end-to-end delivery process with the four known phases.

Iterations usually can have variable lengths, depending on project characteristics. The default recommendation is one-month iterations, which gives a fair amount of time for projects to deliver functionality periodically, allows continuous customer feedback, and provides timely risks and issues management during the course of the project.

OpenUP/Basic is aimed to the offer process guidance to small projects:

  • 3 to 6 people in the team
  • 3 to 6 months effort
Properties
Event-Driven
Multiple Occurrences
Ongoing
Optional
Planned
Repeatable
Illustrations
More Information