The Role of Human-Human Interfaces - presented at the 38th TCF 2013-03-16

250 views

Published on

Much of the work is creating successful software is managing the critical "human relationships" between stakeholders and team members. This presents practices and tools for eliciting requirements and strengthening ongoing communication during development.

Originally this was an Extended Session at the IEEE/ACM IT Professional Conference held at the 38th Annual Trenton Computer Festival, Saturday 2013-03-16.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
250
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

The Role of Human-Human Interfaces - presented at the 38th TCF 2013-03-16

  1. 1. IEEE/IT-PC at TCF.org
  2. 2. Which is the most difficult language to work in? C++ Python Perl Objective C None of the above
  3. 3. Which is the most difficult language to work in? C++ Python Perl Objective C None of the above
  4. 4. Which is the most difficult language to work in? … English … … or whatever else is the dominant language used to communicate in your workplace (e.g., Hindi, Hebrew, French, Spanish, Tagalog, etc.)
  5. 5. What I will talk about isn’t very technical … … but it isn’t very easy
  6. 6. Think of a good dining experience
  7. 7. … aren’t there really many involved?
  8. 8. … aren’t there really many involved? Kitchen and Staff
  9. 9. Waiter Bus Staff Prep Cook II Sommelier (Wine) Head Chef Manager Prep Cook I Sous Chef
  10. 10. User Representatives Ultimate Users Proponent Business Analyst (BA) Project Managers (PMO) Information Technology (IT) Funders Product Manager Software
  11. 11. User Representatives Ultimate Users Proponent Business Analyst (BA) Project Managers (PMO) Information Technology (IT) Funders Product Manager Software
  12. 12. User Representatives Ultimate Users Proponent Business Analyst (BA) Project Managers (PMO) Information Technology (IT) Funders Product Manager Software
  13. 13. Talking to Users  See exactly what users are actually doing …  “Job Shadowing”  Find out what users want …  Card Sorting … and other methods  Find out what people are thinking …  “Survey” … and other methods  Create designs that fit how users actually do thing  User-Centered Designs
  14. 14. Job Shadowing
  15. 15. Usability Test Video Observation
  16. 16. Using “Redesign” Card Sorts Question 25: Allow users to preview "Reading" items. Currently, they can preview "Scripts" and “Narrative" items
  17. 17. “Redesign” Card Sort Matrix Data
  18. 18. Low Medium High 1 2 3 4 5 6 7 Spell Check* (22) Undo* (33) Quick Save (23) Match tree and pane labels (15) Drop Down Prompts* (4) Toggle Set Leader Display *(20) Fix Graphics Preview* (31) Distinct Error messages (7) Preview Reading Items (25) Spell Check* (22) Spell Check* (22) Undo* (33) Toggle Set Leader Display *(20) Fix Graphics Preview* (31) Show Augmentation (1) Remap Error Msgs (6) Remove Stray XML Chars* (29) Item Text Search* (27) RTE Resizing** (14) Redesign Upload Link (16) Branch only of XML Tree (22) Remove Stray XML Chars* (29) Item Text Search* (27) Drop Down Prompts* (27) U s e r R e q u e s t s Implementation Cost A. “High Value, Low Cost” B. “High Value, Medium Cost” C. “Low Value, High Cost”
  19. 19. Electronic Surveys
  20. 20. Online Survey Tool
  21. 21. Sofware Satisfaction Results
  22. 22. Personas/Roles -> Activities
  23. 23. Activity – Menu Structures
  24. 24. Translation into Interface Design
  25. 25.  Create more customer feedback channels  “Client Council”  Locate all Team members close to each other  “Colocation”  Meet weekly all stakeholders  Multiple Face-to-Face weekly meetings Teams Talking to Each Other
  26. 26. Elite “Client Council” …
  27. 27. Weekly Face-to-Face Meetings with IT decision makers … IT Manager
  28. 28. Weekly with IT decision makers … and others IT Manager Marketing Manager Project Manager
  29. 29. Colocation – Near each other
  30. 30.  Be transparent in decision-making  Be straightforward and respectful in all dealings  Be considerate and flexible … and “play nice”
  31. 31. How to make a Masterpiece
  32. 32. You create one … by degrees
  33. 33. How to change the process  Change the development models from Waterfall to more Participative Decision-making  Get more stakeholders involved in decision-making  Collect “User Stories” … and document what they say  Bring Stakeholders together more frequently  Revise requirements … continually
  34. 34. Waterfall Development Model
  35. 35. Waterfall -> Iterative
  36. 36. Iterative and adding the new
  37. 37. Waterfall -> Iterative -> Sprint-like
  38. 38. Collect narrative “User Stories”
  39. 39. Documenting “User Stories”
  40. 40. A Chaotic Example
  41. 41. Adding Method to the Madness
  42. 42. More Egalitarian Relationships
  43. 43. Algonquin Hotel “Roundtable”
  44. 44. Group voting among equals
  45. 45. Wrap Up  Human communication helps create great software  Development Teams must speak with Users  Development Teams must speak among themselves  New software development models (agile; Lean UX) may help promote better communication and decision-making
  46. 46. If I can help …  “I help make computer systems easier for people to use”  Richard D. Herring  rdherring5@yahoo.com
  47. 47. Do you know what these are??
  48. 48. Mystery Object #1
  49. 49. Mystery Object #2
  50. 50. Mystery Object #3
  51. 51. Demonstrator Model
  52. 52. Mystery Object #4
  53. 53. Circa 1975 Announcement
  54. 54. Mystery Object #5

×