Home > Research > Publications & Outputs > A Case for Human Values in Software Engineering

Electronic data

  • 08917668

    Rights statement: ©2019 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.

    Accepted author manuscript, 422 KB, PDF document

    Available under license: CC BY-NC: Creative Commons Attribution-NonCommercial 4.0 International License

Links

Text available via DOI:

View graph of relations

A Case for Human Values in Software Engineering

Research output: Contribution to journalJournal articlepeer-review

E-pub ahead of print
<mark>Journal publication date</mark>28/11/2019
<mark>Journal</mark>IEEE Software
Publication StatusE-pub ahead of print
Early online date28/11/19
<mark>Original language</mark>English

Abstract

This article argues that human values – such as responsibility, transparency, creativity, and equality – are heavily under-represented in software engineering methods. Based on experiences with real-world projects with not-for-profits, we explore how human values can be integrated into existing participatory agile practices. We propose new ways of considering human values in software practice, including: the use of the Schwartz taxonomy of human values and values portraits to contextualise values definitions; the use of values as a way to capture the rationale for requirements to ensure a culture of values throughout the software lifecycle; and a simple adaptation of agile methods to include a role for a ‘critical friend’ who can champion values during decision making.

Bibliographic note

©2019 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.