一句话：通过10个真实软件团队5个月至3.5年的实践，总结GenderMag落地为9项实践、2个陷阱和2个开放问题。
尽管软件中的性别包容性日益受到软件工程研究者与实践者关注，且已有GenderMag等方法，但关于这些方法如何在真实团队中落地仍鲜有报道。真实团队需要权衡新增方法的实际成本，例如时间投入是否可行、如何扩大影响，以及讨论性别时可能引发的争议。为回答这些问题，作者收集了10个真实软件团队、超过50人、持续5个月到3.5年的基于GenderMag的过程数据。文章以9项实践、2个潜在陷阱和2个开放问题的形式呈现这些团队的经验与洞见，供其他希望将性别包容性工程化融入软件产品的真实团队参考。
Although the need for gender-inclusivity in software is gaining attention among SE researchers and SE practitioners, and at least one method (GenderMag) has been published to help, little has been reported on how to make such methods work in real-world settings. Real-world teams are ever-mindful of the practicalities of adding new methods on top of their existing processes. For example, how can they keep the time costs viable? How can they maximize impacts of using it? What about controversies that can arise in talking about gender? To find out how software teams "in the trenches" handle these and similar questions, we collected the GenderMag-based processes of 10 real-world software teams---more than 50 people---for periods ranging from 5 months to 3.5 years. We present these teams' insights and experiences in the form of 9 practices, 2 potential pitfalls, and 2 open issues, so as to provide their insights to other real-world software teams trying to engineer gender-inclusivity into their software products.
DOI 原文 ·
@inproceedings{paperbot5563,
title = {Engineering gender-inclusivity into software},
author = {Claudia Hilderbrand and Christopher Perdriau and Lara Letaw and Jillian Emard and Zoe Steine-Hanson and Margaret Burnett and Anita Sarma},
booktitle = {ICSE},
year = {2020},
doi = {10.1145/3377811.3380371}
}