Scrum is based on short iterations, also called sprints. Their duration is no more than 2-3 weeks. Before starting work, the team independently forms a list of features for the iteration, after which the sprint is launched. After it is finished, all the changes made are uploaded to production, and those that were not completed are transferred to the next iteration.
There is an unspoken rule that features created during a sprint must be completed by the end of the sprint in any case. Below is a comparison table of Agile methods Scrum and Kanban.
Difference between Scrum and Kanban
Let's consider Kanban using the loan database example of the place where it was created. There is a conveyor where parts for Nissan SUVs are produced. There is a robot that, according to the program, produces mirrors. Its software includes the ability to produce mirrors for the left and right doors, rear-view mirrors, and sun visors. The principle of the robot's operation is very simple: by pressing a button, the program changes and the products that are needed at the moment are produced.
When ordering a Nissan Murano in the maximum configuration in any city of our country, an order for the creation of mirrors specifically for your configuration has already been automatically sent to production. This is where the advantage of changing the priority at any time comes into play. In the shortest possible time, the robot can be rebuilt to produce other parts.
The main difference between Scrum and Kanban is the duration of iterations. In Scrum, their average length is about two weeks, while in Kanban, a programmer can change tasks daily, and sometimes several times a day. Accordingly, Kanban has more flexible capabilities, if by this we mean frequent updating of priorities in work. For example, yesterday you posted a new feature to production, and today information came that it does not work as planned, so people do not click the "Buy" button. After receiving complaints, the programmer successfully solves a new task out of turn, in the evening the new solution is already uploaded to production, accordingly, the conversion rates to payments increased by 12%. This can be considered a success.
The evaluation of tasks in Scrum is done in hours or Story points. It is impossible to form a sprint without an evaluation, since it is necessary to know whether it is realistic to complete all the tasks within two weeks. At the end of 14 days, there is valuable information at the output - how many Story points the team was able to do during the sprint. The group's productivity in one iteration is shown by the Velocity parameter. Using it, the Scrum manager can say where the team will be in two weeks.
In Kanban, estimation is not performed by default. This is decided individually by the group itself. The term "Team Velocity" does not exist in this approach, but only the average execution time is taken into account. It can be determined using a special "Cycle Tme" report, which is compiled for a specific task minus the start of work on it.
So, in Scrum, the goal is to finish the sprint, and in Kanban, the goal is to complete the tasks. If we think abstractly, then Scrum can be imagined as a bus that stops strictly at stops, where people leave it in groups, and Kanban is a small shuttle in which the passenger can ask the driver to stop where he needs.
Recommended articles on this topic:
32 methods of finding and attracting clients
Cross-marketing: 5 examples and 8 mistakes
Absolutely Free Internet Advertising: 19 Options