First, a quick review of a key tenet of The Scrum Guide: Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.
Scrum mandates that the Sprint Backlog be transparent, but it provides limited guidance on how to accomplish this. Nor does it define how to achieve explicit transparency to the flow of work into the Product Backlog, from the Product Backlog into the Sprint Backlog, and whatever happens to the work after it makes it into a “Done” increment. This is where Kanban can help. By visualizing work in new ways, a Scrum Team can apply the set of practices laid out in this guide to more effectively optimize value delivery. These practices borrow from and build upon the principles of lean thinking, product development flow, and queuing theory.