O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Scrum Methodology

Introduction about Scrum project management, Benefits, Roles, Meetings, Artifacts and challenges facing organizations implementing Scrum

  • Seja o primeiro a comentar

Scrum Methodology

  1. 1. Platform Overview November13th,2016 Presentedby: MAbdelAziz
  2. 2. Agenda
  3. 3. “A holistic or “rugby” approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements” (1986) Hirotaka Takeuchi and Ikujiro Nonaka. HBR
  4. 4. Requirements Analysis Design Coding Integration Testing Deployment Waterfall Waterfall might be good if we assume perfect knowledge from the beginning and we make no mistakes along the way.
  5. 5. Vision Scrum Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint Details
  6. 6. Scrum main benefits
  7. 7. Product Owner • Setting the main objectives and vision • Focuses on the “What” • Sets and adjusts priorities of items • Reference point for requirements validation • Accepts or rejects an increment • Considers different stakeholders Scrum Dev Team • Cross functional self- managed team • Focuses on the “How” • Negotiates commitment with product owner • ~ 3 to 9 members • Collaborate to reach agreed commitments Scrum Master • NOT a project manager • Facilitates the process • Shields the team from external distractions • Track and enforce time boxes • Promoting self- organization within the team
  8. 8. Product Backlog  Customer-centric feature list  Visible to all stakeholders  Any stakeholder can add items  Constantly re-prioritized by the Product Owner  Items at top are more granular than items at bottom  Maintained during the Backlog Refinement Meeting Product Backlog Item (PBI)  Written in a Story form  Can include acceptance criteria  Effort is estimated by the team  Can broken down to a list of tasks to achieve definition of “done”
  9. 9. Sprint Backlog  Consists of committed PBIs negotiated between the team and the Product Owner during the Sprint Planning Meeting  Visible to the team  Referenced during the Daily Scrum Meeting  Each PBI is broken to a list of tasks that focus on the “How”  A task should require one day or less  Remaining effort is re- estimated daily (in hours)
  10. 10. Sprint Burndown Chart  Indicates the remaining efforts (hours) within the sprint  Updated daily by the Scrum team  It is NOT a management report
  11. 11. Release / Product Burndown Chart  Indicates the remaining efforts (Story points) for the entire project  Updated after each Scrum  Useful to adjust forecasts
  12. 12. Critical Products In Scrum, Product Increments should be fully developed and tested in a single Sprint; products that need large amounts of regression testing or safety testing for each release are less suited to short Sprints Global Teams In Scrum, team members should have close and ongoing interaction, ideally working together in the same space most of the time Resistance Scrum needs to be adopted by the entire company and the customers as well.
  13. 13. Thank you!

×