>> Preemption points are regular time intervals at which the team will review a task’s progress and decide whether they should cut scope, change their strategy, or drop the task and cut losses altogether.
That definition is too abstract for me. If there is no deadline, why would one cut scope or drop the task? Conversely, why do I need preemption points to decide to cut scope, change strategy or drop the task? Usually the realization/decision comes naturally during implementation, without needing artificial occasions at constant intervals.
>> Preemption points are regular time intervals at which the team will review a task’s progress and decide whether they should cut scope, change their strategy, or drop the task and cut losses altogether.