Iterações: melhor sem elas?

515 visualizações

Publicada em

Presentation given in Agile Brazil 2012

Publicada em: Tecnologia
0 comentários
3 gostaram
Estatísticas
Notas
  • Seja o primeiro a comentar

Sem downloads
Visualizações
Visualizações totais
515
No SlideShare
0
A partir de incorporações
0
Número de incorporações
3
Ações
Compartilhamentos
0
Downloads
5
Comentários
0
Gostaram
3
Incorporações 0
Nenhuma incorporação

Nenhuma nota no slide
  • team working towards a go
  • even though sometimes we fight over trivial things
  • point out that there is absolutely no correlation between the two, one is a management/tracking approach, the other is a concept of quick feedback
  • let’s meet our team, most of the data shown is directly extracted from real scenarios
  • here Is the meat in our team, assume that the developers will always be pairing
  • these are potentially the other roles that will be involved in a project
  • but we won’t talk about them now
  • - show graph with historical velocity-- talk about how it tends to fluctuate to some extentthis is our team’s history
  • we hit the ground running, straight into a ongoing project, conveniently at a sprint planning meeting
  • - show backlog with some stories to be more graphical about the subject-- go through estimation-- highlight which stories will be picked as part of the next iteration (considering the historical velocity)
  • let’s not look at the whole backlog, let’s pick a decent sample, shall we?
  • time to estimate our stories, normal planning poker goes on
  • time to estimate
  • - show backlog with some stories to be more graphical about the subject-- go through estimation-- highlight which stories will be picked as part of the next iteration (considering the historical velocity)
  • the discussion takes place, which stories should we pick for the next iteration? mostly it involves taking “H” or not
  • then one of our members mentions XP
  • and focuses, conveniently, in courage
  • let’s pick 22 then : ), jokes aside… there is no right or wrong answer here
  • o quenóspodemosdizeré…
  • explain the steps:backlog is the sprint backlogin dev also considers automated testingqa means exploratory testing and validationlet’s skip ba stuff
  • here we have our board ready for the beginning of the iteration
  • on the stand up next day, our two pair have picked up A and B for work
  • two days later, on the standup, stories B, C and D are already dev complete and move to QA, our second pair picks E… “A” seems to be stuck
  • on the standup of day 4, A finally goes to QA, while B and C are done, F is picked up for development, we finally have our first points delivered, yay!
  • A is done, E goes to QA, G is picked up
  • - then a couple of our pairs are having a really inspired week-- by the end of the first week pretty much all the points are done... done DONE!- what happens now?- short term goals-- awesome to keep focus-- motivation-- what happens when they are met though?-- party \\o/
  • - then a couple of our pairs are having a really inspired week-- by the end of the first week pretty much all the points are done... done DONE!- what happens now?- short term goals-- awesome to keep focus-- motivation-- what happens when they are met though?-- party \\o/
  • - oh well, we pick more stories, I guess-- talking about human beings, do we really think that we would be as motivated to accomplish the extra set of stories as we werefor meeting the goal?-- going beyond expections is good, but people will tend to relax
  • - oh well, we pick more stories, anyways-- we probably won't go as swiftly through them (the goal has been met... it is only human)-- if we end up with some of them halfway through our pipe by iteration end, what happens?
  • - IMPORTANT:last day of iteration, let’s not pick another story
  • fizemos 22 pontos,nossamédiaé 20,temos 8 emprogresso…quantospontosvamosnoscomprometernapróximaiteração?
  • let’s take a look at the board again to refresh our memories
  • let’s go to the next planning then… we are going to go super fast through this iteration, bear with me
  • who would pick “P”? who would not? who would try to pick even more than P ?
  • let’s take a look at our board
  • IMPORTANT: story I was developed in one iteration and tested in the other, sprint is not doing so well, we realized we needed some crazy testing for story “I”digress a bit and talk how clear we are on our objective and how we are falling behind on meeting it
  • who thinks this was a disaster?
  • - show graph with historical velocity-- talk about how it tends to fluctuate to some extent
  • - show graph with historical velocity-- talk about how it tends to fluctuate to some extent
  • meta talk about analogies and metaphors… we can call it the giant wheel effect, some people might have different
  • there are those who like roller coasters better
  • myself, I’m a see-saw-man… it is funny how sometimes one iteration going bad can help the other go better and vice-versa.taking technical debt can speed up things, but might leave more need for refactoring on the next iterationspending time on refactoring and ground work can hurt the current iteration velocity, but can help the next one
  • so, let’s talk some about iterations
  • every two week we have retro, we get together, we force a showcase
  • we are focused on delivering these points
  • team is focused on the small chunk of work ahead
  • team (and even stakeholders) tend to forget about the big picture, people might rush to deliver stories before the end of an iteration
  • life is a continuous flow… we are not time boxed creatures, they might be useful as metrics but not as constraintsthe next quotes are taken literally from people in different projects I’ve been on in my career, some had to be translated to portuguese
  • let’s talk about line segments… and lifewe could probably come up with some equation to describe itbut we are human
  • and humans have the need of making sense of what they experience and observethey have the need of communication
  • so let’s go back to our segment of line called life
  • instead of saying that a given point in our life can be described by the distance between that point and A, since we don’t know B yet
  • we end up with these more abstract concepts that divide our life experience in smaller chunks, so we can make sense of them, and talk about them
  • let’s talk about a day… two spins of the clock, should we talk about….
  • this instead?
  • let’s say it is 11:55 pm and you start flossing
  • then you put your toothpaste in your brush and look at the clock, it is 00:01 now… what do you do? would you avoid starting to floss at that time?
  • what do I do now?
  • when you assume and or force a concept like that, if you are not careful, you might end up with things like thiswho NEVER heard this in a project?
  • it is hard to estimate a project… we guess it crudely most of the time… why extend this to a pointless per iteration exercise? why try to predict the future? are you going to act on it? why say…
  • why say this? what happens if we don’t? can we really say that we will work towards doing so?
  • why say this? what happens if we don’t? can we really say that we will work towards doing so?
  • remember when we got to this point? what sense did all that meta-discussion make? would it have changed our behaviour at all in the upcoming iteration?why so much stress? why so many lies? why not be honest with yourself?does it even matter if we discuss this over and over and over?
  • isn’t that the only honest thing we can really say?
  • awesome, everyone is happy that way… but what usually happens?
  • what if our client still wants to talk about iterations and don’t buy this whole continuous work thing?
  • clientes, usuários, gerentes?
  • how can I still talk in a meaningful way for planning?
  • mention cycle time toohow much is produced over time
  • we can still talk the same language, without being bound by pointless contraints
  • if we look at the past, we can observe some very interesting stuff
  • this is kind of like velocity but not really… we are not commiting to the next iteration, just extracting metrics out of historical data. we did this on a scenario where there was a scrum of scrums
  • is it more interesting to talk about points? or is it more interesting to talk about…
  • features over time? which one brings us closer to what essentially our stakeholders and ourselves are looking at? which one of them brings us close to the end of the rainbow?
  • the great question we aim to answer is how much time it takes?precisamosestimarhistórias?
  • seráque se nósnosfocarmosmaisnumfluxocontínuo e empequenaspartes de trabalhonãonosaproximamosmaisrapidamente de responder a pergunta fundamental de sofware?
  • study from Vasco Duarte, from finland… prediction data after 5 sprints, for a 20+ iterations project… the data contributed by readers and capture by the author seem to gravitate around it being roughly equivalent to use # of stories vs # of points, even on immature teams
  • Iterações: melhor sem elas?

    1. 1. iteraçõesmelhor sem elas?
    2. 2. Mozair@MACSkeptichttp://github.com/MACSkeptic
    3. 3. •Testes•Linguagens•Estimativas•Processos
    4. 4. •Testes•Linguagens•Estimativas•Processos
    5. 5. iterações
    6. 6. iterações !=desenvolvimento iterativo
    7. 7. meet team rocket
    8. 8. 4 developers2 quality analysts
    9. 9. Business AnalystsManagersProduct OwnersScrum Masters
    10. 10. Business AnalystsManagersProduct OwnersScrum Masters
    11. 11. points 23 19 20 15 25 17 21 18 sprint
    12. 12. planning
    13. 13. KH
    14. 14. H
    15. 15. H (3)
    16. 16. points 23 19 20 15 25 17 21 18 sprint
    17. 17. H (3)
    18. 18. XP•communication•courage•feedback•respect•simplicity
    19. 19. XP• communication•courage• feedback• respect• simplicity
    20. 20. H (3)
    21. 21. “o time se compromete aentregar 22 pontos naspróximas 2 semanas”
    22. 22. backlog in dev qa done 10 dias
    23. 23. backlog in dev qa done H (3) dia 0
    24. 24. backlog in dev qa done H (3) dia 1
    25. 25. backlog in dev qa done H (3) dia 3
    26. 26. backlog in dev qa done H (3) dia 4
    27. 27. backlog in dev qa doneH (3) dia 5
    28. 28. backlog in dev qa done H (3) dia 6
    29. 29. backlog in dev qa done H (3) dia 6
    30. 30. backlog in dev qa done??? H (3) dia 7
    31. 31. backlog in dev qa done H (3) dia 7
    32. 32. backlog in dev qa done H (3) dia 8
    33. 33. backlog in dev qa done??? H (3) dia 9
    34. 34. backlog in dev qa done H (3) dia 10
    35. 35. recaptulando
    36. 36. dia 6: 15 pontos dia 10: 22 pontos 8 WIP 
    37. 37. retrospectiva &planejamento
    38. 38. 22 pontosentregues
    39. 39. 8 pontos WIP
    40. 40. quantos pontos na próxima iteração?
    41. 41. backlog in dev qa done H (3) dia 10
    42. 42. planning
    43. 43. P (3)
    44. 44. P (1)
    45. 45. backlog in dev qa done L(5) dia 0
    46. 46. backlog in dev qa done L(5) dia 6
    47. 47. backlog in dev qa done L(5) dia 10
    48. 48. recaptulando
    49. 49. dia 6: 3 pontos dia 10: 15 pontos 6 WIP 
    50. 50. retrospectiva &planejamento
    51. 51. 15 pontosentregues
    52. 52. (╯ ╯ ┻━┻
    53. 53. ┬─┬ノ( º _ ºノ)
    54. 54. 6 pontos WIP
    55. 55. quantos pontos na próxima iteração?
    56. 56. backlog in dev qa done L(5) dia 10
    57. 57. points 23 19 20 15 25 17 21 18 sprint
    58. 58. points 23 19 20 15 25 17 21 18 22 15 sprint
    59. 59. iterações
    60. 60. ciclodefinido 
    61. 61. objetivo claro 
    62. 62. foco 
    63. 63. foco 
    64. 64. entregar os pontos 
    65. 65. conceitoforçado 
    66. 66. A B
    67. 67. A B
    68. 68. A X B
    69. 69. dias horas anos A Xmeses semanasB
    70. 70. “não vamos começar uma nova estóriaporque é o último dia da iteração”
    71. 71. “essa estória veio da iteração passada,precisamos evitar que isso aconteça”
    72. 72. guesstimate 
    73. 73. “o time se compromete a entregar 20 pontos nas próximas 2 semanas”
    74. 74. velocidade “futura”
    75. 75. scope quality$$$$ tempo
    76. 76. scope realityquality tempo/$$$
    77. 77. “o time se compromete a entregar 20 pontos nas próximas 2 semanas”
    78. 78. scope realityquality tempo/$$$
    79. 79. scope realityquality tempo/$$$
    80. 80. P (1)
    81. 81. “o time se compromete aentregar, com qualidade, o máximo possível nas próximas 2 semanas”
    82. 82. stakeholders
    83. 83. planejamento?
    84. 84. # pessoas vs porta
    85. 85. entrega vs tempo
    86. 86. “tempo”2 semanas?
    87. 87. iteração sprint2 semanas 10 dias
    88. 88. passado
    89. 89. “uma estória de 3 pontosleva em média 2 dias”
    90. 90. “em 2 semanas são entregues em média 20 pontos”
    91. 91. pontos
    92. 92. features
    93. 93. estórias/tempo vspontos/tempo
    94. 94. quantotempo leva?
    95. 95. Real Previsto Real Previsto 13% 4% 350 396 228 220Pontos Pontos Stories Stories
    96. 96. obrigado!  @MACSkeptic

    ×