Founder, Trainer & Coach
Member since 2 years
When faced with some challenge we try various things and finally find one silver bullet. Further we make use of the same silver bullet by incorporating it as part of Process and make it a rule to follow.
SCRUM as a framework has originated in similar situations and become the silver bullet for avoiding the ills of waterfall method. Scrum is successful and now widely used within multiple organizations.
Since SCRUM is almost 20 years old and 20 years of usage must have generated enormous feedback for the framework itself. Maybe it’s time to look at those feedbacks and do a retrospective on the way we’re using SCRUM.
My experience with multiple scrum projects taught me that one of the biggest de-motivating factor of working with scrum sprints are their monotonous nature of work. The sprint cycles with sprint planning and retrospectives becomes too repetitive to keep up the initial momentum.
We use the word “Just for change” quiet often for our own well being and happiness. SCRUM Dev is the same “Just for change” development practices incorporated within sprints.
These sprints contain unplanned working to themed based working which breaks the monotonous cycle of work and help maintaining the team momentum. At the same time it also benefits the product and its quality.
We're living in the days of fusion where fusions have created extremely useful products. There are fusions like western music with Indian classical, Pizza with Indian dishes like Paneer etc to name a few.
Scrumban is also a fusion generated by combining the best practices of Scrum and Kanban. Scrum is an excellent framework for delivering the software by using iterative incremental way while kanban "Just in Time" technique enables us to handle on demand agility for frequently changing and dynamic working environments.
Scrum framework consists of artifacts and roles while kanban is a visual board which deals with Work in the form of Work in Progress limits. There are situations where our product development environment faces ever changing priority and requirements.
ScrumBan is an effort to combine the iterative development and role based responsibilities of Scrum along with capability to handle the adaptive dynamics of Kanban.
Scrumban can be used effectively for product development as well as for maintenance purposes. In scrumban we do a Release Planning but not sprint planning. Planning on Demand is the characteristics of Scrumban where based on the items on the Scrumban board we decide to do planning or product demonstrations.
Scrumban also imbibes some new concepts of release planning called Triage & feature freeze which greatly improves the product quality.