Scope creep

Most commonly associated with software development projects, the idea of scope creep (also known as feature creep) can apply to other non-software fields that simply involve requirements with deadlines!

A project may begin with a finite set of requirement upon which the vendor and client agree beforehand. However, as the vendor develops the project, the client adds or changes requirements for various reasons (e.g. changing tastes of the client, the vendor taking too long, etc.) This results in the project's exponential increase in complexity and, thus, completion time for the vendor.

What seems to the client to amount only to a "minor change" will accompany other "minor changes" over time, creating a burnout for the vendor.