What you hear is commonly believed and shared. But it is not true since Kanabn is not a methodology , it is also not like a framework like Scrum. Its a collection of practices which makes your process visible and gives you signal to Limit your work in progress. one has to design its own Kanban system. The design of Kanban system starts with visualizing what you are doing right now mean it starts with your current process and it show areas to improve as you learn about the system.
What i see is when Scrum does not work people visualize their process using Kanban and say Kanban is good for us, but now we also have people who also visualize the work with Scrum and they call it ScrumBan :-)
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
I have hear this comparison before, once you understand the differences you will no longer compare them. It's like comparing two different types of car that are built for different purposes. They could be ultimately be use for a similar purpose or you could use them both along your journey.
Kanban is Japanese for “visual signal” or “card.” 1. Visualize Work 2. Limit Work in Process
3. Focus on Flow 4. Continuous Improvement
Scrum is an Agile framework for completing complex projects. (Product BackLog, Sprint Planning, Sprint Backlog)
In summary: Both Scrum and Kanban allow for large and complex tasks to be broken down and completed efficiently. Yet they are totally different in the philosophy and the practical applications (Scheduling, iteration, and cadence/Roles and responsibilities/Boards are Different).
...
1 reply by Pier Luigi Calabria
May 15, 2017 8:20 AM
Pier Luigi Calabria
...
Thank you for now
Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
Saket, thank you for the explanation. Saving Changes...
Pier Luigi CalabriaProject Manager| INFORM Institut für Operations Research und Management GmbH, Aachen, GermanyAachen, Germany
May 15, 2017 4:39 AM
Replying to Saket Bansal
...
What you hear is commonly believed and shared. But it is not true since Kanabn is not a methodology , it is also not like a framework like Scrum. Its a collection of practices which makes your process visible and gives you signal to Limit your work in progress. one has to design its own Kanban system. The design of Kanban system starts with visualizing what you are doing right now mean it starts with your current process and it show areas to improve as you learn about the system.
What i see is when Scrum does not work people visualize their process using Kanban and say Kanban is good for us, but now we also have people who also visualize the work with Scrum and they call it ScrumBan :-)
Pier Luigi CalabriaProject Manager| INFORM Institut für Operations Research und Management GmbH, Aachen, GermanyAachen, Germany
May 15, 2017 7:02 AM
Replying to George Lewis
...
I have hear this comparison before, once you understand the differences you will no longer compare them. It's like comparing two different types of car that are built for different purposes. They could be ultimately be use for a similar purpose or you could use them both along your journey.
Kanban is Japanese for “visual signal” or “card.” 1. Visualize Work 2. Limit Work in Process
3. Focus on Flow 4. Continuous Improvement
Scrum is an Agile framework for completing complex projects. (Product BackLog, Sprint Planning, Sprint Backlog)
In summary: Both Scrum and Kanban allow for large and complex tasks to be broken down and completed efficiently. Yet they are totally different in the philosophy and the practical applications (Scheduling, iteration, and cadence/Roles and responsibilities/Boards are Different).
Good explanation by Saket and George.. Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
I have hear this comparison before, once you understand the differences you will no longer compare them. It's like comparing two different types of car that are built for different purposes. They could be ultimately be use for a similar purpose or you could use them both along your journey.
Kanban is Japanese for “visual signal” or “card.” 1. Visualize Work 2. Limit Work in Process
3. Focus on Flow 4. Continuous Improvement
Scrum is an Agile framework for completing complex projects. (Product BackLog, Sprint Planning, Sprint Backlog)
In summary: Both Scrum and Kanban allow for large and complex tasks to be broken down and completed efficiently. Yet they are totally different in the philosophy and the practical applications (Scheduling, iteration, and cadence/Roles and responsibilities/Boards are Different). Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
I have hear this comparison before, once you understand the differences you will no longer compare them. It's like comparing two different types of car that are built for different purposes. They could be ultimately be use for a similar purpose or you could use them both along your journey.
Kanban is Japanese for “visual signal” or “card.” 1. Visualize Work 2. Limit Work in Process
3. Focus on Flow 4. Continuous Improvement
Scrum is an Agile framework for completing complex projects. (Product BackLog, Sprint Planning, Sprint Backlog)
In summary: Both Scrum and Kanban allow for large and complex tasks to be broken down and completed efficiently. Yet they are totally different in the philosophy and the practical applications (Scheduling, iteration, and cadence/Roles and responsibilities/Boards are Different). Saving Changes...
