Continous Monitoring

4,047 views

Published on

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.

Published in: Technology

Continous Monitoring

  1. 1. Sreekanth @sreeix 1
  2. 2. Nilakanta @nilakanta 2
  3. 3. Developers 3
  4. 4. ThoughtWorks www.thoughtworks.com 4
  5. 5. Continuous Monitoring (For Continuous Improvement) 5
  6. 6. Presentation = 45 Min. 6
  7. 7. Design Radiators = Remainder 7
  8. 8. Jargon Warning 8
  9. 9. We all know Continuous Integration... 9
  10. 10. Cruisecontrol 10
  11. 11. Cruisecontrol.net 11
  12. 12. Hudson 12
  13. 13. Cruise 13
  14. 14. And We’ve Had Build Radiators 14
  15. 15. Angry Snowman 15
  16. 16. Traffic Lights 16
  17. 17. Nabaztag 17
  18. 18. Build Radiator 18
  19. 19. More Build Radiators 19
  20. 20. Why? 20
  21. 21. am·bi·ent: adjective existing or present on all sides 21
  22. 22. vi·su·al: adjective producing mental images 22
  23. 23. au·to·mat·ic: adjective having a self-acting or self- regulating mechanism 23
  24. 24. ac·ces·si·ble: adjective capable of being used or seen 24
  25. 25. Story of a Large Agile Project 25
  26. 26. Developers Write Code 26
  27. 27. QA’s Write Functional Tests 27
  28. 28. People call for Deleting Functional Tests 28
  29. 29. PM Steps in... 29
  30. 30. Adds Tests the Build Radiator 30
  31. 31. ~15 passing tests out of 70 31
  32. 32. No New functional tests (aka. Stop the Line) 32
  33. 33. Fix Existing Tests 33
  34. 34. Add New Tests 34
  35. 35. Ends with most passing tests and growing 35
  36. 36. Left Test metrics on radiator 36
  37. 37. Team own up for tests (Collective Responsibility) 37
  38. 38. Right Away (Fast Feedback) 38
  39. 39. Deja Vu? 39
  40. 40. Digression... 40
  41. 41. Andon 41
  42. 42. Lean Manufacturing 42
  43. 43. Jidoko Quality Control System 43
  44. 44. Andon ( , , ) is a manufacturing term 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 problem 44
  45. 45. Andon Board (Image Credit: wikipedia) 45
  46. 46. Detect a problem 46
  47. 47. Stop 47
  48. 48. Fix the Immediate problem 48
  49. 49. Install a Countermeasure 49
  50. 50. Automate Supervisory Functions 50
  51. 51. Not Production Function 51
  52. 52. Employees decide when to stop 52
  53. 53. Employees Decide Counter Measures 53
  54. 54. Examples 54
  55. 55. Examples 55
  56. 56. Back to Software Development 56
  57. 57. Big Visible Charts 57
  58. 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 one can miss. 58
  59. 59. Tests 59
  60. 60. Burn Down 60
  61. 61. Scope Burndown 61
  62. 62. Niko Niko Cal 62
  63. 63. XP Values Quiz Communication Feedback Simplicity Courage Respect 63
  64. 64. XP Values Quiz Communication Feedback Simplicity Courage Respect 64
  65. 65. Good Projects Gone Bad 65
  66. 66. Good at Detecting Problems 66
  67. 67. Good at Fixing Problems 67
  68. 68. Not Good At Stopping 68
  69. 69. Worse At Installing Countermeasures 69
  70. 70. Enter. 70
  71. 71. Continuous Monitoring 71
  72. 72. Coined by Owen Rogers (@exortech) 72
  73. 73. “the practice of leveraging ambient displays to provide the whole team with information to continuously monitor overall project health” 73
  74. 74. Not Just ... 74
  75. 75. Build Status 75
  76. 76. Burndowns 76
  77. 77. It is... 77
  78. 78. Project Information 78
  79. 79. Source Control History 79
  80. 80. 80
  81. 81. Deployment Status 81
  82. 82. Performance metrics 82
  83. 83. Code Quality 83
  84. 84. 84
  85. 85. Team Calendar 85
  86. 86. Wasted time in meetings 86
  87. 87. 87
  88. 88. Use your imagination... 88
  89. 89. Information lives in silos 89
  90. 90. Project Management Software 90
  91. 91. (D)SCM Repositories 91
  92. 92. Operational Databases 92
  93. 93. Bugtrackers 93
  94. 94. Emails 94
  95. 95. Excel Sheets 95
  96. 96. Lead QA worries about Bug Queue 96
  97. 97. Tech Leads worry about Code Quality 97
  98. 98. PM Worries about Stories Signed off 98
  99. 99. Democratize Information 99
  100. 100. Make it collective Responsibility 100
  101. 101. Another Story... 101
  102. 102. 102
  103. 103. Simple Radiator with Build 103
  104. 104. Branch R1 - 2306 Stage 1 - 2608 Smoke - 2601 DB - 2306 Regression - 2308 CCDashboard 104
  105. 105. Performance problems 105
  106. 106. Operational Database 106
  107. 107. Reported Metrics in standup every week 107
  108. 108. Tech cards for the Issues 108
  109. 109. Operational Metrics 109
  110. 110. People fix issues soon as they see. 110
  111. 111. Everybody looked at Performance 111
  112. 112. Right Away. 112
  113. 113. I focus on writing code 113
  114. 114. Bugs 114
  115. 115. Bug Map 115
  116. 116. 116
  117. 117. Refactor Problem Areas 117
  118. 118. Prerequistes 118
  119. 119. Open workspace 119
  120. 120. Open Information 120
  121. 121. Self organizing Teams 121
  122. 122. Implementation 122
  123. 123. Step 1 123
  124. 124. Big Visible Charts 124
  125. 125. It is easy. 125
  126. 126. Step 2 126
  127. 127. Software Radiators 127
  128. 128. Start with... 128
  129. 129. Build Monitoring 129
  130. 130. Add as new problems are fixed 130
  131. 131. Software > Paper Charts 131
  132. 132. Automated 132
  133. 133. Flexible Representation 133
  134. 134. Flexible Alerting 134
  135. 135. Tips for Radiators 135
  136. 136. Focus on Problems 136
  137. 137. Not Metrics 137
  138. 138. Trends 138
  139. 139. Not Absolute Numbers 139
  140. 140. Visibility and Simplicity 140
  141. 141. Not too much data 141
  142. 142. Visualization is important 142
  143. 143. One size may not fit all teams 143
  144. 144. Caveats (as you build raidators) 144
  145. 145. Too much data 145
  146. 146. Use More Radiators 146
  147. 147. Use Alerts 147
  148. 148. Don’t Bother me till there is a problem 148
  149. 149. Don’t display Coverage till it is Abnormal 149
  150. 150. Like Nagois 150
  151. 151. Questions? 151

×