logging in or signing up Xebia Scrum India Meetup June 2011: Transitioning From Scrum To Kanban scrumindia 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: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 79 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: September 09, 2011 This Presentation is Public Favorites: 0 Presentation Description This brilliant Scrum to Kanban presentation was prepared by Rakesh Pandey. This was the first time we had the pleasure of having him at Scrum India Meetup at NCR. Hoping for many such insightful presentations! Comments Posting comment... Premium member Presentation Transcript Transitioning Scrum to Kanban: Presenter: RAKESH PANDEY CSM, PMP®, IIMC Transitioning Scrum to KanbanSlide 2: Scrum 3 Roles 4 Ceremonies 3 ArtifactsSlide 3: PO / BSA Scrum Master Team (Developers, Testers, etc.) Scrum RolesSlide 4: Ceremonies Sprint Planning Daily Scrum Sprint Review Sprint RetrospectiveSlide 5: Artifacts Product Backlog Sprint Backlog Burndown ChartDone: Code Completed Code Reviewed Documented Tested Pass in Integration Env When do we call something Done! For a functionality to be called Done it has to be Releasable DoneWhat Worked Well: What Worked Well Self Motivated Teams Teams Motivated to Take Decisions Team worked best when Challenged Quality Focus Do it right First Time Frequent Releases (every Month ) Team Recognitions / AwardsChallenges: Challenges Cross Team Code Reviews Management involvement for Results High Product Learning Curve for New Team MembersWhy KANBAN?: Hummm …. Everything was well. Then Why KANBAN? Bottlenecks: BottlenecksSlide 11: WORKSTREAMSAdoption from Scrum: Adoption from Scrum Roles Planning Meetings Daily Standup Team Discussion Product Backlog Team BacklogPrioritization Estimation : Prioritization Estimation Common GroundPrioritization : Common Product Backlog Business Group – Focus 5 Project Origin Project ROI PrioritizationSlide 15: Common Product Backlog Single Backlog for User Stories on all Products Teams worked from the same Product BacklogProject Origin: Project Origin: Business Group – Focus 5ROI - Benefit: ROI - BenefitEstimation: Planning Poker Size = Effort X Complexity X Uncertainty EstimationSlide 20: RAKESH PANDEY +91-9810112234 rpandeydelhi@yahoo.com Thank You!KANBAN: KANBAN Swim Lanes You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
Xebia Scrum India Meetup June 2011: Transitioning From Scrum To Kanban scrumindia 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: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 79 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: September 09, 2011 This Presentation is Public Favorites: 0 Presentation Description This brilliant Scrum to Kanban presentation was prepared by Rakesh Pandey. This was the first time we had the pleasure of having him at Scrum India Meetup at NCR. Hoping for many such insightful presentations! Comments Posting comment... Premium member Presentation Transcript Transitioning Scrum to Kanban: Presenter: RAKESH PANDEY CSM, PMP®, IIMC Transitioning Scrum to KanbanSlide 2: Scrum 3 Roles 4 Ceremonies 3 ArtifactsSlide 3: PO / BSA Scrum Master Team (Developers, Testers, etc.) Scrum RolesSlide 4: Ceremonies Sprint Planning Daily Scrum Sprint Review Sprint RetrospectiveSlide 5: Artifacts Product Backlog Sprint Backlog Burndown ChartDone: Code Completed Code Reviewed Documented Tested Pass in Integration Env When do we call something Done! For a functionality to be called Done it has to be Releasable DoneWhat Worked Well: What Worked Well Self Motivated Teams Teams Motivated to Take Decisions Team worked best when Challenged Quality Focus Do it right First Time Frequent Releases (every Month ) Team Recognitions / AwardsChallenges: Challenges Cross Team Code Reviews Management involvement for Results High Product Learning Curve for New Team MembersWhy KANBAN?: Hummm …. Everything was well. Then Why KANBAN? Bottlenecks: BottlenecksSlide 11: WORKSTREAMSAdoption from Scrum: Adoption from Scrum Roles Planning Meetings Daily Standup Team Discussion Product Backlog Team BacklogPrioritization Estimation : Prioritization Estimation Common GroundPrioritization : Common Product Backlog Business Group – Focus 5 Project Origin Project ROI PrioritizationSlide 15: Common Product Backlog Single Backlog for User Stories on all Products Teams worked from the same Product BacklogProject Origin: Project Origin: Business Group – Focus 5ROI - Benefit: ROI - BenefitEstimation: Planning Poker Size = Effort X Complexity X Uncertainty EstimationSlide 20: RAKESH PANDEY +91-9810112234 rpandeydelhi@yahoo.com Thank You!KANBAN: KANBAN Swim Lanes