making feedback visible_agileee_2010
TRANSCRIPT
Making Feedback Visible Coloring the Elephant
Anda Abramovici & Sudhindra Rao
& special appearance from Chris Leishman
Our talk today
team dynamics
making the obvious, obvious!
metrics
story telling
shared context convincing people of things
informa8on radiators
making the obvious, obvious! About feedback
3 Points in 8me Project ini8a8on
Project in flight
Project at risk
Coloring your elephant
Feedback
Feedback is informa8on
made available and usable
What kind of informa8on
Anything about the project
Recurring
Quan8ta8ve – what you can measure or count
Qualita8ve – what people say
OHen much informa8on is available, but
hidden (in plain sight)
not understood
not ac8onable by the team
Where does feedback come from
People team
stakeholders
Where does feedback come from
People team
stakeholders Automated systems
code build CI
Where does feedback come from
People team
stakeholders Automated systems
code build CI
Results of delivery did we deliver on 8me
customer sa8sfac8on
How do we get feedback
Standup
IPM
Retrospec8ve
Informa8on radiators
When do we discuss it Standup
IPM
Retrospec8ve
During the course of every day
When do we act on it Standup
IPM
Retrospec8ve
During the course of every day
Project ini8a8on
Process maps and value streams
Story wall with epics
Release planning exercises
Itera8on planning exercises
Story: The great wall of stories
aka
From dev team to CEO in one glance
… actually, it took 3 weeks
Or, How we came to be “the one”
Construc8ng a useful story wall
Vote & Priori8ze
Measure & Organize
Project in flight
Monitoring development progress
Story card wall
Burn up charts
Development monitors
QA monitors
Bugs dashboard
Release quality
Story: QA and Developer Dashboard
When consistency is a bad thing
Give the elephant a voice
Inherited SILK test suite
?
Story: So many applications.. So little time..
http://github.com/betarelease/cc_monitor
Story: So many applications.. So little time..
http://github.com/betarelease/cc_monitor
Integra8on Applica8on
Last success: 1 minute ago
295 20
Visualising Priority
10% 12% 5% 28% 8% 3% 4%
10% 12% 5% 28% 8% 3% 4%
Visualising Progress
✓
✓
✓
✓
✓
✓
✓
✓
✓ ✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓ ✓
✓
✓
✓
✓
✓
✓
Visualising Risks
Project at Risk
Delivery deadlines
Conflic8ng requirements
Gold pla8ng
Reality check
Newton’s Timeline
Story: How selenium grid was born
Lack of feedback slowed us down
Build 8me
Story: How selenium grid was born
Detailed informa8on drives decision
Crea8ve solu8on leads to industry benefit
Story: Newton’s 8meline in ac8on
We didn’t know where we were We knew:
Everyone needs to see: what’s s8ll leH to do?
Better focusing decisions & repriori8za8on
Anatomy of Newton’s 8meline
End Date Milestone
Timeline
Milestone
Today
Work func8on
Team Name
Should be completed Things s8ll need doing Things s8ll need doing Things s8ll need doing Things s8ll need doing
Things s8ll need doing Things s8ll need doing Things s8ll need doing Things s8ll need doing
Should be completed Should be completed Should be completed
Should be completed Should be completed Should be completed Should be completed
Story: Newton’s 8meline in ac8on
Better focus, decisions & repriori8za8on
Example of Newton’s Timeline
Effec8ve feedback is
Seen
Heard
Discussed
Acted upon
The importance of visibility
Focuses the team on what needs agen8on
The importance of visibility
Increased focus on common goal
The importance of visibility
Exposes areas of misunderstanding
The importance of visibility
Exposes areas of disagreement
The importance of visibility
Leads to shared context
The importance of shared context
team members gain a
common understanding
The importance of shared context
inconsistencies in understanding are discovered and resolved
This can sometimes take a long time
The importance of shared context
The very act of discovering these inconsistencies
encourages awareness and increased collabora8on
Visible feedback
Low maintenance
Easily explained
Easily maintained by the team
Easily adapted to changing informa8on
Become focal point for the team
Make it sustainable
Deciding what to look at
Experiment
What you care about Experience
Disrup8ons
When you “know” something and want to explain it
Deciding what to look at
Experiment
What you care about Experience
Disrup8ons
When you “know” something and want to explain it
Look at the Elephants
Let the problem be your guide
You know you’re missing the mark, but not by how much or what to do about it.
You’re stuck wai8ng for other teams to deliver
The build is taking too long
Too many broken builds
Don’t stare at the mouse
Coloring your elephant
