Effective Software Project Management

The Scoping Phase of an Incremental SDPM Strategy

Basically there is no difference between a Linear and an Incremental SDPM strategy except for the way the deliverables are deployed. Both strategies require a completely documented requirements specification. Given that condition, both strategies are somewhat intolerant of scope change. Unfortunately, they know it will happen, but they proceed on the assumption that it won’t.

As you know, in a Linear SDPM strategy the deliverables are first deployed after all integration testing has been successfully completed and the customer signs off on the acceptance test procedure. The deliverables then move to the implementation stage and are put into production status. The project is completed. The customer doesn’t see any of the solution until they see all of the solution. There is no chance to “try it out” before they buy it. Their only hope is that the developers understood their needs and delivered according to those needs. The customer isn’t looking for any surprises.

In the Incremental SDPM strategy, things are quite different. You still have the same degree of confidence that the requirements are completely defined and documented. The Incremental strategy is scope change–intolerant just like the Linear strategy. The only changes expected are those that emanate from outside the project itself. For example, market changes that compromise the business value of the current scope must be addressed, and change is necessary in order to counter ...