Scope creep is often regarded as a negative term by both customers and vendors. Should we, perhaps, embrace it instead?
In the initial stages of any development project, both the customer and the developer dedicate significant effort to locking down a definitive scope.
Both parties aim to extract maximum value and ensure the project is delivered with timely value.
The reality is that no one can ever be 100% certain that every possible feature has been accounted for, nor can they be sure that unnecessary costs haven't been added by over-scoping. This uncertainty leaves both parties with an uncomfortable, unbalanced concern.
Does this mean that fixed-scope projects should be abandoned entirely in favour of a time and materials billing? Or should organisations adopt a much more flexible approach to managing projects?
After all, even if all parameters are perfectly met with a locked-down scope, it is inevitable that new ideas or additional requirements will emerge during the project's development.
This evolution should be embraced by both the client and the developer to ensure that the final product continues to meet and exceed evolving business needs.
Ultimately, both the client and the developer need to adopt a more flexible approach to deliver greater success in project outcomes.
By: Dion Visagie
