Traditional Waterfall Development

• Phases of waterfall

  • Requirements

  • Design

  • Code

  • Integration

  • Test

  • Deploy

• Problems with the waterfall approach

  • No provisions for changing requirements

  • No idea if it works until the end

  • Each step ends when the next one begins

  • Mistakes found in the later stages are more expensive to fix

  • There is usually a long time between software releases

  • Teams work separately, unaware of their impact on each other

  • The people who know the least about the code are deploying it into production

Extreme programming (XP)

• Based on the iterative approach to software development

• Intended to improve software quality and responsiveness to changing customer requirements

• One of the first agile methods

• Values

  • Simplicity

  • Communication

  • Feedback

  • Respect

  • Courage

Kanban

• A Japanese manufacturing system in which the supply of components is regulated through the use of instruction cards sent along the production line.

• Core principles

  • Visualize the workflow

  • Limit work in progress

  • Manage and enhance the flow

  • Make process policies explicit

  • Continuously improve