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 luqman

2.044 visualizações

Publicada em

Publicada em: Tecnologia, Negócios
  • Entre para ver os comentários

Scrum luqman

  1. 1. SCRUM<br />Mohammed Luqman Shareef<br />me@luqmanshareef.com<br />
  2. 2. Agenda<br />What is scrum?<br />Roles in scrum<br />Scrum artifacts<br />Scrum meetings<br />Advantages<br />Q & A<br />
  3. 3. What is Scrum?<br />Scrum is an agile approach to software development.<br />It is an iterative development. The project progresses in series of Sprints.<br />There is no team lead. Teams are self-organizing. Scrum Master is a coach for the team.<br />
  4. 4. Ham and Egg story<br />A chicken and a pig decide to start a restaurant. <br />Chicken says “Lets call it Ham and Eggs!" <br />Pig replies “No Thanks, You’d only be involved where as I’d be committed!"<br />
  5. 5. Roles in Scrum<br />Committed (Pigs)<br />Product Owner<br />Scrum Master<br />Team Member<br />Involved (Chickens)<br />Stakeholders (Users, Customers..)<br />Managers<br />
  6. 6. Roles in Scrum<br />Product Owner<br />Writes User stories.<br />Creates product backlog.<br />Prioritizes user stories.<br />Scrum Master<br />Is a team member and NOT a team lead.<br />Makes sure Scrum team lives by the values and practices of Scrum.<br />Facilitates Daily Standup and Sprint Review meetings.<br />Team<br />Responsible for delivering the product.<br />Typically made of 5-7 people.<br />
  7. 7. What is Sprint?<br />Sprint is a time-boxed iteration, typically 2-4 weeks.<br />Output is a shippable product (No matter how basic it is).<br />A release typically consists of multiple sprints.<br />Each Sprint starts with Sprint planning, having daily scrum meetings, ends with Sprint review followed by sprint retrospective.<br />
  8. 8. Scrum artifacts<br />Product Backlog<br />Sprint Backlog<br />Product burn down chart<br />Sprint burn down chart<br />Team Velocity<br />
  9. 9. Product backlog<br />Managed by product owner.<br />It is the list of all the features to be added to the product.<br />Contains user stories ( a short description of customer requirements).<br />User stories re-prioritized by product owner after each sprint.<br />
  10. 10. Scrum Meetings<br />Sprint Planning<br />Daily Standup<br />Sprint Review<br />Sprint Retrospective<br />Only pigs are allowed to speak, chicken are welcomed only to listen.<br />
  11. 11. Sprint Planning<br />Estimate the effort/Story points from the product backlog.<br />Planning Game / Poker<br />Each User story is divided into Engineering tasks<br />Every team member gets a deck of cards with numbers representing story points.<br />For each user story every one estimates and show the card with that number.<br />Discuss the discrepancies and finalize the story points.<br />Determine the Sprint goal.<br />Plan for the user stories for next sprint.<br />Out come is ‘Sprint Backlog’ (list of user stories to be completed).<br />Tasks are signed up by team members (Not assigned).<br />
  12. 12. Daily scrum meeting<br />Not more than 15 mins.<br />Standup<br />No problem solving<br />Same time and same location<br />3 Questions<br />What did you do yesterday?<br />What obstacles are in your way?<br />What will you do today?<br />
  13. 13. SPRINT review<br />Team presents the product that has bee built during the sprint to management, customer and product owner.<br />3 Questions<br />What was the Sprint goal?<br />What was committed from Product backlog?<br />What is completed?<br />Product owner checks against DONE criteria.<br />Executed from dev environment.<br />Stake holders comment/criticize on the developed functionality<br />Identify not completed and new functionality to be added to the product backlog<br />
  14. 14. SPRINT Retrospective<br />End of each sprint<br />Product owner, Scrum master and team are involved.<br />3 Questions<br />What went well (Continue doing this)<br />What didn’t go well (Stop doing this)<br />Improvement areas (Start doing this)<br />
  15. 15. Burn down charts<br />To track progress<br />Sprint burn down chart<br />Shows number of tasks left in the current sprint backlog.<br />Updated daily by scrum master and uploaded to a shared location (sharepoint).<br />Product burn down chart<br />Shows number of requirements left.<br />Requirements can be added/removed.<br />
  16. 16. Team Velocity<br />Team velocity = Number of story points burnt in a sprint.<br />If a team of 4 members complete 3 user stories with story points 5,5,8 story points respectively.<br />Team velocity = (5 + 5 + 8 ) / 4<br /> = 4.5 user stories per person in a sprint<br />
  17. 17. Advantages<br />Increased productivity.<br />Continuous development process improvement.<br />Team<br />Team gets focused. One common goal.<br />More accountability and responsibility.<br />Flat structure, No manager-sub ordinate relation.<br />Team work, No individual failure/success.<br />Stakeholders<br />Higher visibility.<br />Better evaluation.<br />
  18. 18. Questions?<br />
  19. 19. Thank you<br />www.luqmanshareef.com<br />