The phases of a WUP project are shown below, including what happens in these phases. Keep in mind that the phases as stated here are not linear in time, but they consist merely of recurring events.

Conceptual phase

• Create business concept
• Verify technical scope
• Consider contextual risk
• Get sponsor commitment

Analysis phase

• Define problem domain
• Functional Design
• Define domain classes
• Define use cases
• Define stories
• Consider requirements risk
• Initial design
• Prototyping
• Technical Design
• Define initial database
• Define initial class model
• Consider technological risk
• Put together a team
• Consider skills risk
• Define increments
• Define release dates
• Get sponsor commitment

Development phase

Start increment
• Production design
• Redefine use cases
• Pick use case
• Start realizing a story
• Define a test
• Run a test
• Finish story
• Finish use case
• Integrate the system
• Run integration tests
• Release
• Evaluate (total design)
• Optimization
• Fix slipped-through bugs
• Acceptation test
• End-of-increment release
• Deployment
• Get sponsor commitment for new increment (optional)

Post-deployment Phase

• Evaluate development phase
• Train users (optional)
• Maintenance

When changing phases, the customer should be able to call off the continuation of the project. Each of the phases can be considered a time box and each of them can be planned and estimated in cost separately. During the phases, the customer should be closely involved and able to steer the project at all times.