Waterfall Vs Agile Project Management

2. Which of the following is a characteristic of a Waterfall approach:

• Attempts to Define Detailed Requirements Upfront Prior to the Start of the Project

• May be Broken Up into Phases with Phase Gates to Approve Phase Transitions

• Requires breaking up the project into iterations

A Waterfall approach is best suited for projects that have high levels of uncertainty

• True

• False

The Waterfall approach was called "Waterfall" because the outputs of one phase flowed into the

next phase as inputs like a "Waterfall"

• True

• False

An Agile project is more likely to result in maximizing the business value the customer receives

from the project

• True

• False

Reduced overhead and faster time to market are generally characteristics of an Agile approach

• True

• False

An Agile approach will ALWAYS result in fastest time to market.

• True

• False

Which projects suits waterfall approach?

• Building the pyramids

• Projects with high certainty

• Building Bridges

• Software

• R & D