Is your team performing?

getting metrics out of your team?

How about your product?

in fact, how well do you know your product?

How will you know?

feedback from users, ops, testing?

Once upon a time at

consultants, working as developer and tester

We had a problem

We wanted to settle concerns about stability and performance for a new application about to be integrated in a legacy environment

Blunt tools

Subject kept popping up, much labor to settle it (to our satisfaction) every time From the heart of the application Lack "depth" Lack reliability/repeatability Involve manual labor Provide slow feedback MBeans/JConsole => No mining, unreliable Cron/CSV/Excel => Hard to repeat, much work, error prone

Water cooler effect

an immediate side effect

[ demo time ]

Apply a function, nonNegativeDerivative, talk about composability, how different data can be combined easily

Pulling metrics

Pushing metrics

Thirst for knowledge

need for metrics, notice missing info, eagerness to retest/deploy, experimentation

Familiarity with behaviour

easily spot trends/errors, don't panic, spotted prod. HW problems

Increased confidence

outspoken within the team, outside (graph as fact), history as reference

Influence on design

at least one feature not impl., metrics show when/where improvement needed (or not)

A tool for testing

data as reference when "composing" is easy!, regressions using historic data

Starting early

start in development, silos, ready for prod.