IT 363 - Wk 2 Waterfall/Traditional vs. Agile

Waterfall/Traditional

A structured, plan-driven SDLC methodology that follows a sequential, phased approach.

Waterfall Phase Flow

Each phase depends on the outcome of the previous phase and is completed in sequence.

Waterfall Advantage

Provides discipline and tangible outputs at the end of each phase.

Waterfall Advantage: Control

Provides greater control through a defined timeline.

Waterfall Disadvantage

Has limited flexibility because there is little room for change once a phase is considered complete.

Agile

An iterative software development approach that embraces change throughout development.

Agile Iterative Development

Development occurs through repeated short cycles rather than one long sequential process.

Agile Methods

Common Agile methods include eXtreme Programming (XP) and SCRUM.

Short Iterations

Agile projects are developed in short cycles so progress and changes can be addressed frequently.

Customer Involvement

Agile emphasizes frequent customer involvement, including the use of an on-site customer.

Planning Games

An Agile practice in which planning is performed collaboratively and repeatedly throughout development.

Constant Feedback

Agile relies on continuous feedback to improve the system during development.

People Oriented

Agile emphasizes communication, collaboration, and the people involved in developing and using the system.

Waterfall vs. Agile: Structure

Waterfall is sequential and plan-driven, while Agile is iterative and designed to accommodate change.

Waterfall vs. Agile: Flexibility

Waterfall allows little change after a phase is completed, while Agile embraces change throughout development.

Waterfall vs. Agile: Customer Involvement

Agile emphasizes frequent customer involvement and feedback, while the slides describe Waterfall primarily as a sequential phased process.

Waterfall vs. Agile: Development Style

Waterfall progresses phase by phase, while Agile uses short iterations with repeated planning and feedback.