Continous Monitoring

download Continous Monitoring
  • date post

    06-May-2015
  • Category

    Technology

  • view

    3.661
  • download

    0

Embed Size (px)

description

Most lean manufacturing system have some version of singnelling or notifications system that is used by the workers to signal issues and errors. Andon is a very important part of Lean Manufacturing process, but it's an often overlooked practice in the Agile Development process.There are vast amounts of data produced out of an agile software development process, but most of it live in their own silos, where the access is available to only few people. The metrics on the process that are presented to the team are hard to understand, makes little sense and represents very limited scope. We champion the use of visually appealing and all round view of the development process. We also present a set of metrics that we build the andon process around, it breaks down the traditional data silos (includes source code information, deployment/bugs/story/application performance/build status) and makes information accessible to all people on the team. And when all the information is shared across the team in visually appealing way people feel empowered to detect and resolve the process problems.Information radiators are widely used in development process.We will also present our version of the information radiator that's based on these ideas.

Transcript of Continous Monitoring

  • 1.Sreekanth@sreeix 1

2. Nilakanta @nilakanta2 3. Developers3 4. ThoughtWorks www.thoughtworks.com4 5. Continuous Monitoring (For Continuous Improvement)5 6. Presentation = 45 Min. 6 7. Design Radiators = Remainder7 8. Jargon Warning8 9. We all knowContinuous Integration... 9 10. Cruisecontrol 10 11. Cruisecontrol.net 11 12. Hudson12 13. Cruise13 14. And Weve Had Build Radiators 14 15. Angry Snowman 15 16. Traffic Lights16 17. Nabaztag17 18. Build Radiator18 19. More Build Radiators19 20. Why? 20 21. ambient: adjective existing or present on all sides21 22. visual: adjective producing mental images22 23. automatic: adjective having a self-acting or self- regulating mechanism 23 24. accessible: adjective capable of being used or seen24 25. Story of a LargeAgile Project25 26. Developers Write Code26 27. QAs Write Functional Tests27 28. People call for Deleting Functional Tests 28 29. PM Steps in...29 30. Adds Tests the Build Radiator30 31. ~15 passing tests out of 70 31 32. No New functional tests (aka. Stop the Line)32 33. Fix ExistingTests33 34. Add New Tests 34 35. Ends with most passing tests and growing35 36. Left Test metrics on radiator 36 37. Team own up fortests(Collective Responsibility)37 38. Right Away(Fast Feedback)38 39. Deja Vu?39 40. Digression... 40 41. Andon41 42. Lean Manufacturing42 43. Jidoko Quality Control System43 44. Andon (,, ) is a manufacturingterm referring to a system to notify management, maintenance, and other workers of a quality or process problem. The centrepiece is a signboard incorporating signal lights to indicate which workstation has the problem44 45. Andon Board(Image Credit: wikipedia)45 46. Detect a problem46 47. Stop47 48. Fix the Immediateproblem48 49. Install a Countermeasure49 50. Automate SupervisoryFunctions50 51. Not Production Function51 52. Employees decide when to stop52 53. Employees Decide Counter Measures 53 54. Examples54 55. Examples55 56. Back to SoftwareDevelopment56 57. Big Visible Charts57 58. Display important project information not in some formal way, not on the web, not in PowerPoint,but in charts on the wall that no onecan miss.58 59. Tests 59 60. Burn Down 60 61. Scope Burndown61 62. Niko Niko Cal 62 63. XP Values QuizCommunication Feedback SimplicityCourageRespect 63 64. XP Values QuizCommunication Feedback SimplicityCourageRespect 64 65. Good Projects Gone Bad65 66. Good at DetectingProblems 66 67. Good at Fixing Problems67 68. Not Good AtStopping 68 69. Worse AtInstalling Countermeasures69 70. Enter.70 71. Continuous Monitoring71 72. Coined by Owen Rogers (@exortech) 72 73. the practice of leveraging ambient displays to provide the whole team with information to continuously monitor overall project health 73 74. Not Just ... 74 75. Build Status75 76. Burndowns 76 77. It is... 77 78. Project Information 78 79. Source ControlHistory79 80. 80 81. Deployment Status81 82. Performance metrics 82 83. Code Quality83 84. 84 85. Team Calendar 85 86. Wasted time in meetings86 87. 87 88. Use your imagination...88 89. Information lives insilos89 90. Project ManagementSoftware 90 91. (D)SCM Repositories91 92. OperationalDatabases 92 93. Bugtrackers 93 94. Emails94 95. Excel Sheets95 96. Lead QA worries about Bug Queue 96 97. Tech Leads worry about Code Quality 97 98. PM Worries about Stories Signed off98 99. Democratize Information 99 100. Make it collectiveResponsibility100 101. Another Story... 101 102. 102 103. Simple Radiatorwith Build 103 104. Branch R1 - 2306 Stage 1 - 2608 Smoke - 2601 DB - 2306 Regression - 2308CCDashboard104 105. Performanceproblems 105 106. OperationalDatabase 106 107. Reported Metrics in standup every week 107 108. Tech cards for the Issues108 109. Operational Metrics 109 110. People fix issues soon as they see. 110 111. Everybody looked at Performance111 112. Right Away. 112 113. I focus on writingcode113 114. Bugs 114 115. Bug Map 115 116. 116 117. Refactor ProblemAreas117 118. Prerequistes 118 119. Open workspace119 120. Open Information120 121. Self organizingTeams 121 122. Implementation 122 123. Step 1123 124. Big Visible Charts 124 125. It is easy. 125 126. Step 2126 127. Software Radiators 127 128. Start with... 128 129. Build Monitoring129 130. Add as new problems are fixed 130 131. Software > PaperCharts131 132. Automated 132 133. Flexible Representation133 134. Flexible Alerting 134 135. Tips for Radiators 135 136. Focus on Problems136 137. Not Metrics 137 138. Trends138 139. Not AbsoluteNumbers139 140. Visibility andSimplicity140 141. Not too much data141 142. Visualization is important142 143. One size may not fit all teams143 144. Caveats (as you buildraidators) 144 145. Too much data 145 146. Use More Radiators 146 147. Use Alerts147 148. Dont Bother metill there is a problem 148 149. Dont display Coverage till it isAbnormal149 150. Like Nagois 150 151. Questions?151