Introduction to OpenUP |  |
Relationships
Contents | Core Principles Minimal, Complete, and Extensible Iteration Lifecycle Micro-Increments Project Lifecycle The OpenUP Family Who Should Use OpenUP
Main Description
Getting Started | Core Principles | Roles | Work Products | Disciplines | Lifecycle
### What is OpenUP? OpenUP is a lean Unified Process that applies iterative and incremental approaches within a structured lifecycle. OpenUP embraces a pragmatic, agile philosophy that focuses on the collaborative nature of software development. It is a tools-agnostic, low-ceremony process that can be extended to address a broad variety of project types. OpenUP layers: micro-increments, iteration lifecycle and project lifecycle Personal effort on an OpenUP project is organized in micro-increments. These represent short units of work that produce a steady, measurable pace of project progress (typically measured in hours or a few days). The process applies intensive collaboration as the system is incrementally developed by a committed, self-organized team. These micro-increments provide an extremely short feedback loop that drives adaptive decisions within each iteration. OpenUP divides the project into iterations: planned, time-boxed intervals typically measured in weeks. Iterations focus the team on delivering incremental value to stakeholders in a predictable manner. The iteration plan defines what should be delivered within the iteration, and the result is a demo-able or shippable build. OpenUP teams self-organize around how to accomplish iteration objectives and commit to delivering the results. They do that by defining and "pulling" fine-grained tasks from a work items list. OpenUP applies an iteration lifecycle that structures how micro-increments are applied to deliver stable, cohesive builds of the system that incrementally progresses towards the iteration objectives. OpenUP structures the project lifecycle into four phases: Inception, Elaboration, Construction, and Transition. The project lifecycle provides stakeholders and team members with visibility and decision points throughout the project. This enables effective oversight, and allows you to make "go or no-go" decisions at appropriate times. A project plan defines the lifecycle, and the end result is a released application.
Key Considerations
Use OpenUP as-is when you have a small, co-located team. Modify OpenUP for small teams with different circumstances (for instance, a novel project or geographically distributed team members). See Supporting Material: Resources for Modifying Methods for more information on how to customize OpenUP.
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright. OpenUP/DSDM Copyright.