Control of Scope, continued
Who can control what variables?
Cost: customer paying, so customer should have control what they get (within bounds of what is possible)
Time: programmers are developing, so programmers should have control (within the bounds of what is useful)
Quality: not a reasonable variable
Scope: key variable for management!
Two strategies identified by Beck:
Make estimates and give feedback frequently to improve accuracy and usefulness. This reduces likelihood that important functionality will be dropped at the last minute from a release.
Focus on customers' priorities; if functionality must be reduced, drop the least important capabilities.
William Wake emphasizes that customer and programmers must have control over their domains
Customer controls scope, priorities, composition and date of releases
Programmer determines time estimates, technical alternatives and consequences, development details within releases
created May 14, 2003
last revised May 15, 2003