Continous Monitoring
Upcoming SlideShare
Loading in...5
×
 

Continous Monitoring

on

  • 2,812 views

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 ...

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.

Statistics

Views

Total Views
2,812
Views on SlideShare
2,799
Embed Views
13

Actions

Likes
5
Downloads
82
Comments
0

3 Embeds 13

http://www.slideshare.net 7
http://paper.li 5
http://agilefaqs.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Continous Monitoring Continous Monitoring Presentation Transcript

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