TL;DR: IEEE Std. 7000 meets Agile practices (note: access to IEEE Std. 7000 is free after registration for IEEE Xplore).
Quick links: (1) Story Valuation, (2) Ethical Review, (3) two-way Practice-Process Mappings (4) Glossary (5) FAQs
Ethical Software Engineering (ESE) is for you if:
- You see yourself as a socially responsible software engineer.
- You see the risk that the software under construction may have undesired and/or unexpected and/or unjustified effects for one or more of its stakeholder groups and want to manage and mitigate this risk.
- You look for a set of essential, as-light-as-possible practices that increase the chances of your project or product development effort becoming compliant with IEEE Std. 7000.
ESE targets any software engineer1 who wishes to create ethically valuable software, agile teams in particular. Its motivating themes are:
- Synergies: A value- and risk-based approach to design is very much at the heart of agile methods; for instance, Extreme Programming aims at balancing cost, time, quality and scope variables.
- Dual relation: Agile practices may promote social responsibility and ethical behavior, but may also harm ethical values. The devil is in the detail, software usage context matters.
- Novelty: The topic of ethical values has not been discussed much in Agile practices so far.2 The Agile Alliance has a Code of Conduct. And a blog post on coaching ethics made it to the top 10 of 2022 (Agile Alliance).
But what are ethical values? Our glossary references the definitions of the terms value and ethical value from IEEE Std. 7000; the Merriam-Webster Dictionary defines the term "ethic". The following figure shows three different meanings of the term "value", depending on the viewpoint taken:
For additional motivation for ethical software engineering and terminology clarification, please refer to "Are Programmers Ethically (and Legally) Responsible for Their Code?", an article by Jennifer Riggins on The New Stack (Aug 16, 2018).
ESE provides new and/or enhanced practices (i.e., activities and artifacts):
- Story Valuation activity, a good place to get started with ESE
- Ethical Review report and meeting
- Extended, value-enhanced Definition of Ready artifact
- Extended, value-enhanced Definition of Done artifact
- Value Retrospective activity, inspired by and complementing other forms of retrospectives.
Other folders and pages in this repository include:
- Roles directory (not fully populated at present)
- Experimentation instructions (method validation)
- Future work
Other content is linked in the directory-level index pages.
Working with ESE (the content of this repository) does not assume that you have read the IEEE Std. 7000 end to end. It is helpful but not required to be familiar with its concepts and processes; these are introduced and/or referenced as needed.
Experience with the Agile practices that ESE applies, extends or complements is welcome and useful but not strongly required; links and examples provide opportunities to catch up.
The Background Information page provides value comparisons and mappings from IEEE Std. 7000 to Agile concepts and practices (and back).
The Glossary defines and explains terms in IEEE Std. 7000, Agile, ESE.
A collection of Frequently Asked Questions (FAQs) is available.
See Bibliography page.
See experimentation folder and README.
January 13, 2024
ZIO aka Olaf Zimmermann
Bärbel Bohr, Mirko Stocker and Stefan Kapferer contributed to the ESE content via discussion input, experimenation and/or review feedback.
This work was funded by the Hasler Foundation.
Footnotes
-
We use the term "software engineer" in a broad sense here, including roles such as requirements engineer, architect, developer, tester, operator and maintainer. The entire software development lifecycle is in scope, with special emphasis on analysis and design. ↩
-
For instance, search for terms such as "ethics" on the website of the Agile Alliance. ↩