What is Scrumban ?
9.Scrumban's Artefacts
The definition of "artifact" in Agile frameworks typically refers to tools, documents, or certain key elements that provide value and support the team in implementing the framework effectively. In the context of Scrum, artifacts like the Product Backlog and Sprint Backlog are tangible items that capture and display information crucial for the development process.
In describing the artifacts of Scrumban, the traditional notion of an artifact is expanded to include elements integral to the functionality and philosophy of the Scrumban framework. This broader interpretation encompasses not just physical items or documents, but also key concepts and mechanisms that are central to the framework's operation:
Scrumban Board: The central artifact in Scrumban, it is an evolved form of the Scrum board, integrating Kanban's visualization principles. Unlike the Scrum board, the Scrumban board is a continuous representation of work progress and doesn’t reset after a sprint. It typically includes columns representing various stages of work, such as 'To Do,' 'In Progress,' and 'Done', and may also feature additional columns based on the team's workflow.
Work In Progress (WIP) Limits: While not a physical artifact, WIP limits are a crucial component of the Scrumban system. They are indicated on the Scrumban board for each stage of the workflow to control the amount of work undertaken at any given time, thereby optimizing flow and preventing overburdening the team.
Enhanced Backlog: In Scrumban, the product backlog is similar to Scrum’s but is managed more fluidly. It is continuously refined and prioritized based on current needs and capacity, aligning with Kanban's pull system. The backlog in Scrumban often includes a more dynamic prioritization mechanism, reflecting the framework's emphasis on adaptability.
Ready Queue: This is a unique element in Scrumban, acting as a buffer between the backlog and the work being currently undertaken. It represents work items that have been prioritized and are ready to be pulled into the workflow as soon as capacity becomes available.
Flow Metrics: While not a traditional artifact like a backlog or board, flow metrics are vital in Scrumban. They include measurements like cycle time and throughput, providing empirical data on the team's performance and the efficiency of their workflow. These metrics help in making informed decisions and continuous improvements.
These artifacts in Scrumban blend Scrum's structured approach with Kanban's emphasis on flow and visualization, creating a framework that is both flexible and focused on continuous improvement. They serve as tools to manage and visualize work, prioritize tasks effectively, and measure and enhance the team's workflow efficiency.
10. Scrumban's Product Delivery Approach
The process of product delivery in Scrumban adapts the incremental and iterative approach of Scrum, integrating it with Kanban's continuous flow principles: Continuous and Adaptive Planning: Unlike Scrum, where planning is confined to the start of each sprint, Scrumban adopts a more continuous and adaptive approach to planning. This framework aligns with the demand-driven nature of Kanban, allowing for frequent reassessment and reprioritization of work based on current needs and capacity.
​
Pull-Based Work System: In Scrumban, work is pulled into the process as capacity allows, rather than being pushed into fixed iterations. This approach ensures that the team is always working on the most valuable and highest-priority items, and it can adapt more readily to changes and new requirements.
Incremental Delivery with Flexible Iterations: While Scrumban maintains the incremental delivery model of Scrum, the iterations (or cycles) are more flexible. The focus is on continuously delivering small, valuable increments of the product, but without the strict time-boxed constraint of Scrum sprints.
Flow Optimization for Efficiency: The Kanban influence in Scrumban emphasizes optimizing the flow of work. By managing WIP limits and visualizing the workflow on the Scrumban board, teams can identify and address bottlenecks, leading to more efficient and streamlined delivery.
Focus on Minimal Marketable Features (MMF): Scrumban encourages teams to break down work into smaller, manageable pieces that can be quickly completed and delivered. These Minimal Marketable Features provide immediate value and are regularly deployed, enhancing the product incrementally.
Emphasis on Quality and Sustainability: Quality is a key focus in Scrumban, with teams ensuring that each increment meets the defined quality standards before it is considered complete. This emphasis on quality aligns with the sustainable pace of work advocated by Scrumban, avoiding burnout and maintaining high standards.
Responsive to Market and Customer Feedback: The delivery process in Scrumban is highly responsive to feedback. By incorporating feedback into the continuous planning and prioritization process, teams can swiftly adapt the product to better meet customer needs and market demands.
In summary, Scrumban's approach to product delivery is characterized by continuous, adaptive planning, pull-based work systems, flexible iterations, optimized workflow, a focus on delivering small and valuable increments, and responsiveness to feedback. This approach enables a more dynamic and efficient delivery process, ensuring that the product evolves effectively in response to changing requirements and stakeholder feedback.