Yep, the article argues that "locking sprints is a terrible process" because you're either going over or under the mark set upfront. As if those are the only op

Yep, the article argues that "locking sprints is a terrible process" because you're either going over or under the mark set upfront. As if those are the only options. The idea of locking sprints was a reaction against the problem of going _sideways_ , i.e. "changing priorities without notice" and requests for unplanned work to be done "now" without any thought of the effects.