Содержание
- 2. Основные понятия AGILE Scrum Methodology
- 3. Scrum – это гибкая методология, которая фокусируется на business value Позволяет быстро и последовательно предоставлять работающие
- 4. CHARACTERISTICS Self-organizing teams Product progresses in a series of month-long “sprints” Requirements are captured as items
- 5. THE AGILE MANIFESTO–A STATEMENT OF VALUES Source: www.agilemanifesto.org
- 6. PUTTING IT ALL TOGETHER
- 7. SPRINTS Scrum projects make progress in a series of “sprints” Typical duration is 2–4 weeks or
- 8. Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.
- 9. NO CHANGES DURING A SPRINT Plan sprint durations around how long you can commit to keeping
- 10. SCRUM FRAMEWORK
- 11. SCRUM FRAMEWORK Product backlog Sprint backlog Burndown charts Artifacts
- 12. PRODUCT OWNER Define the features of the product Decide on release date and content Be responsible
- 13. THE SCRUMMASTER Represents management to the project Responsible for enacting Scrum values and practices Removes impediments
- 14. THE TEAM Typically 5-9 people Cross-functional: Programmers, testers, user experience designers, etc. Members should be full-time
- 15. THE TEAM Teams are self-organizing Ideally, no titles but rarely a possibility Membership should change only
- 16. SCRUM FRAMEWORK
- 17. Sprint planning meeting Business conditions Team capacity Product backlog Technology Current product
- 18. SPRINT PLANNING Team selects items from the product backlog they can commit to completing Sprint backlog
- 19. THE DAILY SCRUM Parameters Daily 15-minutes Stand-up Not for problem solving Whole world is invited Only
- 20. EVERYONE ANSWERS 3 QUESTIONS These are not status for the ScrumMaster
- 21. THE SPRINT REVIEW Team presents what it accomplished during the sprint Typically takes the form of
- 22. SPRINT RETROSPECTIVE Periodically take a look at what is and is not working Typically 15–30 minutes
- 23. START / STOP / CONTINUE Whole team gathers and discusses what they’d like to: Start doing
- 24. SCRUM FRAMEWORK
- 25. PRODUCT BACKLOG The requirements A list of all desired work on the project Ideally expressed such
- 26. A SAMPLE PRODUCT BACKLOG
- 27. THE SPRINT GOAL A short statement of what the work will be focused on during the
- 28. MANAGING THE SPRINT BACKLOG Individuals sign up for work of their own choosing Work is never
- 29. MANAGING THE SPRINT BACKLOG Any team member can add, delete or change the sprint backlog Work
- 30. A SPRINT BACKLOG Tasks Code the user interface Code the middle tier Test the middle tier
- 31. A SPRINT BURNDOWN CHART Hours
- 32. Hours 40 30 20 10 0 Mon Tue Wed Thu Fri Tasks Code the user interface
- 33. SCALABILITY Typical individual team is 7 ± 2 people Scalability comes from teams of teams Factors
- 34. SCALING THROUGH THE SCRUM OF SCRUMS
- 36. Скачать презентацию