At the beginning of Agile, there was a tendency to aim at “pure” Agile, following the Scrum rules by the book. Even if there might be still Scrum cargo cult implementations, many Agilists have realized that Agile is more about continuous improvement and value delivery in a specific context than staying stand-up in daily status meetings. In this article, Mark Haynes discusses the Scrumban approach that borrows tools from both Scrum and Lean Kanban. Author: Mark Haynes First, full disclosure. I don’t like hybrids. I think they usually implement the worst features possible. They create indecision. Without a set of guiding principles your actions, will tend to whipsaw back and forth, providing no clear direction. Picture the conversation. Oh yes, our group is a mixture of Waterfall and Scrum. Today we are Scrum but tomorrow we will be Waterfall. You see we are flexible. No, you’re confused. Pick one. What is Scrumban? This question is implementation-specific, so it begs the question of what are the key considerations when blending these two approaches? Is it just adding a Kanban board to an existing Scrum Team or is it aligning Scrum ceremonies with Lean Kanban? It depends on the needs of your team and their focus, but it goes deeper than that. Scrum is a light management framework, with short fixed-length sprints and a focus on team dynamics. Lean Kanban embraces the continuous flow of work through a queue and the elimination of waste, mostly in terms of excess inventory. Scrum is [...]
The post Hold my Beer: We Are Going Scrumban! first appeared on Scrum Agile Project Management Expert.↧