Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scrum101

4,534 views

Published on

An introduction to Agile and Scrum

Published in: Technology, Business
  • Be the first to comment

Scrum101

  1. 1. Scrum Being Agile
  2. 2. Sandy Mamoli
  3. 3. The Plan
  4. 4. • Agile: Why? • Scrum: The Ingredients • Scrum: The How-to • Questions
  5. 5. Ask Questions!
  6. 6. Who are?
  7. 7. Why Agile?
  8. 8. Do we have a problem? • 66% over budget • 50% over time • 42% of all requirements change
  9. 9. Predictability
  10. 10. Scare the crap out of them !!
  11. 11. Motivation • Time to market: 14 - 30 day cycles • Manage budget risk • Manage time risk • Improve quality
  12. 12. Benefits • 82% Increased Productivity • 77% Improved Quality • 78% Stakeholder satisfaction • 37% Improved Cost
  13. 13. Ingredients
  14. 14. • Iterative and incremental development • Working software • Small cross-functional teams • Embrace change • Short feedback loops • Priority by business value
  15. 15. Iterative and Incremental
  16. 16. Working software
  17. 17. Empowered teams
  18. 18. Cross-functional teams
  19. 19. Embrace change
  20. 20. Visibility Transparency Feedback
  21. 21. Priority by business value
  22. 22. Scrum: The How-To
  23. 23. Not a methodology
  24. 24. Not a panacea
  25. 25. Not the only way
  26. 26. Scrum
  27. 27. Courtesy: Gillian Clark
  28. 28. Scrum Teams
  29. 29. Product Owner
  30. 30. Scrum Master
  31. 31. The Team
  32. 32. Product Owner • Working on shared product vision • Gathering requirements • Prioritising requirements • Accepting the product at the end of each sprint • Managing the release plan • Manage ROI
  33. 33. Scrum Master • Shepherding the team • Working with the Product Owner • Removing Impediments • Keeping the process moving • Protecting the team • Ask the team!
  34. 34. The Team • Estimating size of requirements • Committing to increments of deliverable software • Managing the sprint (self-organising) • Delivering software • Tracking their own progress (with SM)
  35. 35. Questions?
  36. 36. The Product Backlog
  37. 37. Courtesy: Gillian Clark
  38. 38. When?
  39. 39. • Some requirements done at the initial planning stage • Some requirements are done later
  40. 40. Sprint 0
  41. 41. Requirements Trawling Completeness
  42. 42. What?
  43. 43. User stories/Features
  44. 44. Courtesy: Chris Spagnuolo
  45. 45. What is a user story? A concise, written description of a piece of functionality that will be valuable to a user (or owner) of the software.
  46. 46. “As a music lover I want to submit payment by VISA card so that I can purchase the album”
  47. 47. Written in business language
  48. 48. Example product backlog
  49. 49. Who?
  50. 50. • Product owner • Customer team • End users • Advice from the technical team • The developers or Scrum Master
  51. 51. Only the Product Owner can prioritise!
  52. 52. Questions?
  53. 53. Estimating/Sizing
  54. 54. Story Points vs. Ideal Man-Days
  55. 55. 13 8 5 3 1 ?
  56. 56. Estimates are made by the team
  57. 57. Planning Poker
  58. 58. Velocity
  59. 59. Spikes
  60. 60. Questions?
  61. 61. Sprint planning
  62. 62. Courtesy: Gillian Clark
  63. 63. What goes into a sprint?
  64. 64. Sprint planning meeting
  65. 65. 2 Parts • Select backlog and set goal (Product Owner, Team) • Plan and select sprint functionality (Team)
  66. 66. Part 1: Select backlog
  67. 67. How much?
  68. 68. Yesterday’s weather
  69. 69. Commitment based
  70. 70. Part 2: Plan functionality
  71. 71. Task breakdown
  72. 72. “As a music lover I want to submit payment by VISA card so that I can purchase the album” 1. Code the UI - 6 hrs 2. Code the middle tier - 8 hrs 3. Connect to gateway - 8 hrs 4. Create landing page - 2 hrs 5. Write unit tests - 4 hours 6. End to end testing - 2 hours
  73. 73. Done?
  74. 74. Done: Acceptance “As a music lover I want to submit payment by VISA card so that I can purchase the album” 1. I can purchase an album by VISA card 2. I cannot pay with a VISA card that’s expired 3. I cannot pay with a VISA card with a wrong number
  75. 75. Done: Quality • Designed • Implemented • Unit tested • Someone else has looked at the code • End 2 end tested
  76. 76. The Sprint
  77. 77. The War room
  78. 78. Courtesy: Gillian Clark
  79. 79. • What did I achieve yesterday? • What am I going to work on today? • Do I have any impediments?
  80. 80. Impediments
  81. 81. Impediment backlog
  82. 82. Track progress
  83. 83. Defects?
  84. 84. Questions?
  85. 85. The Sprint Demo
  86. 86. Courtesy: Gillian Clark
  87. 87. Potentially shippable
  88. 88. Potentially shippable != shippable
  89. 89. The Retrospective
  90. 90. Courtesy: Gillian Clark
  91. 91. Inspect & Adapt
  92. 92. • What worked well? • What didn’t work well? • Where can we improve?
  93. 93. Outcomes go to... • The product backlog • The impediment backlog • The ground rules
  94. 94. Go!
  95. 95. Do it by the book?
  96. 96. Still alive? sandy@sprog.co.nz

×