Deadlines and sprints are bad for you
I think the author misses what the purpose of deadlines is. They are contracts between organizations for when software will be available, which are used for other organizations to make informed decisions without needing very tight and constant communication. They&#x27;re analogous to SLAs in service-oriented designs.<p>In a moderately large (say, 500+ employee) organization, deadlines are essential to get anything done. Suppose, for example, you&#x27;re overhauling a billing system, making international tax calculations simpler. The finance team is making a hiring decision: they need to get tax stuff calculated before the end of the year; do they need to find consultants to help them with this, or is the software going to be ready in time?<p>If your answer to them is &quot;I can&#x27;t tell you, we just do stuff on the kanban board and don&#x27;t think about deadlines,&quot; they&#x27;re  
(1) going to be less than thrilled with you, decreasing trust, and (2) unable to make their decision effectively.<p>I don&#x27;t think &quot;there&#x27;s only &quot;stuff&quot; to be done&quot; is an adequate alternative to deadlines and sprints if it doesn&#x27;t address the reason organizations use those tools. They&#x27;re primarily tools for predictability and scaling outbound communication about progress; I think the author mistakenly believes they&#x27;re supposed to be motivational tools. They&#x27;re sometimes misused that way, for sure, but that&#x27;s not the whole picture.