Agile – scrum +


Published on

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

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • traced back to 1957, In 1974, a paper by E. A. Edmonds introduced an adaptive software development process. Agile Manifesto 2001
  • In 1986, Hirotaka Takeuchi and IkujiroNonaka described a new approach to commercial product development that would increase speed and flexibility, based on case studies from manufacturing firms in the automotive, photocopier and printer industries
  • כולם מעורבים, בעמידה לא נרדמים, הכרטיסים מכילים את כל הפרטים מה-backlog
  • Agile – scrum +

    1. 1. Agile – Scrum + Alon Lahav SVP engineering
    2. 2. Agile iterative and incremental development, whererequirements and solutions evolve throughcollaboration between self-organizing, cross-functional teams
    3. 3. Agile ManifestoIndividuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan
    4. 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 stop thinking about the software at the theoretical level
    5. 5. ScrumScrum is an iterative and incremental agilesoftware development framework formanaging software projects and product orapplication development.
    6. 6. Scrum Sprint
    7. 7. Scrum
    8. 8. The Board
    9. 9. Roles• Product Owner - voice of the customer, writes the user stories prioritizes them, and adds them to the product backlog• Development Team - self-organizing• Scrum Master
    10. 10. Requirements• Automated regression test• Continues build• Onsite product knowledge
    11. 11. product backlogs - Definition• A prioritized list of requirements, or stories,• or features. Things that the customer wants, described using the customer’s terminology (user stories).• Owner - product owner• Shared Excel document / Google doc
    12. 12. Backlog Item• ID - auto-incremented number• Name – a short, descriptive name of the story• Importance – the product owner’s importance rating for this story (Any story that the product owner believes has a remote possibility of being included in the next sprint should have a unique importance level)• Initial estimate – the team’s initial assessment of how much work is needed to implement this story (in man days)• Notes• The user story or how to demo
    13. 13. Sprint Planning Meetings• purpose - to give the team enough information to be able to work in undisturbed peace for a few weeks, and to give the product owner enough confidence to let them do so.• Outcome: – A sprint goal – A sprint backlog – A defined sprint demo date
    14. 14. Sprint Planning Meeting - Participants• The whole team• The product owner• Scrum Master
    15. 15. Sprint planning meeting agenda• 30 mins - Product owner goes through sprint goal and summarizes product backlog.• 90 mins - Team time-estimates, and breaks down items as necessary. Product owner updates importance ratings as necessary. Items are clarified.• 60 mins - Team selects stories to be included in sprint.• 60 mins – starting breakdown of stories into tasks.
    16. 16. Defining the sprint length• once you have decided what length you like best, stick to it for an extended period of time.• 3 week sprints• everyone knows that every 3 weeks there is a release
    17. 17. Sprint Goal• should be in business terms, not technical terms.• not already been achieved• everybody in the company (not only top-level management) can knows what the company is doing – and why!
    18. 18. Sprit BacklogP1 2dP2 2d P3 3d P4 1d P5 7d P6 P7 P8 1D P9 2dP10P11
    19. 19. Sprit Backlog• A snapshot of stories from the product backlog. A list of stories that the team will commit to for this sprint• The team decides how many stories to include in the sprint.
    20. 20. Sprint Planning meeting• index cards with the stories and put them up on 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. 21. Sprint Planning meeting
    22. 22. After Sprint Planning meeting• index cards can be carried right off to the team room and be used as a wall-based taskboard• After the sprint planning meeting, the Scrum master manually updates the Excel-based product backlog
    23. 23. Sprint backlog
    24. 24. Daily Scrums• start exactly on time• standing up• Up to 15 minutes• update the taskboard during the daily scrum• update time estimates
    25. 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 and release it
    26. 26. sprint retrospectives• 1 – 3 hours• Participants: The product owner, the whole team, scrum master• The Scrum master shows the sprint backlog and, with help from the team, summarizes the sprint. Important events and decisions• Round table• estimated vs. actual• selected 5 process improvements to focus on
    27. 27. release planning• Product owner defines a list of acceptance thresholds• Time estimate the top X (or whatever) stories in the product backlog• Acceptance test
    28. 28. Acceptance test
    29. 29. The + in Scrum +• Weekly progress report• Penalty to Scrum meetings “late-rs”• Dual code responsibility• One Team!!!
    30. 30. Offshoring• One Team!!!• Video Based Daily Scrum meetings• Sprint planning meetings?• Share thoughts and ideas
    31. 31. Scrum Master