Making feedback visible_agileee_2010

Making Feedback Visible Coloring the Elephant Anda Abramovici & Sudhindra Rao & special appearance from Chris Leishman

Our talk today story telling team dynamics metrics informa8on radiators making the obvious, obvious! shared context convincing people of things

making the obvious, obvious! About feedback 3 Points in 8me Project ini8a8on Project in ﬂight 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

Process maps and value streams Project Story wall with epics ini8a8on Release planning exercises Itera8on planning exercises

Story: The great wall of stories Or, How we came to be “the one” aka From dev team to CEO in one glance … actually, it took 3 weeks

Construc8ng a useful story wall

Vote & Priori8ze

Measure & Organize

Monitoring development progress Story card wall Project Burn up charts Development monitors in ﬂight 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.. 20 295 Integra8on Applica8on Last success: 1 minute ago http://github.com/betarelease/cc_monitor

Visualising Priority

10% 12% 8% 28% 5% 3% 4%

Visualising Progress

✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

Visualising Risks

Delivery deadlines Conﬂic8ng requirements Project Gold pla8ng at Risk 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 beneﬁt

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 Today Milestone Milestone End Date Timeline Should be completed Things s8ll need doing Work Should be completed Things s8ll need doing Should be completed Things s8ll need doing func8on Should be completed Things s8ll need doing Should be completed Things s8ll need doing Team Should be completed Things s8ll need doing Should be completed Things s8ll need doing Name Should be completed Things s8ll need doing

Story: Newton’s 8meline in ac8on Better focus, decisions & repriori8za8on

Example of Newton’s Timeline

Eﬀec8ve 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 Experience What you care about Disrup8ons When you “know” something and want to explain it Experiment

Deciding what to look at Experience What you care about Disrup8ons Look at the Elephants When you “know” something and want to explain it Experiment

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

Anda Abramovici Chris Leishman anda.abramovici@gmail.com chris@leishman.org 415‐516‐8247 Sudhindra Rao

http://agileee.org	137
http://agileee.com	6
http://2011.agileee.org	5
http://www.agileee.com	1

Making feedback visible_agileee_2010

by Anda Abramovici on Oct 12, 2010

Accessibility

Categories

Upload Details

Usage Rights

4 Embeds 149

Statistics

Making feedback visible_agileee_2010 — Presentation Transcript