Scrumban pechakucha


Published on

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

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Scrumban pechakucha

  1. 1. Implementing Scrumban- Story so far<br />May 21st ,2011- Scrum Bangalore “PechaKucha” Presentation<br />By Nitin Ramrakhyani, Sr. Product Manager, Digite Inc.<br />
  2. 2. Background Context<br />Digite Inc, valley based product company, pioneer in Web-based Collaborative Products/ Solutions for Geographically Distributed Teams<br />Over 75 customers/ 250,000 users in North America, Europe, Asia/ Pacific.<br />Two products, Quarterly releases<br />30+ dev team size, 5-8 QA, 1 PO, distributed across three locations.<br />
  3. 3. What we did earlier?<br />
  4. 4. Challenges<br />High Impact Analysis<br />Increasing Defect rate<br />Increasing Competition<br />Complex Requirements<br />
  5. 5. Enter Scrum<br />ImgSrc: Scrum Primer by Pete Deemer<br />
  6. 6. How much we Scrummed?<br />Release Planning – Backlog Prioritization, estimation<br />Multiple iterations in each release<br />Iteration demos<br />Feature Teams – For better impact analysis<br />Early QA involvement<br />Increased Automation, Daily builds<br />Daily scrums<br />Retrospectives<br />
  7. 7. What Worked, for us ?<br />Iteration demos – Early feedback, to make early correction<br />Early involvement of QA<br />Feature teams<br />Retrospectives, allowing team to reflect and make improvements. <br />Lead to lower defect rate, better quality….more happiness. <br />
  8. 8. What didn’t work, for us?<br />Daily scrum  Weekly Status Calls<br />Still needed Usecases, stories couldn’t help.<br />Interruptions threw off Iteration plans, often.<br />Tough to do iteration planning multiple times, gather all stakeholders.<br />Backlog changes within a sprint not allowed in scrum, but needed for business.<br />Needed quicker defect-fix deployment, hence Release(minor or Hotfix as we call) WITHIN Iterations<br />
  9. 9. What next?<br />
  10. 10. Enter Kanban<br />Derived from the combination of two Japanese words, kan ("visual") and ban ("card" or "board"), kanban roughly translates to sign board or signal board. <br />
  11. 11. Kanban Introduction – Key Principles<br />Visualize your Work<br />Limit Work in Process (WIP)<br />Remove bottlenecks and improve the flow<br />Increase throughput<br />
  12. 12. Kanban Introduction<br />
  13. 13. Who doesn’t like cocktails?<br />Scrum + Kanban = Scrumban<br />
  14. 14. Shaken, not Stirred….Our mix<br />Scrum <br />Release Planning – remained same at high level<br />Iteration Planning and fixed iteration scope<br />Daily Standup - within smaller teams<br />Retrospectives<br />Agile Engg practices – daily builds, test automation etc.<br />Kanban<br />Work Visualization ( different than Agile task boards)<br />WIP Limits, to discourage multi-tasking<br />Test as soon as “done”<br />Dealing with bottlenecks asap<br />Focus on smooth “flow”<br />
  15. 15. Visibility Was the Key<br />
  16. 16. Late Scope Additions - Allowed<br />
  17. 17. What we measure?<br />
  18. 18. Benefits<br />Better/ “Value” delivery<br />Can make releases “Whenever(almost, bug-fixes mainly)<br />Much better visibility<br />Happy customers/ users. <br />
  19. 19. Recommendation<br />Make your own Cocktails(or Mocktails)….<br />
  20. 20. References<br /><br /><br /><br />Kanbandev - Yahoo group<br /><br />www.digite/swift/community<br />Thank You, Reach out to me anytime:- <br />@nitinr30 /nramrakhyani<br />@productician<br /> :<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.