1 / 19

HCI Masters Project Course

HCI Masters Project Course. PSLC Project Phase 2 Report. What the project is about. Work Updates. Data Collection. We collected more data CTAT Winter Workshop More Contextual Inquiries 4 focus areas high-level analysis tools (curves)

azuka
Télécharger la présentation

HCI Masters Project Course

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HCI Masters Project Course PSLC Project Phase 2 Report

  2. What the project is about

  3. Work Updates

  4. Data Collection • We collected more data • CTAT Winter Workshop • More Contextual Inquiries • 4 focus areas • high-level analysis tools (curves) • low-level drilling bits (logfiles visualizations, Knight graphs) • Exporting function • Multi-user issues • finding datasets of interest • access and permissions • social networking

  5. Scenarios • PSLC Primary Investigators (2) • PSLC Research Programmer • Student of PSLC PI • PSLC Member • Non-member Researcher/Grad student

  6. Initial Prototyping • Focused on one of the scenarios (Primary Investigator) • Did sketches of ideas • Consolidated ideas and made initial wire-frames

  7. Lessons Learnt • Need to have correct focus • CIs may not tell you what the client wants. • Informed data means more later on. Need context to understand early stuff • Need to talk to all stakeholders. • Conclusion: There are standard (curves) reports and we don't know how they work.

  8. What’s Next

  9. What’s Next: Refocus • Invited client to affinity diagramming • Organized design ideas • Built shared understanding • Got valuable feedback on idea groups, BUT • Missing details on LearnLab analysis tools • Needed to focus more on designing analysis tools

  10. What’s Next New Development Plan • Identify highest priorities • Interview client stakeholders • Serialize research and prototyping • Split up the group into subteams

  11. Four foci High-level analysis tools Low-level tools analysis Exporting function Multi-user issues Development Plan Why change course? Need more data for about 8 analysis tools Integrate and adapt 2 borrowed designs Should be easy to design quickly

  12. Development Plan Serialize research and prototyping What is this? Pick highest priority analysis tool or feature. Do an entire design/test/build cycle on it. Move on to next tool.

  13. Development Plan Interviews with client stakeholders • CI data didn’t address focus • Didn’t see needs for client solution • Client solution not obviously applicable • Lacked understanding of client solution • Analysis tools needed for collaboration • Need to understand analysis techniques. • Talking client stakeholders is fast

  14. Development Plan Serialize research and prototyping • Prototype hard stuff early. • Concrete stuff required for June seminar • Client will be coding features • Work more closely with client • Build better partnership

  15. Development Plan Splitting up into sub-teams • Spread resources • How it will work: • Pick a set of features or tools • Assign one team to do R&D • User testing by other team • Rework and hand off final design to client • Pick next feature set to work on • Still workingthis out

  16. Development Plan Next actions • Think-Aloud on existing prototype of an analysis tool • CI to gather data for an upcoming tool • More research on LearnLab analysis tools

  17. Potholes We Ran Into (and How We Got Around them)

  18. Problems • Methods approach exhausted • Solution: breakaway from data if it makes sense • Getting requirements when clients are only current users of a feature • Solution: Use client stakeholders for CI’s • Additional CI's adding marginal value • Solution: Prototype and test

  19. Feedback • New development plan • Soliciting requirements without hypothetical questions? • Anything else you have comments on

More Related