[et_pb_section fb_built=”1″ _builder_version=”4.4.1″ background_color=”#fbfcfd” global_module=”1099″][et_pb_row column_structure=”1_2,1_2″ disabled_on=”on|on|off” _builder_version=”4.5.6″][et_pb_column type=”1_2″ _builder_version=”4.4.1″][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2020\/01\/Merle-black-and-white-round-less-shiny-1.png” _builder_version=”4.4.1″ custom_margin=”-5%|||25%|false|false” custom_css_main_element=”-webkit-clip-path: circle(50% at 50% 50%);||clip-path: circle(50% at 50% 50%);||width: 75px;||height: 75px;”][\/et_pb_image][\/et_pb_column][et_pb_column type=”1_2″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.5.6″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.8)” custom_margin=”-3%|||-60%|false|false”]<\/p>\n
Merle Randlepp<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=”4.5.6″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.44)” custom_margin=”-5%|||-60%|false|false”]<\/p>\n
Agile Coach<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row disabled_on=”off|off|on” _builder_version=”4.4.1″][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2020\/01\/Merle-black-and-white-round-less-shiny-1.png” align=”center” _builder_version=”4.4.1″ custom_margin=”||||true|false” custom_css_main_element=”-webkit-clip-path: circle(50% at 50% 50%);||clip-path: circle(50% at 50% 50%);||width: 75px;||height: 75px;”][\/et_pb_image][et_pb_text _builder_version=”4.4.1″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.8)” text_orientation=”center” custom_margin=”-3%||||false|false”]<\/p>\n
Merle Randlepp<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=”4.4.1″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.44)” text_orientation=”center” custom_margin=”-3%||||false|false”]<\/p>\n
Agile Coach<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.4.1″][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_post_title author=”off” comments=”off” featured_image=”off” _builder_version=”4.4.1″ title_font=”Source Sans Pro|700|||||||” title_text_align=”center” title_text_color=”rgba(0,0,0,0.8)” title_font_size=”47px” text_orientation=”center” title_font_size_tablet=”40px” title_font_size_phone=”35px” title_font_size_last_edited=”on|desktop”][\/et_pb_post_title][et_pb_text _builder_version=”4.7.4″ _module_preset=”default” text_font=”Source Sans Pro||||||||” text_font_size=”15px” text_line_height=”1em” text_orientation=”right” custom_margin=”|||10%|false|false”]
There are many different agile methodologies – Scrum, Kanban, XP (Extreme Programming), Lean, Crystal, FDD (Feature Driven Development), mutual hybrids, etc. [\/et_pb_text][et_pb_text _builder_version=”4.9.0″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ link_font_size_tablet=”” link_font_size_phone=”” link_font_size_last_edited=”on|desktop”]<\/p>\n 1990. In the 1990s, Dr. Jeff Sutherland and Ken Schwaber began to combine object-oriented programming with Japanese product development methods. The name “Scrum<\/strong>” comes from the rugby sports game and means players gathering in a circle, putting their heads together, and quickly discussing the game plan. Kanban’s roots go back to the 1940s when Toyota was developing products, and it became more widespread a decade later than Scrum, after the method was adapted for development by David Anderson. The name “Kanban<\/strong>” means “visual sign” in Japanese, which denoted the use of a visual job tracking board in the automotive industry. <\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.0″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ link_font_size_tablet=”” link_font_size_phone=”” link_font_size_last_edited=”on|desktop”]<\/p>\n The main difference between Scrum and Kanban is the length of the development cycle – Scrum<\/strong> is about working in 2-week (1-4 week) cycles called sprints. A certain amount of work is taken into one sprint and the team’s goal is to complete the work by the end of the sprint. Scrum<\/strong> has a limit on how many jobs can fit into one sprint to ensure that all jobs are completed by the end of the sprint. [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2020\/07\/Scrum-Board-scaled.jpg” title_text=”Scrum-Board” _builder_version=”4.4.9″][\/et_pb_image][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2020\/07\/Kanban-Board-scaled.jpg” title_text=”Kanban-Board” _builder_version=”4.4.9″][\/et_pb_image][et_pb_text _builder_version=”4.9.0″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ link_font_size_tablet=”” link_font_size_phone=”” link_font_size_last_edited=”on|desktop”]<\/p>\n Scrum and Kanban boards can both contain columns of your choice, usually using the statuses “pending”, “in progress”, “testing” and “done”.<\/em><\/p>\n On the Scrum<\/strong> board, only one sprint work can be seen at a time, and the pending work (Backlog<\/em>) is in a separate view. The Scrum board belongs to one dedicated Scrum team at a time. In Scrum, the prioritization of tasks<\/strong> on the board is very important – the works with higher priority are located at the top. In Kanban, prioritization is not directly mandatory, but it is often used. <\/p>\n Scrum avoids modifying jobs within an ongoing sprint. New jobs can only be added to the next, pending sprint. Scrum releases to the production environment at the end of each sprint. Recently, however, the use of ad-hoc<\/em> releases has also become more common. Scrum has three clearly defined roles:<\/p>\n
The two most common methodologies are Scrum and Kanban: according to various studies, the share of Scrum use is over 50%, Kanban and various hybrids around 15%.
Kanban vs Scrum is definitely not in competition with each other<\/strong>, their principles are largely the same and they are also used as a hybrid (ScrumBan). The goal of both frameworks is the same – to help manufacture a product or provide a service as efficiently as possible and to the customer with the greatest value proposition. Both methodologies share agile principles and values.
The choice of a specific agile methodology depends on the specific situation and the needs of the organization.<\/p>\nHistory<\/h2>\n
Scrum began to spread more widely in the world in 2002 with the popularization of the Agile Manifesto<\/a> . <\/p>\n<\/ul>\n
Kanban vs Scrum: Key Differences<\/h2>\n
Workflow<\/h3>\n
The Kanban<\/strong> workflow is continuous and time-indefinite, with the team picking jobs from a constantly changing list of pending tasks as needed. <\/p>\nLimitations<\/h3>\n
Kanban<\/strong> has a limit on the number of tasks that can be worked on at the same time (WIP – Work In Progress<\/em>), which helps to check that there are not too few or too many tasks in the work.<\/p>\n<\/ul>\n
Plaques<\/h3>\n
On the Kanban<\/strong> board, the pending work in the first column is always present and visible.
The Scrum board is cleared at the end of each sprint and recreated at the next sprint, the Kanban board is permanent.<\/p>\n
The Kanban board can be shared between different teams or people as needed.<\/p>\nChanges<\/h3>\n
In Kanban, jobs can be changed at any time and as much as necessary.<\/p>\nReleases<\/h3>\n
In Kanban, delivery takes place on an ongoing basis, as part of a continuous process.<\/em> <\/p>\nRoles<\/h3>\n