Project Management Process

2. Kanban Framework

• Developed by Toyota, means the board

• Management focus

• A visual workflow management method focused on continuous delivery, work-in-progress (WIP) limits, and flow efficiency. Originated from Lean Manufacturing (Toyota)

• Core Practices:

  • • Visualize the workflow (Kanban board: To Do → Doing → Done).

    • Limit Work in Progress (WIP).

    • Manage flow (optimize time from start to finish).

    • Make policies explicit.

    • Implement feedback loops (daily standups, metrics).

    • Improve collaboratively (based on data & experiments).

  • Kanban Vs Scrum:

    • It's Continuous flow instead of Fixed Sprints

    • No fixed roles instead of cross functional team

    • Controlled via WIP limits instead of sprint control

    • On-demand instead of release and sprint planning

    • Changes allowed anytime instead of change freezing during sprint

    • Lead time, Cycle time, Throughput instead of Velocity and burndown

When it suitable?

• With the Support team

• Frequent changes

• Unpredictable work

• Need for flexible delivery

So enterprises can adapt Kanban in support of SQUADs and mission-critical SQUADs.

3. Scrumban

• Mix between Scrum and Kanban

• Scrumban = Scrum structure + Kanban flexibility — Ideal for teams needing agility without losing predictability.

• Uses Scrum structure (optional sprints), with Kanban flow.

• May retain Scrum roles (PO, SM, Devs).

• Combines backlog grooming + Kanban pull.

• WIP Limits Used, but may be flexible.

• Meetings: Can keep Scrum ceremonies (daily, retro, review).

• Best For: 

  • • Core team that all SQUADs have dependencies on

    • Managed Product Support team, which should release batches regularly

    • Teams transitioning from Scrum to Kanban.