The document discusses how to better integrate user input and feedback into the software development process in a continuous and context-aware manner. It identifies issues with how user input is currently handled and proposes a continuous feedback model along with several technical enablers, like visual annotation tools and recommendation systems, to make user input a first-order concern in development. The goal is to help engineering teams get more direct and rich feedback from users to improve their applications.
6. Various types of user input ? Perpetual Beta Legacy Documents Usage Data Implicit Explicit Pull Push Issue and Bug Report Enhancement Request Feature Request Workshop Interview, Survey Clarification Request Field Observation Lead Users (Not used in SE) Communication Feedback
16. A Continuous Feedback Model Prospective Observation Assisted Feedback Improvement D ecision Back- Feedback Systematic Analysis Application User Engineering Team Development Infrastructure Community Sharing
18. Technical building blocks Visual Annotation Recommend end user to share their experience with engineering teams end other end users Observation & Context Elicitation Allow user to annotate and „paint“ on the GUI in the work context Proactive Assistance Detect user intention and problem situations through observation of user and application Making user input a 1 st order concern
19. TeamWeaver Context Framework problem problem Execution Ontology Interaction Ontoloy Feedback Reporting Interface OS sensors User Profile Elicitation Problem events update trigger A pplication sensors Execution Env. sensors A dditional feedback interact Session- ization Context Observer http://www.teamweaver.org
20. Visual Annotation with OpenProposal End user application http://www.openproposal.de OpenProposal plus Username, Application, Version, Date, etc. Issue Tracker
fast development cycles/reduce time-to implementation There are many studies, proving that the biggest problems in software projects lie in the requirement analysis, the first stage of every software project. The interviewed experts in the study of the Standish Group have the opinion that insufficient requirements are the biggest problem and that the involvement of customer and user is very important. This study was performed again in the last years and the results didn’t changed significantly.
Horizontal (user/dev) and vertical (iterations) gaps + user2user gap * Gap ** Actual distribution ** Media switches when sending requests (vs. feedback channels) ** Community interaction ** Difficult to monitor heterogeneous comm. streams
* back-feedback: ** customized release notes ** root updates in need
* Visual annotations: important, but only snapshot tools
* Proactive assistnce: ** Rate MR ** Extend help info ** Get recommendation for workaround