Information radiators


Published on

Slides from my talk at Agile Portugal.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Ward A100 errors in administering medicine reported this yearWard B10 errors in administering medicine reported this year
  • Ward A100 errors in administering medicine reported this yearWard B10 errors in administering medicine reported this year
  • Scrum valuesA ) COMMITMENT -Be willing to commit to a goal. Scrum provides people with all the authority they need to meet their commitmentsB) FOCUS - Do your job. Focus all your efforts and skills on doing the work that you have committed to doing. Dont worry about anything else.C) OPENNESS- Scrum keeps everything about a project visible to everyone.D) RESPECT- Individuals are shaped by their background and their experiences. It is important to respect the different people who comprise a team.E) COURAGE- Have the courage to commit, to act, to be open and to expect respectXPCommunicationFeedbackSimplicityCourage(Respect?)
  • This is not a useful information radiator. How many ways is it wrong? Too small, focus on people not work, no history, no future, completely uncontrolled WIP
  • Trade off sliders – helps the team with their decisions. Self-organisation tool, takes the decision making very close to the workThanks for Juliano
  • 400 Lunch Target200 Dinner
  • Simple, clear. Are there too many states? Are there a whole lot of hand offs? Why are there two colours of cards?Easy to create, should be easy to maintain.Be careful of “Ready for” states, as these create queues.
  • Sparse board. Excuse – team was going to ramp up.Nothing special
  • Not a tool for the scrum master or project manager
  • Burn up charts. Courtesy of JulianoBersano & Luke StubblesFocus on the work. History, near present, and future… release burn ups so don’t show what is happening right now. Simple to create, maintain and understandLeft – basic chart, are we close to the burn? Simple, clearRight – more complex visiualisation, can be used as a cumulative flow diagram
  • Luke StubblesVisualising and reducing WIP (Work in Progress). each team member has 3 avatars (each numbered 1,2 & 3). People pick them up from the parking bay (wip 1). It allows you at a glance to see when people are working on more than 1 thing - and it's great to refer to as a success measure with the team.
  • Build light – broken, building, ok.You only know current state, not where you were, how long you have been in the current state.
  • Yeung’s build dashboard.Different builds, how long they took, how long they should have taken, how long ago, which tests have been run. Nicely fractal, get some information at a glance, then more as you get closer.
  • Trade off sliders – helps the team with their decisions. Self-organisation tool, takes the decision making very close to the workThanks for Juliano
  • a little abstract. Nice visuals, and shows some history.
  • Lots of information, but does it work? Is there too much here?
  • DefectsBurn up chartsTree integration
  • Someone is fixing the buildSomeone is working on something of no value
  • Who is doing what. Useful for WIP control and organisation
  • Information radiators

    1. 1. What makes a good information radiator?<br />Lachlan Heasman – ThoughtWorks Australia<br />
    2. 2. A choice<br />A<br />B<br /><br />Which ward <br />would you choose?<br /><br />
    3. 3. WARD A<br />A<br />Medical units with more reported errors, for instance, in administering medicine, actually had better health outcomes for their patients<br />Pfeffer, J. 2007 – What Were They Thinking?<br /><br /><br />
    4. 4. What’s that got to do with Information Radiators? Or agile? <br />HURRY UP!<br />
    5. 5. Courage<br />Without knowing about a problem you cannot fix the problem<br />Admitting to a mistake or problem takes courage because “Hierarchies don’t like bad news” Seddon<br />Courage is a value that underpins both Scrum and XP<br />It takes courage to create a good information radiator<br />
    6. 6. Information Radiator<br /> Alistair Cockburn - Agile Software Development 2nd edition- 2007<br /> "An information radiator displays information in a place where passers by can see it. With information radiators, the passers by don't need to ask any question; the information simply hits them as they pass."<br />
    7. 7. OK, but so what?<br />
    8. 8. Why Bother with this?<br />Information is hard to see, and all we have to work with in software development is information<br />Looking for information on delivery is wasteful <br />Requires extra processes<br />People have to wait<br />Increases time to react<br />Information loses value with time<br />Would your customer pay for a status report?<br />
    9. 9. What do we get out of this?<br />Information radiators can:<br />Help a team self-organise<br />Protect a team by broadcasting the state of delivery – no surprises<br />Assist with organisation and planning<br />Call attention to what is going on with the work<br />Control / highlight WIP<br />
    10. 10. OK I want to jump in. How do I do this?<br />
    11. 11. Focus on the work<br />What do you have to do?<br />What is getting in the way?<br />How long is it taking to get something done?<br />Is there uncertainty?<br />Take a system view of what is happening<br />
    12. 12. Horror<br />
    13. 13. KISS<br />Keep It Simple, Stupid<br />Easily changed and maintainable<br />Do it by hand, not with a tool (unless it’s Mingle)<br />
    14. 14. Simple<br />
    15. 15. Predictive & Reflective<br />Predictive – gives you the chance to do something different to avoid problems<br />Reflective – shows if anything has changed<br />
    16. 16. Outstanding Issues Over Time<br />
    17. 17. Change as work changes<br />As you learn how learn more you should be adapting how you are working<br />As you change how you work the way you present what is happening should change<br />Unlike a status report; there is not a template you use and stick with<br />
    18. 18. Story wall<br />
    19. 19. Story wall<br />
    20. 20. Make it big<br />The information must be easily seen and understood<br />Use colour and form<br />People can move closes for details<br />
    21. 21. Story Wall<br />
    22. 22. Make it everyone’s<br />The team must own it<br />The team must keep it up to date<br />
    23. 23. How about you show us what you have been talking about?<br />
    24. 24. Burn up charts<br />
    25. 25. The Wall!<br />
    26. 26. WIP Control<br />
    27. 27. Build lights<br />
    28. 28. Build dashboard<br />
    29. 29. SLiders<br />
    30. 30. Riskometer<br />
    31. 31. combinations<br />
    32. 32. combinations<br />
    33. 33. Combinations<br />
    34. 34. People radiators<br />
    35. 35. People radiators<br />
    36. 36. How to do it?<br />Have courage<br />Focus on the work!<br />Keep it simple<br />Predictive and reflective<br />Change as work changes<br />Make It big<br />Make it everyones<br />
    37. 37.
    38. 38. The end<br />