logging in or signing up SCRUMBAN At Digite nramrakhyani Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: Embed: Flash iPad Dynamic Copy Does not support media & animations Automatically changes to Flash or non-Flash embed WordPress Embed Customize Embed URL: Copy Thumbnail: Copy The presentation is successfully added In Your Favorites. Views: 257 Category: Science & Tech.. License: All Rights Reserved Like it (0) Dislike it (0) Added: June 08, 2011 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Implementing Scrumban - Story so far: Implementing Scrumban - Story so far May 21 st ,2011- Scrum Bangalore “ Pecha Kucha ” Presentation By Nitin Ramrakhyani, Sr. Product Manager, Digite Inc.Background Context: 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?: What we did earlier?Challenges: Challenges Complex Requirements High Impact Analysis Increasing Defect rate Increasing CompetitionEnter Scrum: Enter Scrum Img Src : Scrum Primer by Pete DeemerHow much we Scrummed?: 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 RetrospectivesWhat Worked, for us ?: 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?: 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 IterationsSlide 9: What next?Enter Kanban: 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: Kanban – Key Principles Visualize your Work Limit Work in Process (WIP) Remove bottlenecks and improve the flow Increase throughputKanban Introduction: Kanban IntroductionWho doesn’t like cocktails?: Who doesn’t like cocktails? Scrum + Kanban = ScrumbanShaken, not Stirred….Our mix: 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: Visibility Was the KeyLate Scope Additions - Allowed: Late Scope Additions - AllowedWhat we measure?: What we measure?Benefits: Benefits Better/ “Value” delivery Can make releases “Whenever(almost, bug-fixes mainly) Much better visibility Happy customers/ users. Recommendation: Recommendation Make your own Cocktails.….References: References www.goodagile.com http://www.infoq.com/minibooks/kanbanscrum-minibook www.limitedwipsociety.com Kanbandev - Yahoo group www.swift-kanban.com www.digite/swift/community You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.