Kanban was invented at Toyota in the &#x27;40s and &#x27;50s: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Kanban" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Kanban</a><p>Depending on the scale you&#x27;re operating at, it&#x27;s easy to see this as a waterfall methodology. There are lots of different words to describe organizing work, but what&#x27;s important is that the methodology remains consistent enough that the team understands it.<p>I think of time-boxed sprints as great for training. Humans aren&#x27;t going to get better at estimating how long it takes to complete complex engineering tasks. But teams that work together over a long enough period of time can plan ahead better. (For example, time-boxed sprints would suggest that everyone has to take vacations at the same time for Scrum to be effective.) There are plenty of ways to deal with the fact that humans are asynchronous. I particularly liked this author&#x27;s focus on team morale as a major factor.