Geek Academy Batch 2 : Intro to Scrum

310 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
310
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • To understand upcoming work and break down to smaller item, help to see the big picture of product
  • To understand upcoming work and break down to smaller item, help to see the big picture of product
  • To understand upcoming work and break down to smaller item, help to see the big picture of product
  • To understand upcoming work and break down to smaller item, help to see the big picture of product
  • Geek Academy Batch 2 : Intro to Scrum

    1. 1. SCRUM 1st WEEK SAT, NOVEMBER 23, 2013 – SUN, NOVEMBER 24, 2013 GEEK ACADEMY Batch 2 2013
    2. 2. INSTRUCTOR TEAM KARAN Karan(Bomb) Sivarat Gosoft (thailand) bomb0069@gmail.com
    3. 3. THIS CLASS GET NOT
    4. 4. CLASS AGENDA SCRUM OVERVIEWS ROLES ARTIFACTS ACTIVITIES SPRINT BACKLOG REFINEMENT RETROSPECTIVE PLANNING & ESTIMATION DAILY REVIEWS DEFINITION OF DONE
    5. 5. GEEK ACADEMY 2013 SCRUM
    6. 6. WHAT IS SCRUM ? SPRINT 1 2 3 4 TIME 5 6
    7. 7. SCRUM OVERVIEWS
    8. 8. SCRUM OVERVIEWS • • • THREE(3) SCRUM ROLES SIX(6) ACTIVITYS THREE(3) ARTIFACTS
    9. 9. SCRUM ROLES Team
    10. 10. PRODUCT OWNER • • • • • Should have a vision for the product. Defines the features of the product, decides on release date and content. Is responsible for the profitability of the product (ROI). Prioritizes features according to market value. Can change features and priority every sprint.
    11. 11. SCRUM TEAM • • • • • Team • • • Self-organizing; Cross-functional with no roles; Seven plus or minus two; Responsible for committing to work; Authority to do whatever is needed to meet commitment; Open, collocated space; Resolution of conflicts; Working agreements:
    12. 12. SCRUM MASTER • Removing the barriers between development and the customer so the customer directly drives development; • • • Teaching the product owner how to maximize ROI and meet their objectives through Scrum; Improving the lives of the development team by facilitating creativity and empowerment; Improving the productivity of the development team in any way possible; and, Improving the engineering practices and tools so each increment of functionality is potentially shippable.
    13. 13. SCRUM ACTIVITIES
    14. 14. PRODUCT BACKLOG : PRIORITY HIGH PRIORITY FEATURE LOW PRIORITY
    15. 15. PRODUCT BACKLOG : SIZE HIGH PRIORITY LOW PRIORITY HIGH PRIORITY & FINE GRAIN LOW PRIORITY & COARSE GRAIN
    16. 16. PRODUCT BACKLOG : ESTIMATE 1 3 2 2 8 5 HIGH PRIORITY & FINE GRAIN LOW PRIORITY & COARSE GRAIN
    17. 17. SCRUM ACTIVITIES
    18. 18. SCRUM ACTIVITIES SPRINT PLANNING PART I SPRINT PLANNING PART II DAILY SCRUM BACKLOG REFINEMENT SPRINT REVIEWS SPRINT RETROSPECTIVE
    19. 19. SPRINT PLANNING PART I & II Sprint planning part 1 Sprint planning part 2 - Clarification on backlog item - Hours based sprint planning - Tentatively select backlog items for sprint - Commit to the items, get back to PO
    20. 20. SHIPPABLE PRODUCT
    21. 21. SHIPPABLE PRODUCT REQUIREMENT GATHERING DESIGN ANALYST ARCHITECTURE IMPLEMENTED REFACTORED MIGRATE SCRIPT BLA BLA BLA UNIT TEST DOCUMENT REVIEWS FUNCTIONAL TEST
    22. 22. DEFINITION OF DONE • • • • Over time Done should include everything needed before deployment. Team together with product owner defines what “done” means. Examples of “done” -> Design, coding, unit testing, integrated ,Static analysis, refactored, Acceptance tested, deployable Not done backlog items should not be reviewed
    23. 23. DAILY SCRUM • Three questions; • • • What have you done since last meeting? What will you do before next meeting? What is Impediments ? • Daily 15 minute status meeting; • No discussion. Discussion after the daily Scrum
    24. 24. BACKLOG REFINEMENT HIGH PRIORITY & FINE GRAIN 1 3 2 2 8 5 1 3 2 2 5 2 5 2 5 2 2 2 2 2 2 LOW PRIORITY & COARSE GRAIN ENOUGH FOR 1-2 Sprints
    25. 25. SCRUM ARTIFACTS Product Backlog Sprint Backlog Burndown
    26. 26. SCRUM BOARD
    27. 27. SPRINT REVIEWS • • • • Team presents “done” functionality and discusses with PO and stakeholders. Team cannot present functionality that is not “done” Get Product’s Feedback Product Owner prioritizes backlog accordingly
    28. 28. SPRINT RETROSPECTIVE • • Goal : Reflect and create actions for improvements Question • • • What went well during last sprint What could be improved during last spint Improvements needing action will be added to next sprint
    29. 29. SPRINT RETROSPECTIVE
    30. 30. SCRUM ?
    31. 31. SCRUM OF SCRUM http://www.scrumalliance.org/articles/46-advice-on-conducting-the-scrum-of-scrums-meeting
    32. 32. REFERENCES o http://www.scrumprimer.org/anime o http://frank.vanpuffelen.net/2010/09/color-coding-your-scrum-board.html o http://www.boost.co.nz/blog/wp-content/uploads/2012/04/scrum-board2-e1334284189527.jpg o The Scrum Primer v 2.0 o http://www.infoq.com/minibooks/Scrum_Primer
    33. 33. GEEK ACADEMY 2013 Q&A
    34. 34. GEEK ACADEMY 2013

    ×