Translated from Português (Brazil) • View original Scrum, as it adapts to any type of project, is the most widely used framework worldwide in software management. In addition, it is an innovative model, which breaks with traditional forms of management, and is easy to understand. Kanban, on the other hand, is a workflow management method that helps teams better define, manage, and improve processes. This structure helps teams deliver work by visualizing goals, tasks, and progress, contributing to maximizing efficiency and continuously improving results. In this post, we will explain a little about these two agile methods and their benefits, etc! About Kanban As its name suggests, kanban is of Japanese origin and was born. This is an approach to knowledge work created around 2006. The first case emerged in a team from the company Corbis, which began to implement demand flow management practices to improve the efficiency of customer support. The implementation of the Kanban method is very simple, as it does not require structural changes in the company to introduce it. It is only necessary to install a board or software to manage the tasks to be performed by employees. After that, all the requirements are added to this board, with the complete specifications, order of priority, and delivery time. Once you have this board organized, your team will be responsible for managing the execution and delivery of the tasks to be done. With time and the help of software, it is possible to apply performance metrics to perform more accurate task planning. About Scrum Scrum is a structure within the agile methodology created to facilitate teamwork on slightly more complex projects. It promotes the agile methodology by completing work tasks in an iterative way to achieve an already defined goal. With this agile methodology, it is possible to stay focused on delivering value to your company in the shortest possible time. The main concept is to break down your project into smaller, simpler tasks, which we will label Sprints. A Sprint can be weekly or monthly, with start and end dates, with the activities that must be completed within the stipulated deadline. For a good scrum to be carried out, it needs to have the following bases: Collaboration; Value-based prioritization; Defined deadlines; Iterative development; Empirical process control and Self-organization. Differences between the methodologies The main difference between the two methods is the so-called "timebox" that is widely used in scrum, and is nothing more than the maximum time stipulated for each internal event to happen. Although the structures have different systems and approaches, both were designed to help teams achieve the same work goals as quickly and efficiently as possible. But the best part is that your company's teams can use Scrum and Kanban at the same time! When considering Kanban vs Scrum there will be similarities, but there are also many differences to consider as well.