continuous feedback: the new paradigm by jared richardson
TRANSCRIPT
Continuous Feedback The New Paradigm
Jared Richardson@JaredRichardson
Principal ConsultantAgile Artisans
Who Am I?
2
3
Cofounder of GROWS Methodology
Author Ship It! and Career 2.0
Screencast editor PragProg.com
2nd public signatory of the Agile Manifesto
Started AgileRTP in 2007
Coach
AgileArtisans.com
Jared Richardson
Outline
Tradition
Today
Future
Challenge
4
Tradition
5
How Long?
From idea to validation?
From coding to verifying?
From broken to knowing?
6
Requirements Coding
The Plan!
Great Job Team!Works hard. Finishes on time!
Testing Ship It!
Clear, clean requirements
Party!
Requirements Coding
Reality
Works hard Finishes late
Very late
Testing Ship It!
Fuzzy Incomplete
Requirements Coding
Reality
Much less time Complete validation
Works hard Finishes late
Very late
Testing
Fuzzy Incomplete
That’s not how it works!!
“Discussion”
Rewrite
Traditional Validation
Slow
Manual
Infrequent
Reactive
flickr.com/photos/sergiu_bacioiu/4607648893
Tradition
Start late
Short time
Accumulates
Blamed
Constant conflict
Two Approaches
Wait until it’s time
Constant feedback
Two Approaches
Let pressure build up
Depressurize daily
flickr.com/photos/wwarby/3016579275
The result of high pressure
flickr.com/photos/bryanburke/2854366734
Next Gen
Script stuff
Automate tests
Run everything frequently
flickr.com/photos/jdhancock/4238708849
Scripting
Builds
Unit tests
Continuous integration
Watch
Build
Unit Tests
PublishContinuous Integration
So What?
Hands are clean
Picked the right leg to operate on
Who cares?
Does it work?
Bottom rung in a tall ladder
flickr.com/photos/miguelvirkkunen/14621623115
Better is the enemy of best
19
Still Advancing
Automate deploys
Automate integration tests
SCMDevelopers
Watch
Build
Unit Tests
Deploy to Dev
Integration Tests
First Look
Continuous Testing
On Demand Deploy to QA
Manual Testing
Continuous Paradigm
Continuous Testing
Continuous Monitoring
Continuous Insight
What’s done to the environment?
Product is deployed
Supporting libraries updated
App server updated
App server configured
Database restarts
Who cares?
Detect Problems
Before it’s urgent
Detect
Notify
Fix
Traditionally…
Someone needs the app
Notices it’s down
URGENT!
FIX!
Fire drill
Wait 5 minutes
Integration Tests
Continuous Monitoring
Notify
EVERY PLATFORM
Foundation
Problems occur
Fast feedback is good
Slow feedback is bad
Automate as much as possible
Run FREQUENTLY
Tips
Start small
Is it alive?
One product
One environment
Don’t go all enterprisey
flickr.com/photos/fusionpanda/363012054
Feedback Loops
Identify
Reduce
Minutes
Not days
Never weeks
Easy Targets
Compiles
Unit tests
Integration tests
Installed applications
Good, Bad, or Ugly
Known State
Everything, or anything, worksflickr.com/photos/anyadora/4288244511
If you want to make a friend,
ask a favor-Ben Franklin
flickr.com/photos/pmillera4/5913371763
ChallengeExperiment
Within one week
Pick one project
Use Jenkins
Monitor one environment
Four weeks, re-evaluateflickr.com/photos/bernatcg/1123973353
Be Careful
Constant feedback
Highly addictive
Winning is fun
flickr.com/photos/pahudson/7046282179
36
