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. 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 of the carbon footprint. This means it is about time to take another look at how agile development can help decrease energy consumption.

So, this session tries to provide the first answers to "how can the agile community and the agile principles contribute to or guide sustainability?" In this workshop, we want to examine how the principles of the Agile Manifesto can provide guidance for implementing sustainability in IT. In order to do so, we will explore how the principles can contribute to sustainability, and how a greater awareness can change our current way of working for providing our contribution to addressing climate change.