Your SlideShare is downloading. ×
  • Like
Scrumban pechakucha
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Scrumban pechakucha


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

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

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Implementing Scrumban- Story so far
    May 21st ,2011- Scrum Bangalore “PechaKucha” Presentation
    By Nitin Ramrakhyani, Sr. Product Manager, Digite Inc.
  • 2. 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.
  • 3. What we did earlier?
  • 4. Challenges
    High Impact Analysis
    Increasing Defect rate
    Increasing Competition
    Complex Requirements
  • 5. Enter Scrum
    ImgSrc: Scrum Primer by Pete Deemer
  • 6. 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
  • 7. 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. 
  • 8. 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
  • 9. What next?
  • 10. 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. 
  • 11. Kanban Introduction – Key Principles
    Visualize your Work
    Limit Work in Process (WIP)
    Remove bottlenecks and improve the flow
    Increase throughput
  • 12. Kanban Introduction
  • 13. Who doesn’t like cocktails?
    Scrum + Kanban = Scrumban
  • 14. Shaken, not Stirred….Our mix
    Release Planning – remained same at high level
    Iteration Planning and fixed iteration scope
    Daily Standup - within smaller teams
    Agile Engg practices – daily builds, test automation etc.
    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”
  • 15. Visibility Was the Key
  • 16. Late Scope Additions - Allowed
  • 17. What we measure?
  • 18. Benefits
    Better/ “Value” delivery
    Can make releases “Whenever(almost, bug-fixes mainly)
    Much better visibility
    Happy customers/ users. 
  • 19. Recommendation
    Make your own Cocktails(or Mocktails)….
  • 20. References
    Kanbandev - Yahoo group
    Thank You, Reach out to me anytime:-
    @nitinr30 /nramrakhyani