Agileee is an awesome Agile conference that takes place in Eastern Europe. See you next year!

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

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

4. making the obvious, obvious!
About feedback
3 Points in 8me
Project ini8a8on
Project in flight
Project at risk
Coloring your elephant

5. Feedback

6. Feedback is informa8on
made available and usable

7. What kind of informa8on
Anything about the project
Recurring
Quan8ta8ve – what you can measure or count
Qualita8ve – what people say

8. OHen much informa8on is available, but
hidden (in plain sight)
not understood
not ac8onable by the team

9. Where does feedback come from
People
team
stakeholders

10. Where does feedback come from
People
team
stakeholders
Automated systems
code
build
CI

11. Where does feedback come from
People
team
stakeholders
Automated systems
code
build
CI
Results of delivery
did we deliver on 8me
customer sa8sfac8on

12. How do we get feedback
Standup
IPM
Retrospec8ve
Informa8on radiators

13. When do we discuss it
Standup
IPM
Retrospec8ve
During the course of every day

14. When do we act on it
Standup
IPM
Retrospec8ve
During the course of every day

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

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

17. Construc8ng a useful story wall

18. Vote & Priori8ze

19. Measure & Organize

20. Monitoring development progress
Story card wall
Project Burn up charts
Development monitors
in flight
QA monitors
Bugs dashboard
Release quality

21. Story: QA and Developer Dashboard
When consistency is a bad thing
Give the elephant a voice

22. Inherited SILK test suite

26. ?

27. Story: So many applications.. So little time..
http://github.com/betarelease/cc_monitor

28. Story: So many applications.. So little time..
20 295
Integra8on Applica8on
Last success: 1 minute ago
http://github.com/betarelease/cc_monitor

29. Visualising Priority

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

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

33. Visualising Progress

35. ✓ ✓ ✓ ✓ ✓ ✓
✓ ✓ ✓ ✓ ✓
✓ ✓
✓
✓
✓

36. ✓ ✓ ✓ ✓ ✓ ✓
✓ ✓ ✓ ✓ ✓
✓ ✓
✓
✓
✓

37. Visualising Risks

41. Delivery deadlines
Conflic8ng requirements
Project
Gold pla8ng
at Risk
Reality check
Newton’s Timeline

42. Story: How selenium grid was born
Lack of feedback slowed us down

43. Build 8me

44. Story: How selenium grid was born
Detailed informa8on drives decision
Crea8ve solu8on leads to industry benefit

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

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

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

48. Example of Newton’s Timeline

49. Effec8ve feedback is
Seen
Heard
Discussed
Acted upon

50. The importance of visibility
Focuses the team on what needs agen8on

51. The importance of visibility
Increased focus on common goal

52. The importance of visibility
Exposes areas of misunderstanding

53. The importance of visibility
Exposes areas of disagreement

54. The importance of visibility
Leads to shared context

55. The importance of shared context
team members gain a
common understanding

56. The importance of shared context
inconsistencies in understanding are
discovered and resolved
This can sometimes take a long time

57. The importance of shared context
The very act of discovering these inconsistencies
encourages awareness and
increased collabora8on

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

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

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

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

62. Don’t stare at the mouse

64. Coloring your elephant

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