Agile deveopment-with-scrum
•Télécharger en tant que PPTX, PDF•
0 j'aime•508 vues
How to implement Agile methodology in Software development
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à Agile deveopment-with-scrum
Similaire à Agile deveopment-with-scrum (20)
Dernier
Dernier (20)
Agile deveopment-with-scrum
- 1. AGILE DEVELOPMENT WITH SCRUM Gloria Stoilova Scrum Product Owner BA, GfK Sofia
- 2. OUTLINE What is Scrum? The Scrum Team Scrum Events Scrum Artifacts UX & Testing Organizational Impacts
- 3. WHAT IS SCRUM? Scrum is an iterative and incremental agile software development methodology for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project.
- 5. SCRUM FRAMEWORK Founded on empirical process control theory Intentionally incomplete Iterative & incremental Outwardly facing & transparent Requires a definition of “done” Adapts to changing requirements
- 7. PRODUCT OWNER Manages the Product Backlog and ensures business value of the Team’s work Represents stakeholder interests to the team Plans product releases and maintains product roadmap ONE person, not a committee Ultimately responsible for product’s success
- 8. SCRUM MASTER Serves as coach, fixer, and gatekeeper A leadership role rather than managerial Plans individual Sprints with Team members Facilitates all of the Scrum events Manages relationship between Product Owner and rest of team
- 9. THE DEVELOPMENT (SCRUM) TEAM Cross-functional group of 4 to 7 people Self-organizing & continuously improving Team determines how to transform Product Backlog into shippable functionality Accountability belongs to Team as a whole No domain-specific sub-teams
- 10. SCRUM EVENTS
- 11. SPRINTS Consistent duration throughout project Team composition and quality goals remain constant No changes made that affect Sprint Goal Scope can be clarified or re-negotiated as more is learned Risk is limited to cost of one sprint
- 13. SPRINT PLANNING MEETING Time-boxed meeting to determine work to be done in a Sprint First event of every Sprint Answers “What will be delivered in this Sprint?” Answers “How will the work be achieved?”
- 14. DAILY SCRUM (STAND UP) Daily 15 minute (max) meeting Each team member answers three questions: - What has been accomplished since last meeting? - What will be done before the next meeting? - What obstacles are in the way? NOT a status meeting Only Development Team can participate
- 15. SPRINT REVIEW (DEMO) Development Team demonstrates work done in the Sprint Product Owner determines what has been “Done” or not “Done” Results in a revised Product Backlog Informs planning for the next Sprint
- 16. SPRINT RETROSPECTIVE Final activity of every Sprint Team reflects on the Sprint in terms of people, relationships, process, and tools Identify what went well and where improvements are needed. Team plans how to implement improvements
- 17. SCRUM ARTIFACTS
- 19. PRODUCT BACKLOG Single source of requirements and changes to the product Ordered by unique priority Never complete Dynamic and changes as needed responding to changing business needs Anyone involved can contribute to it
- 20. PRODUCT BACKLOG Highest priority items have the most detail Detail on lower priority items deferred until it’s needed
- 21. SPRINT BACKLOG Set of Backlog items that the Team commits to delivering in the Sprint Serves as a real-time picture of how work is progressing Belongs solely to the Development Team
- 22. DEFINITION OF “DONE” A shared understanding of what it means when work is considered done Defined at the beginning of the project Applies globally to the project Might include things such as: - Unit & functional tests - Documentation
- 23. USER EXPERIENCE & TESTING All explained in details Agile_Testing presentation
- 24. USER EXPERIENCE TASKS UX tasks happen slightly ahead of programming tasks UX expertise stays involved No big handoffs
- 25. TESTING No distinct testing phase Features are tested as they are completed during the Sprint they are developed in. Either developers or dedicated Testers create Unitest
- 27. ORGANIZATIONAL IMPACTS Transitioning to Scrum isn’t always easy. Traditional roles change. Cultural changes. Commitment to continuous improvement.
- 29. QUESTIONS?
- 30. THANK YOU!
- 31. RESOURCES Scrum.org - http://www.scrum.org/ Scrum Alliance - http://www.scrumalliance.org/ All Things Product Owner - http://www.romanpichler.com/blog/ Agile Project Management with Scrum by Ken Schwaber Succeeding with Agile: Software Development Using Scrum by Mike Cohn A Practical Guide to Distributed Scrum by Elizabeth Woodward