Save 37% off PRO during our Black Friday Sale! »

Introduction to Scrum

24ef21e3175a6823ea7b5a718ed289da?s=47 andrkoel
October 26, 2011

Introduction to Scrum

Explains reasons for scrum and the basics of Scrum

24ef21e3175a6823ea7b5a718ed289da?s=128

andrkoel

October 26, 2011
Tweet

Transcript

  1. Introduction to Agile and Scrum Andrej Koelewijn @andrkoel andrej@koelewijn.net

  2. Introduction to Agile and Scrum First why...

  3. Introduction to Agile and Scrum First why... Then how

  4. Two types of projects...

  5. None
  6. None
  7. None
  8. None
  9. Manufacturing

  10. None
  11. Managing these requires a different approach

  12. Functionality is known, Time and resources can be predicted

  13. None
  14. None
  15. Do we know this is the right design?

  16. Do we know this is the right design? Do we

    know how to get the required performance?
  17. Do we know this is the right design? Do we

    know how to get the required performance? Do we know all our platforms work as expected?
  18. Do we know this is the right design? Do we

    know how to get the required performance? Do we know all our platforms work as expected? Do we really know what the end-user wants?
  19. Do we know this is the right design? Do we

    know how to get the required performance? Do we know all our platforms work as expected? Do we really know what the end-user wants? Is the useability good enough?
  20. Do we know this is the right design? Do we

    know how to get the required performance? Do we know all our platforms work as expected? Do we really know what the end-user wants? Is the useability good enough? Do we know what the competition will do?
  21. None
  22. With so many unknowns, you can't predict functionality, time and

    resources
  23. Better approach: Do as much as possible within fixed time

    and with fixed resources
  24. How do you make sure you can deliver... ?

  25. How do you make sure you... ?

  26. ? How do you achieve highest...

  27. Work on limited number of features at a time...

  28. None
  29. Whenever you run out of time or money,

  30. You have the most important features releasable...

  31. Limit Work in Progress

  32. None
  33. How do you maximize knowledge creation?

  34. How do you maximize knowledge creation? Trail and error is

    how you do it...
  35. None
  36. None
  37. None
  38. None
  39. The faster you can iterate through plan-do-check-act...

  40. The faster you can iterate through plan-do-check-act... The faster you

    learn
  41. None
  42. None
  43. None
  44. None
  45. None
  46. None
  47. How do you improve productivity?

  48. How do you improve productivity? By removing handovers and queues...

  49. None
  50. None
  51. None
  52. None
  53. None
  54. None
  55. Scrum Limit work in progress, order requiments, enable learning through

    feedback, increase productivity by using a single cross-functional team
  56. None
  57. Scrum : By Product Managers For Product Managers

  58. The product manager...

  59. The product manager... Is responsible for Translating Customer needs...

  60. The product manager... Is responsible for Translating Customer needs... Into

    successful products
  61. Product manager (owner) uses Scrum to manage interaction with Product

    development team
  62. The product owner translates user needs into product vision and

    requirements
  63. Team needs to be able to quickly estimate relative size

    of the requirments...
  64. Team continuously keeps track of productivity, So amount of work

    doable in an iteration can be estimated
  65. Team needs to keep track of progress in a sprint,

    Team needs to regularly release working software...
  66. Product owner can regularly test working software And use feedback

    to update list of requirements
  67. Example of 3 iterations...

  68. None
  69. None
  70. None
  71. None
  72. None
  73. None
  74. None
  75. None
  76. None
  77. None
  78. None
  79. None
  80. None
  81. None
  82. None
  83. None
  84. None
  85. None
  86. None
  87. None
  88. None
  89. None
  90. None
  91. None
  92. None
  93. None
  94. None
  95. None
  96. None
  97. None
  98. None
  99. None
  100. All team members participate during planning poker session...

  101. Taskboard to keep track of progress within one iteration

  102. None
  103. None
  104. None
  105. None
  106. None
  107. None
  108. None
  109. None
  110. None
  111. None
  112. None
  113. None
  114. None
  115. None
  116. None
  117. None
  118. None
  119. None
  120. None
  121. Introduction to Agile and Scrum Andrej Koelewijn @andrkoel andrej@koelewijn.net