Determining relevancy: how software developers determine relevant information in feeds

Authors:
Thomas Fritz;Gail C. Murphy
Affiliations:
University of British Columbia, Vancouver, British Columbia, Canada;University of British Columbia, Vancouver, British Columbia, Canada
Venue:
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Year:
2011

Citing 6
Cited 1

E-mail as habitat: an exploration of embedded personal information management

interactions
Palantír: raising awareness among configuration management workspaces

Proceedings of the 25th International Conference on Software Engineering
Understanding email use: predicting action on a message

Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Short and tweet: experiments on recommending content from information streams

Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Using information fragments to answer the questions developers ask

Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Awareness 2.0: staying aware of projects, developers and tasks using dashboards and feeds

Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1

On the perceived interdependence and information sharing inhibitions of enterprise software engineers

Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work

Quantified Score

Hi-index	0.01

Visualization

Abstract

Finding relevant information within the vast amount of information exchanged via feeds is difficult. Previous research into this problem has largely focused on recommending relevant information based on topicality. By not considering individual and situational factors these approaches fall short. Through a formative, interview-based study, we explored how five software developers determined relevancy of items in two kinds of project news feeds. We identified four factors that the developers used to help determine relevancy and found that placement of items in source code and team contexts can ease the determination of relevancy.