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.
Spikes <ul>Mateusz Srebrny < [email_address] > Agile Warsaw June 14, 2010 </ul>
Overview <ul><li>Introduction
Unknown technologies and research
Spikes in XP
Spikes in my team
Spikes in another team
Spikes in your teams? </li></ul>
Introduction <ul><li>Non-coding scrum master
Redesign and scaling-out of the server-side infrastructure of the biggest polish instant messenger (over 2M peak concurren...
3 years, a small team of developers
Scrum after half a year
R&D project </li></ul>
And you? <ul><li>How many of you work in an Agile way?
How many of you develop the code?
How many of you lead your teams?
How many of you heard of spikes? </li></ul>
Agile design ideals <ul><li>Architecture magically emerges
Daily face-to-face designing
No change-hampering documents
But...
Upcoming SlideShare
Loading in …5
×

AgileWarsaw: Spikes

2,162 views

Published on

How to deal with unknown technologies and research tasks in an Agile project.

From AgileWarsaw, June 14, 2010

Published in: Technology
  • Be the first to comment

AgileWarsaw: Spikes

  1. 1. Spikes <ul>Mateusz Srebrny < [email_address] > Agile Warsaw June 14, 2010 </ul>
  2. 2. Overview <ul><li>Introduction
  3. 3. Unknown technologies and research
  4. 4. Spikes in XP
  5. 5. Spikes in my team
  6. 6. Spikes in another team
  7. 7. Spikes in your teams? </li></ul>
  8. 8. Introduction <ul><li>Non-coding scrum master
  9. 9. Redesign and scaling-out of the server-side infrastructure of the biggest polish instant messenger (over 2M peak concurrent users)
  10. 10. 3 years, a small team of developers
  11. 11. Scrum after half a year
  12. 12. R&D project </li></ul>
  13. 13. And you? <ul><li>How many of you work in an Agile way?
  14. 14. How many of you develop the code?
  15. 15. How many of you lead your teams?
  16. 16. How many of you heard of spikes? </li></ul>
  17. 17. Agile design ideals <ul><li>Architecture magically emerges
  18. 18. Daily face-to-face designing
  19. 19. No change-hampering documents
  20. 20. But...
  21. 21. … life tends to get more complicated </li></ul>
  22. 22. Unknown technologies and research <ul><li>Sometimes you need: </li><ul><li>to choose between two new technologies
  23. 23. to learn something about the subject first
  24. 24. to do something extremely unique </li></ul><li>Problems: </li><ul><li>research takes a lot of time
  25. 25. the research time estimation?
  26. 26. the output of the research? </li></ul></ul>
  27. 27. Spikes and XP <ul><li>XP @ wikipedia: </li><ul><li>Development can also create spike solutions to analyse or solve the problem.
  28. 28. These solutions are used for estimation and discarded once everyone gets clear visualization of the problem. </li></ul></ul>
  29. 29. My spike understanding <ul><li>Put a time-box around research task
  30. 30. Specify the required output: </li><ul><li>Working prototype
  31. 31. Decision-making session
  32. 32. List of questions to be answered
  33. 33. Design sketch </li></ul></ul>
  34. 34. Spikes in my team <ul><li>Backlog items preplanned for two, three sprints
  35. 35. Three day-long two-people spikes per sprint
  36. 36. No backlog item for spikes
  37. 37. The output – team meeting with interested parties </li><ul><li>Product Owners
  38. 38. available domain experts
  39. 39. interfacing team members </li></ul></ul>
  40. 40. Spikes in my team – spike meetings <ul><li>Research details
  41. 41. Usually a couple of options for implementation </li><ul><li>Sometimes ready to implement
  42. 42. Sometimes needed some ad-hoc modifications
  43. 43. Sometimes needed another spike </li></ul><li>Never failed to deliver something of value </li></ul>
  44. 44. Spikes in my team – summary <ul><li>Never more than three spikes on a subject
  45. 45. Estimated within focus factor – the same amount of research work every sprint
  46. 46. The need to facilitate the spike meeting
  47. 47. Bonus value: </li><ul><li>Inclusion of less experienced in the research
  48. 48. People from other teams help with the quality...
  49. 49. … and spread the info about the interesting things going on within the team </li></ul></ul>
  50. 50. Spikes in my team – discussion <ul><li>What do you think? </li></ul>
  51. 51. Spikes in another team <ul><li>Research backlog item – 'X – analysis'
  52. 52. The research tasks: </li><ul><li>Check up technologies Y, Z
  53. 53. Discuss with relevant people A, B
  54. 54. Produce a proof of concept </li></ul><li>Estimation just like with other backlog items </li></ul>
  55. 55. Spikes in another team - meeting <ul><li>After the research tasks were completed – a meeting of all involved developers
  56. 56. Meeting goal: </li><ul><li>Break-up the researched feature into development tasks </li></ul><li>The development tasks presented during a sprint planning session
  57. 57. The time for this meeting included in the sprint time consumption estimates </li></ul>
  58. 58. Spikes in another team - discussion <ul><li>What do you think? </li></ul>
  59. 59. Research outside the sprint <ul><li>There was some research done without spikes </li><ul><li>By a new team member
  60. 60. In a holiday season
  61. 61. Analysis before the actual project start </li></ul></ul>
  62. 62. My spike understanding <ul><li>Put a time-box around research task
  63. 63. Specify the required output: </li><ul><li>Working prototype
  64. 64. Decision-making session
  65. 65. List of questions to be answered
  66. 66. Design sketch </li></ul></ul>
  67. 67. Reference <ul><li>http://en.wikipedia.org/wiki/Extreme_programming_practices
  68. 68. http://www.extremeprogramming.org/rules/spike.html
  69. 69. http://blog.agilebuddy.com/2009/11/what-is-a-spike-in-scrum.html
  70. 70. More discussion? </li></ul>
  71. 71. :) <ul><li>Thank you.
  72. 72. Let the informal session start. </li></ul>
  73. 73. Agile Manifesto <ul><li>Individuals and interactions over processes and tools
  74. 74. Working software over comprehensive documentation
  75. 75. Customer collaboration over contract negotiation
  76. 76. Responding to change over following a plan
  77. 77. That is,
  78. 78. while there is value in the items on the right,
  79. 79. we value the items on the left more. </li></ul>

×