Scrumban helping out Scrum
Step by step

An example of how Scrumban can be leveraged to help out the Scrum implementation.

Example : Scrumban Implementation Guide


Phase 1: Mapping the Workflow

  • The initial phase involves creating a visual representation of the entire workflow. This encompasses inputs, the steps involved in the process, tasks handled by external team members, and outputs.
  • The goal is to graphically represent the various tasks your team handles, such as user stories, bug fixes, estimates, and spontaneous customer requests.

Activities:

  • Activity 1: Charting the Workflow
  • Activity 2: Adopting Evolutionary Changes, Implementing WIP Limits, Transitioning from Push to Pull Systems
  • Activity 3: Teams Design Their Initial Effective Kanban Boards (Beyond Basic Columns of To Do, Doing, Done)


Phase 2: Tracking Performance

  • Begin to monitor team performance.


Phase 3: Metric Analysis and Application

  • Coaches and Scrum Masters should guide teams in collecting and interpreting fundamental metrics, including:
    • Work In Progress (WIP) Limits: Tracking ongoing tasks
    • Obstacles
    • Lead Time
    • Throughput

Activity:

  • Activity 1: Integrate these metrics into daily stand-ups for better team comprehension.


Phase 4: System Stabilization and Enhanced Focus

  • Prioritize stabilizing the system before making improvements. Set WIP limits to enhance focus.

Activities:

  • Activity 1: Identifying Stability in the System
  • Activity 2: Analyzing Visual Patterns from Boards and Metrics


Phase 5: Advancing Risk Management and Decision-Making

  • Scrum Masters can assist Product Owners in embedding a consistent notion of value in work descriptions to make more informed business decisions.
  • Consider how proposed tasks will increase or protect revenue, reduce or avoid costs.


Phase 6: Ongoing Enhancement

  • Teams should persistently pursue process betterment and refine their ability to pinpoint and prioritize the most impactful improvements.

  • Coaches and Scrum Masters should leverage retrospectives to introduce continuous improvement practices:

    1. Encouraging regular and systematic thinking
    2. Incorporating and applying team evaluation tools
    3. Recognizing and circumventing unsafe change patterns.