I don't know which process you follow, but while sprints are created in collaboration, in mid/large organizations everything is supposed to be in-sync across departments (so you can align interdisciplinary tasks).
In most cases I've seen, Agile basically introduces an additional company-internal clock with tick-tocks for days and weeks.
To me the article correctly describes how agile is assumed to be somewhat abstracted from "real-world" time, but in reality it's just two other hands on the same clock with pressure and tasks still increasing close to "real-world" clock-events (launch-dates, exhibitions, customer-events,...)
In most cases I've seen, Agile basically introduces an additional company-internal clock with tick-tocks for days and weeks.
To me the article correctly describes how agile is assumed to be somewhat abstracted from "real-world" time, but in reality it's just two other hands on the same clock with pressure and tasks still increasing close to "real-world" clock-events (launch-dates, exhibitions, customer-events,...)