Shayke's SCRUM @alphageeks 6
Download as PPTX, PDF1 like754 views
The document discusses the implementation and benefits of Scrum, an agile process that enhances productivity by prioritizing delivery of business value and facilitating better communication and feedback. It outlines the roles within a Scrum team, the planning process for sprints, and identifies pain points in traditional project management approaches while recommending strategies for improvement. Key outcomes from adopting Scrum include improved product delivery times, quality, and overall team environment.
Shayke's SCRUM @alphageeks 6
- 1. Scrum In ActionShay Cohen11/5/2010
- 2. AgendaThe Pain PointsWhat is SCRUM ?Scrum FlowRolesPlanning a SprintPillars & PrincipalsThe ResultsFrom hell to HeavenRecommendation
- 3. Worked very similar way to waterfallTry define all at the beginningBreak the planFix and delay as we go alongMonths aheadEvery feature is P0Low productivity due to missing / changing requirementsLow visibility during planning stageLong release cycles – TTMWe establishing our RoB as we progressA lot of noise during the development – DCRs, Integrations, BugsPoor WLBThe Pain Points Areas for improvement:CommunicationSimplicityFeedbackCourage
- 4. SCRUM in 100 wordsScrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.It allows us to rapidly and repeatedly inspect actual working software.The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.Every 5w anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
- 5. Scrum Flow
- 6. RolesProduct OwnerPMSCRUM MastersTeam LeadersRepresent the stakeholders
- 7. Owner the Product backlog
- 8. Owner the Sprint backlog
- 9. Responsible for the prioritization process
- 10. Approve removal of items during running sprint
- 11. Protect the Team and keep them focused on the tasks in hand
- 12. Manage the daily SCRUM meetings
- 13. Update the dev task progressTeamsHas the responsibility to deliver the product
- 14. Planning a SprintProduct BacklogIteration BacklogUser StoriesUser StoriesTasks (hours)Commit!111Commit!Can’t Commit!
- 15. Planning a SprintProduct BacklogIteration BacklogUser StoriesUser StoriesTasks (hours)Commit!111Commit!?1Commit!
- 16. Sprint Vs. ReleaseSprintFixed durationPotentially deployableReleaseFixed contentContent of one or more SprintsDeployableRequires stabilization period and ZBB
- 17. Pillars & PrincipalsPlanning take place before the sprint beginWe only plan what we know (well defined)Each user story get unique priorityHigh priority items should be scheduled to the beginning of the sprintWe strive for HLD & STP before planningAll tests are automated (Unit, Component, E2E)No test – no feature (E2E)Sprint N-1Planning NSprint NDev/TestDev/TestDev/TestDev/TestQualitySprint N+1Dev/TestPlanning N+1Planning N+1
- 18. Pillars & PrincipalsLast week is for quality and planning – no “new” codeNo buffers – Every developer has a long tail of low priority user storyNew backlog items shall not be added to a running sprintIntegrations are planned for beginning* of SprintDeployments ? Integrations ? Live system support ?Sprint N-1Planning NSprint NDev/TestDev/TestDev/TestDev/TestQualitySprint N+1Dev/TestPlanning N+1Planning N+1
- 20. The Results I
- 21. The Results II
- 22. From hell to HeavenThe outcomeThe “right” feature are in, Nice-to-have / future are outBetter TTM Better QualityBetter transparencyLess status reports/emailsLess meetingsWell known & establish ROBDevelopers have clear and quiet work plan and environment Better WLB
- 23. RecommendationsOrganizationManagement buy-in / sponsorshipAll or nothing - PM/Test/DevDaily scrum, Scrum of Scrums, Daily war-room on quality weekQuality & AutomationTest automationSmoke Tests on submitNightly builds with BVTWeekly / bi-weekly FRS & Manual testsQuality weekQuality gatesState of mindTransparency & communication is the keyConstantly give/take feedbackCourage
Editor's Notes
- #9: Add animation and a “can’t commit”… Move a smaller up…