scrumban pechakucha

20
IMPLEMENTING SCRUMBAN - STORY SO FAR May 21 st ,2011- Scrum Bangalore “Pecha Kucha” Presentation By Nitin Ramrakhyani, Sr. Product Manager, Digite Inc.

Upload: nitin-ramrakhyani

Post on 11-May-2015

2.004 views

Category:

Technology


0 download

DESCRIPTION

Slides from my talk at Scrum Bangalore, May 21st,2011.

TRANSCRIPT

Page 1: Scrumban pechakucha

IMPLEMENTING SCRUMBAN- STORY SO FAR

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

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

Page 2: Scrumban pechakucha

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.

Page 3: Scrumban pechakucha

What we did earlier?

Page 4: Scrumban pechakucha

Challenges

Complex Requirements

High Impact Analysis

Increasing Defect rate

Increasing Competition

Page 5: Scrumban pechakucha

Enter Scrum

Img Src: Scrum Primer by Pete Deemer

Page 6: Scrumban pechakucha

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

Page 7: Scrumban pechakucha

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.

Page 8: Scrumban pechakucha

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

Page 9: Scrumban pechakucha

What next?

Page 10: Scrumban pechakucha

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. 

Page 11: Scrumban pechakucha

Kanban – Key Principles

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

flow Increase throughput

Page 12: Scrumban pechakucha

Kanban Introduction

Page 13: Scrumban pechakucha

Who doesn’t like cocktails?

Scrum + Kanban = Scrumban

Page 14: Scrumban pechakucha

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”

Page 15: Scrumban pechakucha

Visibility Was the Key

Page 16: Scrumban pechakucha

Late Scope Additions - Allowed

Page 17: Scrumban pechakucha

What we measure?

Page 18: Scrumban pechakucha

Benefits

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

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

Page 19: Scrumban pechakucha

Recommendation

Make your own Cocktails.….

Page 20: Scrumban pechakucha

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