If you ask different parts of your company if Scrum or Kanban is better, you'll get WILDLY different answers from different parts of the business. The CEO has v

If you ask different parts of your company if Scrum or Kanban is better, you'll get WILDLY different answers from different parts of the business. The CEO has very different needs and wants than the on-the-ground code monkey. We have to take all of that into account before saying we "don't need" Scrum. Yes, okay, you don't NEED scrum, but maybe it's the best tool for the job, given the collective requirements of the business. Judging by the perspective shared in this article, I'd say it's coming from a Team Lead / Lead Programmer role at a small company, where Kanban works great. Once you grow beyond a certain size, almost everyone switches to Scrum. Why? Because it reduces friction with other parts of the business, which want - nay - NEED to slice time up into manageable, trackable chunks. And this goes all the way to the CEO and investors. You may not like it, but it's a very real constraint on your choice here.