In addition to having all of the activities associated with planning a Linear SDPM strategy, an Incremental SDPM strategy also includes the definition of what development work will take place in each increment. This is significant task, for it involves two concurrent and dependent activities:
Decomposing the Requirements Breakdown Structure (RBS) into minimally coupled and maximally cohesive sets of requirements, functions, and features
Sequencing the development work in order to preserve the dependency relationships between the requirements, functions, and features in each increment
In addition, it would be useful if each increment had sufficient business content to warrant its deployment. If not, the completion of the next increment would be the next opportunity to deploy the then partial solution. The customer would probably prefer to have deployable content at the completion of each increment.
There are three ways to proceed with the decomposition and gathering activity: by requirements, by functions, or by features. For example, you could build ...