Click here to load reader

Agile deveopment-with-scrum

  • View

  • Download

Embed Size (px)

Text of Agile deveopment-with-scrum

  1. 1. AGILE DEVELOPMENT WITH SCRUM Gloria Stoilova Scrum Product Owner BA, GfK Sofia
  2. 2. OUTLINE What is Scrum? The Scrum Team Scrum Events Scrum Artifacts UX & Testing Organizational Impacts
  3. 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.
  4. 4. SCRUM FRAMEWORK Founded on empirical process control theory Intentionally incomplete Iterative & incremental Outwardly facing & transparent Requires a definition of done Adapts to changing requirements
  5. 5. THE SCRUM TEAM Product Owner Scrum Master Business owner StakeholdersScrum Team BADSO
  6. 6. PRODUCT OWNER Manages the Product Backlog and ensures business value of the Teams work Represents stakeholder interests to the team Plans product releases and maintains product roadmap ONE person, not a committee Ultimately responsible for products success
  7. 7. 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
  8. 8. 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. 10. 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
  11. 11. SPRINTS 24 Hours Expanded tasks Daily Scrum meeting Sprint Backlog Product Backlog Potentially shippable product increment 14 Days
  12. 12. 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?
  13. 13. 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
  14. 14. 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
  15. 15. 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. 17. Product Owner SCRUM Master 1st. Level Support
  18. 18. 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
  19. 19. PRODUCT BACKLOG Highest priority items have the most detail Detail on lower priority items deferred until its needed
  20. 20. 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
  21. 21. 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
  22. 22. USER EXPERIENCE & TESTING All explained in details Agile_Testing presentation
  23. 23. USER EXPERIENCE TASKS UX tasks happen slightly ahead of programming tasks UX expertise stays involved No big handoffs
  24. 24. 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
  26. 26. ORGANIZATIONAL IMPACTS Transitioning to Scrum isnt always easy. Traditional roles change. Cultural changes. Commitment to continuous improvement.
  27. 27. WHO USES SCRUM?
  28. 28. QUESTIONS?
  29. 29. THANK YOU!
  30. 30. RESOURCES - Scrum Alliance - All Things Product Owner - 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

Search related