Effective Software Project Management

Traditional Versus Agile Scope Change Management

Scope change is the bane of the traditional project manager. Every scope change request brings with it the work needed to generate the project impact statement as the deliverable from having processed the change request. That can be substantial, especially if there is a high frequency of scope change requests. Someone on the team has to process that scope change request, and that takes away from the time they would otherwise spend doing the productive work of the project.

Scope change is a necessary ingredient for the agile project manager to be successful.

Warning

Spend the time to understand the project, the customer, the business environment, the enterprise, and the resource pool before you make the decision as to the best SDPM strategy.