Agile vs. Waterfall

Changes in scope in an Agile project is normal and is to be expected?

Waterfall should never be used for any project type

Agile is best for large, complex teams where outcome is known at the start

Waterfall requires close collaboration with one customer

Both Waterfall and Agile deliver a product with value to customers

Configuration Control Boards agree on baselines at each project stage in which project type

Features and Scope are unlocked and can change in which project type

Leaders collaborate and modify the plan based on team input in which project type

Artifacts like charter, design, tests, requirements are managed to meet process gates and compliance in which project type

On what type of project do we prioritize the highest value changes first