Scrum and Kanban are popular Agile methods of work that are often confused with project management methodologies.
In this article, we briefly but clearly explain what exactly Scrum and Kanban are and the differences between them.
The fact that you are interested and willing to implement Agile practices in the organization means that you have already reached a stage where you are aware of their need and readiness to put them into practice.
And that’s enough is a successful start in this endeavor. I will do my best to put the systems into practice, but I will need your support, as, in both methodologies, individuals in the team and the relationships between them play an important role. I want you to be open, to share, and not be afraid to fail.
What are Scrum and Kanban
First of all, I would like to clarify the two concepts – Scrum and Kanban. Reference: “Waterfall, Agile, Scrum and Kanban methodologies“, https://stc-montreal.org/waterfall-agile-scrum-and-kanban-methodologies/
They often go hand in hand. Both are frameworks designed to work on projects that allow flexibility and adaptability to ever-changing requirements, covering Agile’s values.
But at the same time, there are some differences that I will try to explain as briefly and clearly as possible.
Scrum has clearly defined roles
Scrum has clearly defined roles. The project is divided into smaller parts (sprints) lasting about two weeks.
At the beginning of each sprint, together with the teams and the Product owner, priorities are set and clear tasks are defined. The teams must have 100% understood the tasks they will work on. Reference: “Working on projects with Scrum and Kanban: which to choose from both“, https://eduwiki.me/projects-with-scrum-and-kanban-which-to-choose/
The work on the individual tasks is constantly inspected. Daily meetings are held to exchange information on who is working on what, how his work is going, are there any obstacles that hinder him, and how they can be removed (adaptation).
This problem-solving process is performed jointly by the developer, the master, and the product owner. At the end of each sprint, a recapitulation of the work done is made and the priorities and tasks for the next one are determined.
The benefits of the introduction of scrum are increased productivity, freedom of the team in terms of how to solve problems. Easy traceability and full transparency.
Kanban is a continuous production planning system
Kanban is a continuous production planning system. It works with an organic number of tasks that the teams work on. Completing one task means starting another. More on the topic: https://www.muzonet.com/
This results in a continuous stream of tasks (as opposed to a scrum where each sprint ends in about two weeks) until the project is completed. Here, the effectiveness must be constantly checked and changed if necessary.
Unlike Scrum, where it is not recommended to change priorities during the sprint itself, with Kanban they are allowed at any time.
At both Scrum and Kanban, teams are self-organizing with all the responsibilities that come with that self-organization.
The advantage of Kanban is that it works with a minimum number of tasks and does not allow scattering. This reduces the likelihood of defects and increases productivity accordingly.
With the right Scrum / Kanban hardening process, there is virtually nothing to lose. Their goal is to facilitate the work of all teams and improve communication between them, which will inevitably affect the productivity and time for project implementation. Reference: “Waterfall vs V-Model vs Scrum vs Kanban”, https://newia.info/waterfall-vs-v-model-vs-scrum-vs-kanban/
The only risk we need to be careful about is choosing an accurate and appropriate framework for the organization, which I will take care of after gathering the necessary information from the teams.
After choosing the right system for us, we will organize training for the teams, in which they will be acquainted in more detail with the essence of the chosen system, will be given specific guidelines and recommendations.
And from there you will have the freedom to organize in an optimal way for the team and everything is in your hands.
Scrum is the most appropriate methodology
After talking with all the teams and separately with the leaders of each of them, I concluded that Scrum is the most appropriate methodology for our organization. Our management is experienced enough and would easily master the system. More about Scrum: https://customessaysonline.net/
I recommend that we start work on its implementation and acquaint the teams with the basic Agile values. To this end, a series of training must be organized.
The orders and permits that I should receive from you for the smooth running of the process are the following:
For communication to proceed properly and easily, I will need to clearly define everyone’s roles. For this purpose, I will ask for joint work with HR teams, because the individuals in the individual teams must work together.
The convening of daily short meetings (daily) during sprints. These meetings should be mandatory for everyone, even if only as listeners.
Meetings at the end of each sprint between the teams and the product owner to discuss the work done, possible problems, prioritization, etc.
To have the freedom to resolve any obstacles or ambiguities regarding the work of the teams, I will need to be able to communicate if necessary with the product owner and senior management.
Depending on the future projects that will be assigned to the organization, I do not rule out the possibility at some stage to make a hybrid model between Scrum and Kanban or even work entirely on Kanban for a specific project, if its essence requires it.