Your SlideShare is downloading. ×
AgileWarsaw: Spikes
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

AgileWarsaw: Spikes

1,411
views

Published on

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

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

From AgileWarsaw, June 14, 2010

Published in: Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,411
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
12
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Mateusz srebrny - Dziekuje organizatorom Mam szerzyc nowe trendy – opowiem jak scrum zachowuje się na styku miedzy klientem a dostawca Przy czym nie bede robil ogolnego wstepu do scruma, zakladam, ze nazwe przynajmniej wszyscy znaja. Opowiem o paru elementach, samych w sobie godnych uwagi analogia ze princowym srodowiskiem klient-dostawca, ktora bede probowal naszkicowac, sprowadza sie wlasnie do lekkosci – scrum pozostawia wszystko komunikacji w ramach kliku technik czy konceptow, co w porownaniu z ponad 40toma procesami princa zaklada duzo mniejszy narzut organizacyjny I formalny
  • .(1) A wiec na poczatek opowiem troche o sobie, samym scrumie I zwiazku miedzy nami . Potem pokaze pare technik, artefaktow uzywanych w scrumie do komunikacji miedzy kliemtem a dostawca . Na koniec krotkie podsumowanie
  • (2) Informatyk, zarzadzanie od 3 lat . To co bede mowil oparte jest na moich doswiadczeniach z prowadzenia zespolu... projekt skomplikowany (historyczne zaszlosci, oraz skala 2M uzytkownikow) Skad pojawil sie Scrum? Otoz, gdy zaczynalismy, firma byla mloda, rok wczesniej przeszla z jednoosobowej w organizowanie wiekszej struktury Nie bylo za duzo kompetencji odnosnie zarzadzania IT, trzeba bylo eksperymentowac, dzialac intuicyjnie . Po pol roku uznalismy, ze to nie dziala tak sprawnie jak bysmy chcieli I zdecydowalismy sie siegnac do promowanego przez Google I Microsoft Scruma. . Nazwa pochodzi od wlasnie takiej formacji w rugby, analogia zespolu scrumowego I rugbowego
  • Transcript

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