OpenUP Methodology: Introduction

Updated:
OpenUP (Open Unified Process) is a lean, open-source version of the Unified Process. It applies iterative and incremental development within a structured life cycle of four phases: Inception, Elaboration, Construction, and Transition. The Eclipse Foundation describes OpenUP as a minimal, complete, and extensible software development process for small, co-located teams. It keeps the architecture focus of RUP and adds agile practices such as a work items list and short time-boxed iterations.
Key Takeaways
- OpenUP was developed in the Eclipse Process Framework project, with content contributed by IBM in 2006.
- It is built on four principles: collaborate, balance, focus, and evolve.
- Work is organized in three layers: micro-increments, iterations, and the project life cycle.
- Compared with RUP, OpenUP is smaller and free, and compared with Scrum, it adds phases and milestones.
What Is OpenUP
OpenUP was created in the Eclipse Process Framework (EPF) project, which started in 2005. IBM contributed process content to the project in January 2006, and OpenUP 1.0 was delivered as part of EPF 1.2. The goal was to offer a free process that keeps the proven ideas of the Rational Unified Process without its size.
The published OpenUP process calls itself a “lean Unified Process”. It is tool-agnostic and low-ceremony, follows the values of the Agile Manifesto, and can be extended for other project types. Teams start with the minimal set of practices and add more only when a project needs them.
The Four Core Principles of OpenUP
OpenUP is built on four principles. Each one corresponds to a set of practices in the process:
| Principle | Official statement | What it means in practice |
|---|---|---|
| Collaborate | Collaborate to align interests and share understanding | The team and stakeholders work together daily and agree on goals |
| Balance | Balance competing priorities to maximize stakeholder value | Scope, cost, and schedule are traded off based on value to stakeholders |
| Focus | Focus on the architecture early to minimize risks and organize development | The riskiest technical decisions are tested in code during the early iterations |
| Evolve | Evolve to continuously obtain feedback and improve | Each iteration ends with feedback that changes the plan for the next one |
Three Layers of Work
OpenUP organizes work at three levels, each with its own time span and result:
| Layer | Time span | Result |
|---|---|---|
| Micro-increments | A few hours to a few days | A small, measurable piece of work done by one person |
| Iteration life cycle | Typically a few weeks | A build that can be demonstrated or shipped |
| Project life cycle | The whole project, in four phases | A released application |

Micro-increments give the team a steady pace and a very short feedback loop. We describe each layer in detail in our series on the iteration life cycle, micro-increments, and project life cycle.
The Four Phases and Milestones
The four phases come from the Unified Process. Each phase contains one or more iterations and ends with a milestone where stakeholders decide whether to continue:
| Phase | Focus | Milestone |
|---|---|---|
| Inception | Agreeing on scope, goals, and a technical approach | Lifecycle Objectives |
| Elaboration | Building and testing the architecture, refining requirements | Lifecycle Architecture |
| Construction | Developing the solution in increments and testing it | Initial Operational Capability |
| Transition | Deploying the product and preparing users and the environment | Product Release |
Need a team that ships every iteration?
OpenUP vs RUP vs Scrum
OpenUP sits between RUP and Scrum. Here is how the three approaches compare:
| OpenUP | RUP | Scrum | |
|---|---|---|---|
| Origin | Eclipse Process Framework, open source | Rational Software, later IBM, commercial | Ken Schwaber and Jeff Sutherland, the Scrum Guide |
| Life cycle | Four phases with iterations inside | Four phases with iterations inside | A continuous series of sprints, no phases |
| Iteration length | Typically a few weeks | Set by the project | One month or less |
| Architecture | Addressed early, in Elaboration | Central to the whole process | Not prescribed |
| Roles and artifacts | A small core set | A large library to tailor down | Three accountabilities and three artifacts |
| Best fit | Small co-located teams that need some structure | Large or regulated projects | Teams that work on a product continuously |
OpenUP borrows several practices from Scrum. In a comparison published in Methods & Tools, Bjorn Gustafsson notes that the OpenUP work items list plays the role of the product backlog, the iteration plan plays the role of the sprint backlog, and the daily stand-up is used in the same way. For details on the Scrum Guide side and on how XP and the Eclipse Way shaped OpenUP, read part 5 of our series.
When to Choose OpenUP
OpenUP works well for a small team that builds a new system with real technical risk and needs formal checkpoints, for example to report to a client or an investor at the end of each phase. It is also a useful reference when a company outgrows informal Scrum and wants an explicit architecture stage without moving to a heavy framework.
For a product that is already live and develops continuously, the phase structure adds little, and Scrum or Kanban is usually simpler. For large programs with many teams and strict compliance, a tailored RUP-style process or a scaled framework gives more control.
How We Use OpenUP Ideas at New Line Technologies
At New Line Technologies, we rarely run OpenUP as published, but we use its structure on new products. In fintech projects, for example, we start with a short elaboration stage where the team builds and tests the riskiest parts of the architecture, such as payment integrations and security, before scaling up development. After that, the team works in regular iterations, and each one ends with a demo for the client.
Learn more about our custom software development services, how a dedicated development team can fit your project, and how this approach relates to the incremental model.
A Common Mistake and How to Avoid It
The most common mistake with OpenUP is treating the four phases as waterfall stages. The team spends Inception and Elaboration writing documents, and the first working code appears only in Construction. In that case, the phases add bureaucracy and the main risk stays untested.
To avoid this, make every phase iterative and require working software at each milestone. By the end of Elaboration, the team should have an executable architecture: a thin version of the system that runs end to end and proves the key technical decisions.
FAQs
Yes, OpenUP follows the values of the Agile Manifesto and uses short time-boxed iterations, a work items list, and daily stand-ups. It adds a structured life cycle with four phases and milestones, which makes it more formal than Scrum.
Both use the same four phases and focus on architecture. RUP is a large commercial process framework with many roles and artifacts that teams tailor down. OpenUP is open source and starts minimal, so teams add practices only when they need them.
OpenUP iterations are time-boxed and typically last a few weeks. Each iteration ends with a build that can be demonstrated or shipped. Inside an iteration, work is split into micro-increments of a few hours to a few days.
The OpenUP materials are now kept in the Eclipse archive, and few teams adopt the full process as published. Its ideas are still in use: many teams combine Scrum with an early architecture phase and milestones, which is close to how OpenUP works.
Planning a new product and want a delivery process with the right amount of structure? Talk to our team, and through our software development services we will help you choose the approach and put together the right team.