Download as PDF, PPTX
Uploaded byAnda Abramovici
Making feedback visible_agileee_2010
This document discusses making project feedback visible to teams. It emphasizes that while much information is available, it is often hidden, not understood, or not actionable by teams. It provides examples of sources of feedback, such as from people, automated systems, and delivery results. Various ways of discussing and acting on feedback are described, including through standups, IPMs, and retrospectives. Visualizing information through tools like burn up charts and dashboards is recommended to focus teams and expose misunderstandings. The importance of shared context through visible feedback that is easily maintained and adapted is highlighted.
More Related Content
Similar to Making feedback visible_agileee_2010
Making feedback visible_agileee_2010
- 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.
- 6.
- 7.
- 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.
- 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 wecame to be “the one” aka From dev team to CEO in one glance … actually, it took 3 weeks
- 17.
- 18.
- 19.
- 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 testsuite
- 26.
- 27. Story: So manyapplications.. So little time.. http://github.com/betarelease/cc_monitor
- 28. Story: So manyapplications.. So little time.. 20 295 Integra8on Applica8on Last success: 1 minute ago http://github.com/betarelease/cc_monitor
- 29.
- 31. 10% 12% 8% 28% 5% 3% 4%
- 32. 10% 12% 8% 28% 5% 3% 4%
- 33.
- 35. ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
- 36. ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
- 37.
- 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.
- 44.
- 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? Betterfocusing 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.
- 48.
- 49. Effec8ve feedback is Seen Heard Discussed Acted upon
- 50.
- 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.
- 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.
- 62.
- 64.
- 65. Anda Abramovici Chris Leishman anda.abramovici@gmail.com chris@leishman.org 415‐516‐8247 Sudhindra Rao