Agile Development & The Unified Process
The Unified Process
The Unified Process was invented by IBM and works well for all kinds of development. You take the project and divide it into 4 phases (Inception, Elaboration, Construction and Transition) and those phases into 9 steps.
Phases represent a percentage of the total build and have specific skill sets tied to them.
- Inception: conceive of what you are going to build
- Elaboration: explore some specifics on what you are building
- Construction: build what you are building
- Transition: take the thing you built and transition it to its final home
On very large projects, each phase, stage or step could then be divided down into its own set of phases, stages and steps.
The unified process works wonders on long term scope. To optimize the day to day development schedule, many employ the agile development method. This approach lends to daily builds (it;s nearly required) and keeps everyone on track. Developers communicate with each other as well as the client. More often than not, when compared to other approaches, agile development yields results closer to expectations, as well as closer to on time and on budget.
– Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
There is value in the items on the right, I value the items on the left more.
Agile Methods within the Unified Process
Although the methods appear to be incompatible on the surface, blending The Unified Process with Agile Methods works rather well.