Is Kanban Agile Scrum? (Kanban In Agile - Kanban With Scrum) Constraints Are What Makes A Process One can relate tools by studying how many various instructions they provide. A prescriptive tool stands for "more instructions to regard", and an adaptive tool stands for “fewer instructions to regard". A 100% prescriptive tool dictates that you don't have to give any decisions, and the tool has got instructions and rules for everything. On the other hand, a 100% adaptive tool lets you and your team do whatever you want because there are no instructions or restrictions. It is very evident that both of these extremes are not practical in engineering and business. Agile processes are often referred to as lightweight processes, mainly because they are
relatively less prescriptive compared to other conventional software development frameworks. Keep in mind that the first and foremost principle of the Agile Manifesto favors individuals and interactions over processes and tools. Kanban and Scrum are highly adaptive processes. And yet, Kanban is more adaptive because Scrum dictates more limitations and instructions, thus it relatively less flexible than Kanban. As an example Scrum designates timeboxed development cycles (Sprints), whereas there are no timeboxed iterations in Kanban. The value of a tool or process comes from how it limits your options while it's still giving you sufficient opportunities to build with quality, speed, and creativity.
Compare Tools To Get Best Out Of Them, Not To Judge Them Similar to all other tools and processes, neither the Kanban framework nor the Scrum
46
