Kanban methodology vs Scrum framework

Hello colleagues, I offer you two methods for organizing the work process related to the visualization of our tasks in a tabular form, which is available to all team members and their leaders so that we can all effectively monitor progress. on the implementation of our project.

There are two main approaches:

Kanban methodology

Kanban proposes to monitor all emerging tasks throughout the project, dividing them into a special kanban board, divided into three conditional columns for research tasks, ready-to-test tasks, and tasks that have been tested and are awaiting final approval.

Tasks will move through the columns depending on their status by your team leaders. You will have a limited number of tasks that you can track on the board, and each new task can be entered by the team leader only if an older one is completed. The board will stand all the time until the end of our project to demonstrate the overall progress and open tasks in progress.

A disadvantage of the approach would be the feeling of constantly unfinished tasks, but instead, you will all have a clear idea of ​​what needs to be completed for the whole project, and decisions can be made easily to reallocate people and resources to complete a difficult task. to be able to start a new one.

Scrum framework

Scrum offers a similar task distribution board according to their status, but it works in stages, not for the whole project. The beginning of each stage will be set on a special sprint planning meeting between the scrum master, team leaders, and team members, and the scrum board will include tasks only for this stage, not for future stages, and the end of the stage will be set only as all tasks for the stage are cleared, and we are ready for the next level in the work progress.

The number of tasks at a given stage will not be limited, it can be changed by the scrum master if you need to adapt to changes in the work.

The downside would be that some teams would complete their tasks faster than other teams because they have fewer or easier tasks for a given stage, and cannot start other tasks before the next stage, but the sense of completeness and clarity for the specific phase of the project we are currently in will be much more tangible, and there will again be an opportunity to reallocate resources in order to complete the phase.

Conclusion

In view of the current goals of the company and the existing organization, taking into account the mood of the teams and their needs, I propose to introduce a system for Scrum Organization with periodic boards at the stages of project completion, for greater clarity about the place in the process. the production of our team at any time.

Taking on the role of a scrum master will help leaders and team members to arrange their tasks in stages, monitor their implementation, and allocate their resources efficiently, respecting the time constraints. I would like to add that many clients are familiar with Scrum’s theory and appreciate its presence in their partners, and it would be good to promote to them that we use it in our organization.

And also many specialists in our professional environment would accept as an added bonus for the work environment the use of this system, and we would attract them more easily in the company. For the introduction of the new approach, please organize a first sprint meeting with the team leaders to discuss the introduction of the scrum board, the definition of the stages, and the distribution of tasks between them.

References

  • Kanban vs Scrum? What Are the Differences Between Scrum and Kanban? scrumtime.org
  • Kanban vs. Scrum: What Are the Differences Between Scrum and Kanban, eduwiki.me
  • Agile, Scrum and Waterfall project management, ossalumni.org
  • Scrum and Kanban methodologies, vbprojects.org
  • Kanban methodology vs Scrum framework, libraryofmu.org

Leave a comment

Your email address will not be published. Required fields are marked *