Scrum
Download as PPTX, PDF
1 like96 views
Scrum is an agile project management framework that allows teams to deliver projects in the shortest time through self-organizing teams. It involves short sprints of work where requirements are captured in a product backlog and prioritized. Teams pull items from the backlog for each sprint and work through daily stand-up meetings, sprint planning, reviews, and retrospectives. The roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the cross-functional team.
Scrum
- 2. SCRUM It is a method of Agile It is a project management emphasis Allowing to deliver the project in shortest time Self organizing teams Self manages the team to determine the best way Requirements are gathered as items in a list of product backlog
- 3. WHY SHOULD WE USE SCRUM Faster time to market Manage changing priorities Enhance software quality Project visibility
- 5. SPRINT Scrum has a fundamental 30-day development cy called a Sprint It is preceded by., o pre-Sprint activities o post-Sprint activities
- 6. SprintInputs Tested Code Change No changes during the sprint Plan sprint durations around how long you can commit to keeping change out of the sprint
- 7. SCRUM FRAMEWORK Roles : Product Owner, Scrum Master, Team Ceremonies : Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting Artifacts : Product Backlog, Sprint Backlog, and Burn down Chart
- 8. Define the features of the product Decide on release date and content Be responsible for the profitability of the product (ROI Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results. Product Owner
- 9. Represents management to the project Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences SCRUM MASTER
- 10. Typically 5-10 people Cross-functional -QA, Programmers, UI Designers, etc. Members should be full-time -May be exceptions (e.g., System Admin, etc.) Teams are self-organizing -What to do if a team self-organizes someone off the team?? -Ideally, no titles but rarely a possibility Membership can change only between sprints SCRUM TEAM
- 11. SPRINT PLANNING MEETING Sprint Planning Meeting Product Backlog Team Capabilities Business Conditions Technology Current Product Sprint Backlog Sprint Goal
- 12. 1st Stage: -Creating Product Backlog -Determining the Sprint Goal. -Participants: Product Owner, Scrum Master, Scrum 2nd Stage: -Participants: Scrum Master, Scrum Team -Creating Sprint Backlog Parts of Sprint Planning Meeting
- 13. Requirements for a system, expressed as a prioritiz Backlog Items Is managed and owned by a Product Owner Spreadsheet (typically) Usually is created during the Sprint Planning Meetin Can be changed and re-prioritized before each PM Product Backlog
- 14. Scrum team takes the Sprint Goal and decides what tasks are necessary Team self-organizes around how theyll meet the Sp Manager doesnt assign tasks to individuals Managers dont make decisions for the team Sprint is created From Sprint Goal to Sprint Backlog
- 15. A subset of Product Backlog Items, which define the work for a Sprint Is created ONLY by Team members Each Item has its own status Should be updated every day Sprint Backlog
- 16. Advantages Completely developed and tested features in short iterations Simplicity of the process Clearly defined rules Increasing productivity Self-organizing Each team member carries a lot of responsibility Improved communication Combination with Extreme Programming
- 17. Disadvantages Undisciplined hacking (no written documen Violation of responsibility Current mainly carried by the inventors
- 18. THANK Q