4. Agile Manifesto
We are uncovering better ways of developing software by doing it and helping
others do it. Through this work we have come to value:
That is, while there is value in the items on the right, we value the items on the left more.
Individuals and interactions > processes and tools
Working software > comprehensive documentation
Customer collaboration > contract negotiation
Responding to change > following a plan
7. Scrum Roles
• Product Owner
• Scrum Master
• Scrum Team
Image taken from Ken Rubin’s webinar A Visually Rich Overview of the Scrum Framework
8. Scrum Roles
Product Owner Scrum Master Development Team
Member of scrum team Servant-Leader Professional who do the work
Decides what work need to be done Scrum Coach of the team Cross functional
Keep Product Backlog ordered Deep understanding of Scrum Framework Available for the project full time
Prioritize work based on value Help Product owner on how to create and
maintain the product backlog
Responsible for self organizing
Refine Product Backlog list Remove impediments to the team progress Helps other team members where
required
Is a single person supported by
others
Owner of the process Commits to work
Closest to the business side of the
project
Responsible of organizing scrum
ceremonies
Self Sufficient
Project the value of the product
9. Scrum Ceremonies
• Sprint Planning Meeting
• Daily Scrum Meeting
• Sprint Review/Demonstration Meeting
• Backlog Grooming – as per need
• Sprint Retrospection Meeting
12. What are self organizing team ?
• Self Sufficient
• Manage work efficiently
• Continuous Collaboration
• Constantly Improving
• Self Policing
• Continuous Improvements
• Highly Motivated
• Does not require Command and Control
• Pull the work themselves
• Trust and respect team members
• Committed