Scrum is a framework for managing projects that uses sprints, daily stand-up meetings, and artifacts like a product backlog to facilitate collaboration and ensure work is progressing towards goals. Key roles include the product owner who prioritizes work, the scrum team who does the work, and a scrum master who facilitates the process. Each sprint is time-boxed, usually to two weeks, and results in a potentially shippable product increment that is reviewed at the end of the sprint. Meetings like planning and retrospectives help coordinate work and improve the process. The goals of scrum include accountability, ability to adapt to change, and focus on delivering value.

1. scrum methodology
Presented by Bunlong VAN
http://geekhmer.github.io

2. Content
• What is Scrum?
• What is a Sprint?
• Scrum Roles
• Scrum Artifacts
• Scrum Meetings
• Purposes of Using Scrum

3. What is Scrum?
• Task Management System
• Helps us to complete our work on time
• Helps with accountability for everyones work
• A framework for discussions and collaboration
• Make required work clear and understandable

4. What is a Sprint?
• A time box – usually 2 week long
• Has an agreed set of goals
• Creates a “potentially shippable product”

5. Scrum Roles
• Product Owner
• Scrum Development Team
• Scrum Master

6. What is the Product Owner?
• The person who prioritizes tasks
• Make final requirements decisions
• Has vision for project
• Responsible to stakeholder (ROI)

7. Scrum Development Team
• A group of people with different skills
• Works together to achieve sprint goals
• Demonstrate “potentially shippable product”
• Self-oranizing

8. Scrum Master
• A facilitator
• Creates happy, workable environment
• Facilitates communications
• Removes thins that stop people from doing
theirwork

9. Scrum Artifacts
• The things produced by doing Scrum
• Product Backlog
• Sprint Backlog
• Potentially shippable product

10. Scrum Meetings
• Sprint Planning Meeting
• Daily Scrum Meeting
• Sprint Review Meeting
• Sprint Retrospective Meeting
• Backlog Refinement Meeting

11. Sprint Planning Meeting
• At the beginning of every sprint
• Moves items from product to Sprint Backlog
• Create tasks to achieve goals of sprint

12. Daily Scrum Meeting
• 15 minutes everyday – same place & time
• Each person reports to the team:
– What they did yesterday
– What they will do today
– What is preventing them from doing their work
• May or may not involve product Owner

13. Sprint Review Meeting
• 2 hours at the end of the sprint
• Team demonstrates work
• Product Owner declares what is finished
• Stakeholder feedback

14. Sprint Retrospective Meeting
• At the end of the sprint after the Sprint Review
• Take about the process and not the product
– What went well
– What did not work
– What could be improved
– What they learned
• Give feedback to each other

15. Backlog Refinement Meeting
• Generally 2 days before next sprint
• Define Product Backlog items properly (INVEST)
• Make items that are to big smaller
• Make acceptance criteria clear
• Discuss priorities of items

16. Purposes of Scrum
• Make clear responsibilities and accountability
• Helps us to react and respond to change
• Helps us to focus on what is important
• Helps us to accomplish things
• Improves quality and productivity
• Helps us to be a learning organization
z