Scrumban pechakucha

IMPLEMENTING SCRUMBAN- STORY SO FAR

May 21st ,2011- Scrum Bangalore “Pecha Kucha” Presentation

By Nitin Ramrakhyani, Sr. Product Manager, Digite Inc.

Background Context

Digite Inc, valley based product company, pioneer in Web-based Collaborative Products/ Solutions for Geographically Distributed Teams

Over 75 customers/ 250,000 users in North America, Europe, Asia/ Pacific.

Two products, Quarterly releases 30+ dev team size, 5-8 QA, 1 PO,

distributed across three locations.

What we did earlier?

Challenges

Complex Requirements

High Impact Analysis

Increasing Defect rate

Increasing Competition

Enter Scrum

Img Src: Scrum Primer by Pete Deemer

How much we Scrummed?

Release Planning – Backlog Prioritization, estimation

Multiple iterations in each release Iteration demos Feature Teams – For better impact

analysis Early QA involvement Increased Automation, Daily builds Daily scrums Retrospectives

What Worked, for us ?

Iteration demos – Early feedback, to make early correction

Early involvement of QA Feature teams Retrospectives, allowing team to

reflect and make improvements. Lead to lower defect rate, better

quality….more happiness.

What didn’t work, for us?

Daily scrum Weekly Status Calls Still needed Usecases, stories couldn’t help. Interruptions threw off Iteration plans, often. Tough to do iteration planning multiple

times, gather all stakeholders. Backlog changes within a sprint not allowed

in scrum, but needed for business. Needed quicker defect-fix deployment,

hence Release(minor or Hotfix as we call) WITHIN Iterations

What next?

Enter Kanban

Derived from the combination of two Japanese words, kan ("visual") and ban ("card" or "board"), kanban roughly translates to sign board or signal board. 

Kanban – Key Principles

Visualize your Work Limit Work in Process (WIP) Remove bottlenecks and improve the

flow Increase throughput

Kanban Introduction

Who doesn’t like cocktails?

Scrum + Kanban = Scrumban

Shaken, not Stirred….Our mix

Scrum Release Planning – remained same at high level Iteration Planning and fixed iteration scope Daily Standup - within smaller teams Retrospectives Agile Engg practices – daily builds, test automation

etc. Kanban

Work Visualization ( different than Agile task boards) WIP Limits, to discourage multi-tasking Test as soon as “done” Dealing with bottlenecks asap Focus on smooth “flow”

Visibility Was the Key

Late Scope Additions - Allowed

What we measure?

Benefits

Better/ “Value” delivery Can make releases “Whenever(almost,

bug-fixes mainly) Much better visibility Happy customers/ users.

Recommendation

Make your own Cocktails.….

References

www.goodagile.com http://www.infoq.com/minibooks/kanbanscrum-mini

book www.limitedwipsociety.com Kanbandev - Yahoo group www.swift-kanban.com www.digite/swift/community