The Agile Manifesto captures "better ways of developing software" yet, could this better way also take the environmental, economic, and social footprints of your software into account?
For example, some forecasts project that in 2030 IT will account for 21% of all energy consumption. The software lifecycle creates direct and indirect carbon emissions: it has a footprint, worsening environmental problems. If we do not change the way we implement software, we will contribute to the increase in the carbon footprint.
However, the environmental aspect is not the only one we need to focus on. If we take sustainability seriously, we have to examine software development holistically from these three perspectives: social, economic, and environmental (as defined by the three pillar model).
In this workshop, we want to examine how agile development and sustainability can be combined for the greater good. In order to do so, we will explore how sustainability can be used as a quality criterion while developing products, and how a greater awareness can change our current way of working for providing our contribution to addressing climate change.
Thus, this session is about raising awareness of our contribution to greater sustainability and highlighting what our responsibility is and how we ensure that we take it into account.
