Agile presentation

811 views
715 views

Published on

This keynote is made for my presentation about scrum. So much stuff is taken From Yahoo Scrum Training given by GC and Antonio of MEME team

Published in: Technology, Sports
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
811
On SlideShare
0
From Embeds
0
Number of Embeds
66
Actions
Shares
0
Downloads
39
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Agile presentation

    1. 1. AGILE
    2. 2. ADAPT FAST and ITERATE
    3. 3. WHAT IS SCRUM ?
    4. 4. • “Scrum is an agile framework for completing complex projects. Scrum originally was formalized for software development projects, but works well for any complex, innovative scope of work” - Scrum Alliance -• “Scrum is an iterative and incremental agile software development method for managing software projects and product or application development.” - Wikipedia -
    5. 5. 3 - roles - ceremonies - artifact
    6. 6. Roles
    7. 7. The Boss
    8. 8. Agile is about
    9. 9. Team ProductScrum master Owner
    10. 10. Product Owner• Worked in shared vision• Manage and prioritized backlog• Decide release dates and contents• Responsible for ROI, audience, etc• Interact with stakeholder and customer to define Product backlog• Adjust feature and prioritize every sprint a needed• Accept or reject work results during sprint review
    11. 11. Scrum master• Protect values and principles• Removes impedance• Keep team fully functional and productive• Enable cooperation• Shield the team from the “dark force”• Facilitate Integration• Improves dynamics to reveal problem• He/She does NOT allocate task
    12. 12. The Team
    13. 13. The Team• Typically 5-9 People• Cross functional : Programmer, tester, etc• Full time allocated• Self-organized• Rich communication• Responsible for quality• Estimates complexity• Commits to increments of deliverable Products
    14. 14. Pigs X Chickens
    15. 15. Artifacts
    16. 16. Product Backlog• The product requirements• Everything (idea, feature, epics)• Expressed in User Story• PO Keep it organized• Always prioritized and estimate• Maintained and visible
    17. 17. User story I as a <client> Wants <feature> Because <ROI>Acceptable Criteria
    18. 18. Sprint Backlog
    19. 19. Sprint Backlog• User stories selected by team• Will be executed in the next x days• Fully estimated• Prioritized• Divided in Daily task • Duration is < 1 day • if > 1 days = split in 2 or more task
    20. 20. Project BoardBurndown chart
    21. 21. Definition of Done• “DONE” or “NOT DONE”• Avoid the 90% syndrome• Code produced, commented, checked in and tested• Peer review• Continuous Integration
    22. 22. Ceremonies
    23. 23. Ceremonies• Sprint planning• Sprint review• Sprint retrospective• Daily Scrum
    24. 24. Sprint Planning• What are we going to build?• How are we going to build it?
    25. 25. Sprint Planning• Planning 1 • PO explains the scope • Team estimates complexity• Planning 2 • Team chooses the sprint backlog • Team writes task to each story
    26. 26. Estimation Game
    27. 27. Sprint Review• Team demo what was accomplished during the sprint• Each developer demo a story• Informal, no slides• Whole team participates• Anyone invited to participate but only (pigs talk)
    28. 28. Sprint Retrospective• What was cool?• What can we improve?• What the team can solve?• What the company need to solve?• Only PO, SM and Team
    29. 29. Daily Standup• What I did since last meeting?• What will I do until next meeting?• Any impedance?
    30. 30. The ZEN of Agile• Honesty• Commitment• Small Victories 1000x > 1 Big Victories

    ×