After using Scrum for many years I am still a huge proponent of this revolutionary agile methodology. Because being agile is about always finding the best ways to deliver higher satisfaction through continuous improvements, we must be able to recognize when there is a better way or alternative when confronted with specific problems or environments. To be clear I don't suggest modifying Scrum, it works great as prescribed when followed diligently. What I propose is not using Scrum at all in certain situations and instead use Scrumban.
Scrumban is a software production model based on Scrum and Kanban, combining the best of both worlds and of course embracing Kaizen at all times. What I have always loved about Scrum is the use of a visual board for managing the work; in Scrumban the board becomes the central piece and it reaches exciting new levels in promoting interactions and teamwork.
The presentation below is the small deck I use to introduce Scrumban in one hour. It's a technique that must be used in the right circumstances. I continue to promote Scrum first for projects focused on new features to increase customer satisfaction, but when teams enter hardening phases in their product life-cycle or fall in complete maintenance mode, instead of letting Scrum lose it's shine, I prefer to introduce Scrumban.
In most large engagements to roll-out Scrum, we often need to educate the entire organization to become more agile. One approach that we use is creating improvement communities to engage people outside of the Scrum teams, as well as infuse the concept of continuous improvement in all areas of the organization. To manage these communities, we have found that using Scrum is too heavy in terms of ceremonies and artifacts, but also based on the people's availability within these communities. Using Scrumban is perfect for these groups as it breathes the same agile thought processes, but permits a better flow for getting the work done. As you discover more about Scrumban, you will truly appreciate the power of understanding flow and calibrating perfectly to achieve great results.
Scrumban is a software production model based on Scrum and Kanban, combining the best of both worlds and of course embracing Kaizen at all times. What I have always loved about Scrum is the use of a visual board for managing the work; in Scrumban the board becomes the central piece and it reaches exciting new levels in promoting interactions and teamwork.
The presentation below is the small deck I use to introduce Scrumban in one hour. It's a technique that must be used in the right circumstances. I continue to promote Scrum first for projects focused on new features to increase customer satisfaction, but when teams enter hardening phases in their product life-cycle or fall in complete maintenance mode, instead of letting Scrum lose it's shine, I prefer to introduce Scrumban.
Scrum vs. Scrumban
View more presentations from Dimitri Ponomareff
In most large engagements to roll-out Scrum, we often need to educate the entire organization to become more agile. One approach that we use is creating improvement communities to engage people outside of the Scrum teams, as well as infuse the concept of continuous improvement in all areas of the organization. To manage these communities, we have found that using Scrum is too heavy in terms of ceremonies and artifacts, but also based on the people's availability within these communities. Using Scrumban is perfect for these groups as it breathes the same agile thought processes, but permits a better flow for getting the work done. As you discover more about Scrumban, you will truly appreciate the power of understanding flow and calibrating perfectly to achieve great results.
  |
A special thank you to Corey Ladas who wrote this great book about Scrumban. He offers a very accessible way to learn and effectively use Scrumban. |