Handling Scope Changes Print

  • workingdevelopersagencies, working, billing, guide, howto, solution, zillionkinghost, hosting
  • 0

When requirements change.

WHY IT MATTERS

Scope change is the most common cause of disputes and overruns.

WHAT CAUSES IT

You think of something new The requirement was unclear Something turns out to be harder than expected

WHAT TO AGREE IN ADVANCE

That changes are quoted separately before work begins How changes are requested and approved What happens to the timescale

THE PROCESS THAT WORKS

You request a change They quote the cost and time impact You approve or decline Work proceeds

WHY IT MUST BE WRITTEN

Verbal change requests are the origin of most disputes about final invoices.

WHAT TO AVOID

"While you are in there, could you also..."

That is a change request, however casually made.

WHAT A GOOD DEVELOPER DOES

Tells you when a request is outside scope, before doing it.

WHAT TO DO IF YOU CHANGE YOUR MIND FREQUENTLY

Accept that it costs money and time.

Or spend longer on the brief before starting.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot