Scrum and Kanban are popular Agile project management methodologies, but their more significant application is real in product development.
Both Kanban and Scrum methodologies are based on the idea of the optimized operation and the creation of high quality and high-value products. Reference: Kanban vs. Scrum: What Are the Differences Between Scrum and Kanban, eduwiki.me, 2020
We are currently discussing the optimization and updating of the way of working in the various departments. I will try to explain to you very simply what are the differences in the two possible models between which we will choose the most suitable for our industry and activity:
Kanban – sets a maximum limit on the work that is done at a time, namely, for us this would reduce the struggle of everyone’s tasks, possible defects and would improve your productivity.
Kanban boards use maps and columns to help teams commit to the right amount of work for them.
It would be a disadvantage for us if we had to (as often happens) start a new product, as Kanban limits the number of tasks we can put in one column.
It would also be negative for us that the Kanban dashboard software limits the addition of more tasks.
What is Scrum
Scrum – The overall idea and focus is largely close to Kanban, but there are usually no limits to the exact number of tasks you can work on (making it more flexible). The amount is determined by the team working on the project.
Whether we work with Scrum or Kanban, you and your teams should check your productivity regularly.
In short: Scrum has sprints and roles (Scrum Master and Product Owner). Reference: What is the Scrum methodology? agileprogramming.org 2020
- There are no sprints or roles in Kanban.
- In both cases, the teams are self-organizing.
- The Kanban dashboard is used continuously throughout the product development lifecycle by simply changing the cards.
- In Scrum, at the end of each sprint, the board is cleaned and restarted. New tasks are added, which remain there until the end of the sprint.
- They are also often in columns and have a corresponding status.
Scrum or Kanban: which methodology to choose for our project
Whichever of the processes we choose, we will be able to plan better, improve our efficiency, save time and resources.
Please discuss internally which of the two methods would be more suitable for your team and answer me why. We will look at the answers and consider how best to proceed and which process to focus on.
Please let me know if you have any questions about my email to our teams.
Regarding the processes of updating our work, my personal opinion is that both would work great in different teams.
As it turns out, they are not mutually repulsive, but rather overlapping, and Scrum is a little more flexible (frameless) and innovative in my opinion. It would give more freedom, and I guess a better end product. My personal opinion is that it is good for each team to review them and decide who would be more suitable for their specific work. They have 5 workers to share their views with us and once we have the results we will be able to discuss what will be best for us and the company.
Why choose Scrum?
In my opinion, Scrum is a suitable system for innovative companies, with a certain equal approach to its staff, composed of high-level functional specialists, and/or in developing products specifically for the needs of the customer, which have no analog or need to be built from scratch. , most often of a technological type of narrow specialists in a limited period of time and a certain quality required in a changing environment, in need of constant adaptation to conventions. Reference: Scrum problems, causes of failure and mistakes, phron.org, 2019
For companies that have set in their organization as a leading value the communication between professionals, to achieve certain goals in specific systems for the execution of orders from customers is also a very adequate solution.
In my opinion, this approach would not be complete for organizations whose teams do not deal with projects, but with long-term activities involving non-functional specialists and low-level employees performing repetitive and uncreative tasks not directly aimed at the requirements of a particular client or implementation. of a unique project (manufacturing companies, shops, companies, companies in the service sector). With more authoritarian senior management with outdated understandings of behavior and attitudes towards staff, customers, procedures and products, I also do not think it will be easy to apply the method.
When not to use Scrum
Maintaining daily communication between professionals, especially those with a low level of soft skills or specific personality traits, without conflicts or creating a negative working atmosphere, due to constant inspections and maintaining a transparent environment on all problematic situations, is a difficult task. for every management. A very flexible and professional approach is required by the management to make the most of the staff’s abilities, to be properly motivated, without overloading or causing any form of dissatisfaction, but also by observing optimal time limits and resource (financial) constraints.