Downloaded 46 times
Uploaded byPaulo Caroli
A linha de montagem de SW -n paulo caroli - QconSP 2010
O documento aborda o fluxo de trabalho no desenvolvimento de software utilizando metodologias ágeis, destacando a natureza empírica e concorrente do processo. Apresenta exemplos de workflows e a importância de ferramentas visuais como card walls para gerenciar tarefas e restrições. Ele enfatiza a integração contínua e a necessidade de adaptação constante dentro de equipes multifuncionais.
More Related Content
Similar to A linha de montagem de SW -n paulo caroli - QconSP 2010
![]project-open[ Workflow Developer Tutorial Part 4](https://cdn.slidesharecdn.com/ss_thumbnails/po-workflow-tutorial-4-training-slides-100605a-101013103857-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
A linha de montagem de SW -n paulo caroli - QconSP 2010
- 1. A linha demontagem de SW representada como cartões na paredePaulo CaroliAgile Coachpcaroli@thoughtworks.comTwitter: @paulocaroli
- 2. AgendaWorkflowDesenvolvimento de SWe AgileCartõesnaparedeConceitosQ&A
- 3.
- 4. Um fluxo detrabalho (workflow) é uma sequência de etapas e atividades de trabalho realizado por uma pessoa ou uma equipe, para alcançar um objetivo específico.
- 5. Um fluxo detrabalho sequencial é um fluxo de trabalho onde cada etapa do trabalho depende da fase anterior.
- 7.
- 11.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. A Workflow snapshot(instantâneo)
- 20.
- 21.
- 22. Desenvolvimento de SWnão é uma atividade altamente previsível nem repetitiva.
- 23. Desenvolvimento de SWé uma ativitade empírica!
- 24. “relativo aos médicos cuja habilidadederive da experiência prática e não da instrução da teoria.” (Wikipedia)
- 25.
- 26. Agile enfatiza ocontrole do processo empírico.
- 27. Inspect and adaptLean’skaizenScrum’s sprint retrospectivesXP’s weekly iterations and short releases
- 28.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 51.
- 53. O workflow dedesenvolvimento de SW
- 55.
- 58. Emmétodos tradicionais, oworkflow e o desenvolvimento sãosequenciais
- 59.
- 60.
- 61. Em Agile, oworkflow ésequencial, mas o desenvolvimentoé concorrente
- 62.
- 63.
- 64.
- 65.
- 66.
- 67. A linha demontagem de SW(comumpara times usandoAgile)
- 74.
- 75.
- 76.
- 77.
- 78.
- 79.
- 80.
- 81.
- 82. Um exemplo deCard Wall
- 83. In QASigned OffBacklogInDev7125110JohnDan4Suzy9182131Paul175Amy
- 84.
- 85.
- 86.
- 87.
- 88.
- 89. DoneTo DoDoingDay 61210Day110101JohnLatency754Suzy9211831Paul175Amy
- 91. DoneTo DoDoingThroughput12101JohnDay 175Day24Suzy92118Day 331Paul175Amy
- 92.
- 93. In QASigned OffBacklogInDevDan1012John1315Suzy491821Paul17Amy5
- 94. Emque a Suzyestá trabalhando?
- 95. In QASigned OffBacklogInDevDan1012John1315Suzy491821Paul17Amy5
- 96. In QASigned OffBacklogInDevDan1012John13145SuzyOnhold91821Paul17Amy5
- 97.
- 98.
- 99.
- 100. Signed OffIn DevInQABacklog12101JohnSuzy5Dan493118PaulAmy217517
- 101.
- 102. Signed OffIn DevInQABacklog12101JohnSuzy5Dan493118PaulAmy217517
- 103. Qual é oestado do cartão #7?
- 104. Signed OffIn DevInQABacklog12101JohnSuzy5Dan493118PaulAmy217517
- 105. In QASigned OffInDev QBacklog10121JohnSuzy57Dan49311821PaulAmy517
- 106.
- 107. In QASigned OffInDev QBacklogDan10121JohnSuzy49311821PaulAmy51775
- 108. In QASigned OffInDev QBacklog121JohnSuzy49311821PaulAmy517107Dan5
- 109. In QASigned OffInDev QBacklog121JohnSuzy49311821Amy517107DanPaul5
- 110.
- 111. In QASigned OffInDev QBacklog12101JohnSuzy57Dan493118PaulAmy21517
- 112. In QASigned OffInDev QBacklog12101JohnSuzy57Dan493118PaulAmy3121517
- 113. In QASigned OffInDev QBacklog12101JohnSuzy57Dan49918PaulAmy3121517
- 114. In QASigned OffInDev QBacklog12101JohnSuzy57Dan4918PaulAmy3121517
- 115.
- 116. Up Stream> Workflow >Down Stream931PaulAmy
- 117. Up Stream> Workflow>Down Stream931PaulAmy31
- 118. Up Stream> Workflow>Down Stream99PaulAmy31
- 119. Up Stream> Workflow>Down Stream9PaulAmy31
- 120.
- 121. In QASigned OffInDev QBacklog12101JohnSuzy57Dan4918PaulAmy3121517
- 122. In QASigned OffInDev QBacklog10211JohnSuzy57Dan3141718PaulAmy1259
- 123.
- 124. In QASigned OffInDev QBacklog10211JohnSuzy57Dan3141718PaulAmy1259
- 125.
- 126. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy57Dan4918PaulAmy3121517
- 127. Pull System eLimites
- 128. Up Stream(X)Workflow >(Y)DownStream(2)931PaulAmy
- 129. Up Stream(X)Workflow >(Y)DownStream(2)931PaulAmy31
- 130. Up Stream(X)Workflow >(Y)DownStream(2)99PaulAmy31
- 131. Up Stream(X)Workflow >(Y)DownStream(2)9PaulAmy31
- 132. Up Stream(X)Workflow >(Y)DownStream(2)Get more work9PaulAmy31
- 133. Up Stream(X)Workflow >(Y)DownStream(2)539PaulAmy31
- 134. Pull System, Queuee Limites
- 135. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy57Dan4918PaulAmy3121517
- 136. 80% done onCard #9
- 137. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy57Dan4918PaulAmy3121517
- 138. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy57DanAmy4918PaulAmy3121517
- 139. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy57DanAmy4918Paul3121517
- 140. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy57DanAmy459Paul311821517
- 141. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy7DanAmy459Paul311821517
- 142. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy77DanAmy459Paul311821517
- 143. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy7DanAmy459Paul311821517
- 144. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy7DanAmy459PaulAmy311821517
- 145. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy7Dan459PaulAmy311821517
- 146. In QA(1)Signed OffInDev (2)Q(2)Backlog1210101JohnSuzy7Dan9459PaulAmy311821517
- 147. In QA(1)Signed OffInDev (2)Q(2)Backlog1210101JohnSuzy7Dan945PaulAmy311821517
- 148. In QA(1)Signed OffInDev (2)Q(2)Backlog12101JohnSuzy7Dan94510PaulAmy311821517
- 149. In QA(1)Signed OffInDev (2)Q(2)Backlog121JohnSuzy7Dan94510PaulAmy311821517
- 150. Maissobre Queue eLimites
- 151.
- 152.
- 153.
- 154.
- 155.
- 156.
- 157.
- 158. In QASigned OffBacklogInDev75112109184315
- 159.
- 160.
- 161.
- 162.
- 163. In QASigned OffBacklogInDev1212
- 164.
- 165.
- 166.
- 167.
- 168.
- 169.
- 170.
- 171.
- 172.
- 173.
- 174. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog1251JohnSuzy7Dan9451021PaulAmy311817
- 175.
- 176. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog1251JohnSuzy7Dan9451021PaulAmy311817
- 177. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog1251JohnSuzy7Dan9451021PaulAmy311817
- 178. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog1251JohnSuzyDan9451021PaulAmy3118717
- 179. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog1251JohnSuzyDan94510PaulAmy312118717
- 180. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog12591JohnSuzyDan4510PaulAmy312118717
- 181. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog591JohnSuzy12Dan4510PaulAmy312118717
- 182. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog7591JohnSuzy12Dan4510PaulAmy31211817
- 183.
- 184.
- 185.
- 186.
- 187.
- 188.
- 189.
- 190.
- 191.
- 192. Bugs de regressão(além dos cartões na parede)
- 193. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog1251JohnSuzy7Dan9451021PaulAmy311817
- 194. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog1251JohnSuzy7Dan9451021PaulAmy311811117
- 195. In QA(1)Signed OffInDev (2)Q(2)Q(2)Backlog211251JohnSuzy7Dan94510PaulAmy311811117
- 196.
- 197.
- 199.
- 200.
- 201.
- 202.
- 203.
- 204.
- 205.
- 206.
- 207.
- 208.
- 209. Não se esqueçasobre osBig Visible Charts
- 210. A parede é2D, pense em como adicionar outras dimensões
- 211. Cuidado com apoluição visual
- 212.
- 213.
- 214.
- 215.
- 216. Obrigado!Perguntas?A linha demontagem de SW representada como cartões na paredePaulo CaroliAgile Coachpcaroli@thoughtworks.comTwitter: @paulocaroli