Why are software delivery teams
eternally engaged in a battle to
contain one of the most volatile
aspects of software engineering, the scope?
Containment of scope is as much an art as
it is a science. This article analyzes the root
causes of scope expansion.
Since scope is a collection of requirements,
let me define a 'good requirement.' A
requirement is considered good if it is:
• Unambiguous • Comprehensive
• Consistent • Enduring
Scope expansion is induced by the two main
stakeholders: the customer and the delivery
Customer-induced scope expansion
Given below are various reasons for customerinduced