Managing scope creep
What is scope creep? Scope creep, also known as requirements or feature creep, is the in-flight addition of requirements, expanded goals, rework or changes post build, to previously agreed deliverables. The lack of control and threat is often due to the fact an impact assessment is not done or the impact does not trigger the formal change control process. So if these types of changes are too minor to require management by formal change processes, how is it they may have such an impact on a project outcome? Of course project delivery is about delivering fit-for-purpose outcomes which often requires going above and beyond the call of duty to achieve customer satisfaction. This flexibility is part of the domain we operate in, so it sounds completely logical to accommodate small or apparently zero impact changes as required. Point one is definitely true, but the second is a value based proposition. In slotting in a minor change by working after standard hours as an act of goodwill,