Even if Scrum is the most popular Agile framework used in software development, it is not the only approach you can use. In this article, Mark Haynes discusses why you might consider Lean Kanban as a better approach for your organization. Author: Mark Haynes, https://dmarkhaynesconsulting.godaddysites.com/ What both Lean Kanban and Scrum have in common is that they are philosophy, not a methodology. The concept of a framework is an important distinction since it permits flexibility in its implementation. Scrum teams can be prone to less than optimal behaviors that Lean Kanban can help to re-adjust. Let’s think about what a few of these might be. Monster User Stories eating your Scrum board Teams fixated on ceremonies and not on process efficiencies Release dates dominate the Sprint, turning Cadences into a schedule The Retrospective becomes an ineffective change feedback loop What are the advantages for a team to go Lean Kanban? I think there are quite a few. After doing Scrum for a few years teams sometimes lose their way and become comfortable with less than optimal behaviors. You can address these using Scrum but do you need to change your framework to fix these problems? Notice these are all queuing problems and are often a question of the team’s behavior. Those are much harder to address using Scrum. Does a Lean Kanban philosophy offer advantages? Let’s explore what it means to be Lean Kanban. Lean Kanban Lean Kanban is not Scrum. They are complementary, but not compatible. One of the foundational principles of both Scrum and Lean Kanban is the Deming Improvement Cycle or PDSA (Plan-Do-Study-Act). Lean Kanban originates from the [...]
The post If You Are Done Scrumming, Try Some Kanban! first appeared on Scrum Agile Project Management Expert.↧