Agile – scrum +

Click here to load reader

  • date post

  • Category


  • view

  • download


Embed Size (px)

Transcript of Agile – scrum +

  • 1. Agile Scrum + Alon Lahav SVP engineering

2. Agile iterative and incremental development, whererequirements and solutions evolve throughcollaboration between self-organizing, cross-functional teams 3. Agile ManifestoIndividuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan 4. The Idea Focus on getting things done Accept that they may mistakes along the way The best way to find those mistakes is to stopthinking about the software at the theoreticallevel 5. ScrumScrum is an iterative and incremental agilesoftware development framework formanaging software projects and product orapplication development. 6. ScrumSprint 7. Scrum 8. The Board 9. Roles Product Owner - voice of the customer, writesthe user stories prioritizes them, and addsthem to the product backlog Development Team - self-organizing Scrum Master 10. Requirements Automated regression test Continues build Onsite product knowledge 11. product backlogs - Definition A prioritized list of requirements, or stories, or features. Things that the customerwants, described using the customersterminology (user stories). Owner - product owner Shared Excel document / Google doc 12. Backlog Item ID - auto-incremented number Name a short, descriptive name of the story Importance the product owners importance ratingfor this story (Any story that the product ownerbelieves has a remote possibility of being included inthe next sprint should have a unique importance level) Initial estimate the teams initial assessment of howmuch work is needed to implement this story (in mandays) Notes The user story or how to demo 13. Sprint Planning Meetings purpose - to give the team enoughinformation to be able to work in undisturbedpeace for a few weeks, and to give theproduct owner enough confidence to let themdo so. Outcome: A sprint goal A sprint backlog A defined sprint demo date 14. Sprint Planning Meeting - Participants The whole team The product owner Scrum Master 15. Sprint planning meeting agenda 30 mins - Product owner goes through sprint goaland summarizes product backlog. 90 mins - Team time-estimates, and breaks downitems as necessary. Product owner updatesimportance ratings as necessary. Items areclarified. 60 mins - Team selects stories to be included insprint. 60 mins starting breakdown of stories intotasks. 16. Defining the sprint length once you have decided what length youlike best, stick to it for an extendedperiod of time. 3 week sprints everyone knows that every 3 weeksthere is a release 17. Sprint Goal should be in business terms, not technicalterms. not already been achieved everybody in the company (not only top-levelmanagement) can knows what the company isdoing and why! 18. Sprit BacklogP1 2dP22d P33d P41d P57d P6 P7P81DP9 2dP10P11 19. Sprit Backlog A snapshot of stories from the productbacklog. A list of stories that the team willcommit to for this sprint The team decides how many stories to includein the sprint. 20. Sprint Planning meeting index cards with the stories and put them upon the wall (or a large table). Importance order For every sprint poetical story: Brake to tasks Estimate each task Summarize the tasks to the Initial estimate 21. Sprint Planning meeting 22. After Sprint Planning meeting index cards can be carried right off to theteam room and be used as a wall-basedtaskboard After the sprint planning meeting, the Scrummaster manually updates the Excel-basedproduct backlog 23. Sprint backlog 24. Daily Scrums start exactly on time standing up Up to 15 minutes update the taskboard during the daily scrum update time estimates 25. sprint demos why The team gets credit for their accomplishment Other people learn what your team is doing. attracts vital feedback forces the team to actually finish stuff andrelease it 26. sprint retrospectives 1 3 hours Participants: The product owner, the wholeteam, scrum master The Scrum master shows the sprint backlogand, with help from the team, summarizes thesprint. Important events and decisions Round table estimated vs. actual selected 5 process improvements to focus on 27. release planning Product owner defines a list of acceptancethresholds Time estimate the top X (or whatever) storiesin the product backlog Acceptance test 28. Acceptance test 29. The + in Scrum + Weekly progress report Penalty to Scrum meetings late-rs Dual code responsibility One Team!!! 30. Offshoring One Team!!! Video Based Daily Scrum meetings Sprint planning meetings? Share thoughts and ideas 31. Scrum Master