Empowered and embedded: ethics and agile processes

The paper addresses how to effectively integrate ethical deliberation into software development, contending that software artifacts embed values that shape human practices and social life. Because features, data practices, and opaque mechanisms can influence autonomy, fairness, and trust, ethical evaluation must include the software itself, not only its use. The authors propose that ethical deliberations—identifying, prioritizing, evaluating, and deciding on normative aspects—should be embedded in the development culture and processes. They argue agile processes are particularly apt due to their empowerment of developers, team-based collaboration, iterative delivery, and time-boxed decisions, thereby enabling techno-ethical judgment as part of routine engineering work.

The paper situates its argument within several strands: (a) persuasive technology, ambient intelligence, and ubiquitous computing highlighting autonomy and paternalism concerns; (b) embedded values and value sensitive design (VSD) traditions asserting that digital artifacts convey values warranting normative scrutiny; (c) technology assessment and ethical technology assessment (eTA), including VDI 3780 and IEEE P7000, focusing on competencies and procedures; (d) Codes of Ethics/Conduct as necessary but insufficient high-level guidance lacking conflict-resolution and context-sensitive application; (e) virtue ethics for IT (e.g., Vallor’s techno-moral virtues) emphasizing habituated moral practice across developers and users; (f) practical toolkits (e.g., ECCOLA cards) and frameworks (e.g., ETICA) that help surface issues but do not by themselves guide evaluative reasoning or decision closure; and (g) systems-theoretic accounts (Umbrello & Gambelin) aligning value-sensitive methods with agile. Collectively, prior work underscores the need for procedural integration of ethics into development while noting gaps in how, when, and by whom ethical deliberation is conducted.

This is a conceptual, normative-analytical paper. The authors develop a meta-theory of integrating ethical deliberation into software engineering by: (1) explicating techno-ethical judgment as a practice combining value identification (epistemic phase), evaluative prioritization (judgmental reasoning), and decision/closure (concluding phase); (2) grounding deliberation in rationality theory (coherence, consistency) and virtue ethics to foster techno-virtuous developer and team cultures; (3) adopting an embedded-values perspective to treat software features as carriers of normative claims; and (4) mapping these deliberative phases onto agile structures (Scrum roles and ceremonies) to embed ethics into standard workflows, documentation, and quality assurance (and potentially DevOps for lifecycle continuity). The argument then justifies, with conceptual and empirical support from the literature, five properties of agile that facilitate ethical deliberation: prevalence, autonomy via flat hierarchies, team participation, techno-ethical realism through iteration, and time-boxed endpoints.

Key claims/findings: 1) Agile is widely adopted, lowering transaction costs for integrating ethical deliberation: e.g., a survey reports 95% of organizations practice agile methods, and about 37% of teams in software engineering use agile (Digital.ai). Agile’s existing cadence of planning, review, and retrospectives provides insertion points for ethics discussions and documentation. 2) Flat hierarchies and empowerment promote autonomy, independent thinking, and responsibility among developers, prerequisites for techno-ethical judgment. Agile teams’ self-organization increases motivation, trust, and willingness to address ethical issues early. 3) Functioning, cross-functional teams and continuous knowledge sharing serve as incubators for ethical deliberation, reducing silos and enabling rational-discursive evaluation of values and trade-offs. 4) Iterative, incremental delivery supports techno-ethical realism: working software makes normative concerns tangible, localizable, and less speculative; requirements can be adjusted as ethical issues surface (e.g., privacy in big data contexts). 5) Time-boxed sprints create salient endpoints that counter endless deliberation; satisficing at aspiration levels enables practical, accountable decision-making with the option to revisit in subsequent sprints. Additional observations: Agile is no panacea—regulated contexts and large-scale systems can pose challenges (documentation, scaling, resource burdens), but agile still provides a promising procedural substrate for embedding ethics by design throughout the lifecycle (including DevOps).

Embedding ethical deliberation into agile addresses the central challenge of turning high-level principles and values into context-sensitive, actionable decisions during software development. Agile’s empowerment, team collaboration, and iterative delivery enable engineers to identify and prioritize values, link them to concrete design choices, and close deliberations within bounded time. This moves beyond principlism and checklist-based approaches by cultivating techno-ethical judgment as a professional habit. Grounding ethics in existing ceremonies, artifacts (backlogs, user stories), and documentation can normalize ethical reasoning and improve accountability. The approach aligns with embedded-values theory, virtue ethics, and systems thinking, and is especially relevant as software’s opacity and pervasiveness shape human practices. While not universally applicable (e.g., highly regulated domains), the framework offers a scalable path to foster ethically desirable outcomes and reduce late-stage moral risk and rework.

The paper argues that agile processes can effectively host and enhance ethical deliberation by leveraging their prevalence, autonomy-supporting structures, collaborative teams, iterative realism, and time-boxed decision points. Contributions include: (1) a conceptualization of techno-ethical judgment integrated into development culture; (2) justification for using agile as the procedural vehicle for embedding ethics; and (3) guidance on aligning deliberative phases with agile ceremonies and artifacts, extendable across the DevOps lifecycle. Future research is called for to empirically evaluate which agile ceremonies best support ethical deliberation, how to formalize procedures for generic and domain-specific ethical topics, how to document and monitor decisions, and how to sustain lifecycle oversight and updates to normative design.

The work is conceptual and lacks empirical validation of specific practices or impacts on outcomes. Agile methods are not universally suitable (e.g., regulated industries requiring extensive documentation, large-scale projects, or hierarchical cultures). Reported agile adoption levels may be overstated, and effective ethics integration still depends on management support, team maturity, and developer capability. Agile can burden teams with meetings, and scaling across interdependent teams is difficult. Availability of embedded ethicists is limited. The approach may not fully resolve conflicts among values or guarantee optimal outcomes, and it presumes organizational willingness to allocate time and resources to ethical deliberation.