The Planet as Our Stakeholder - Slideshare (EN).pptx

The climate impact of IT and how to minimize it.

1. Planet Earth as Our Stakeholder

2. Planet Earth as Our Stakeholder What would you do differently if you considered the planet as your stakeholder? Marjolein Pilon Ambassador of Climate Awareness in IT Scrum Master

3. How do you feel about our planetary challenges?

4. The IT Carbon Footprint Data centers consume 1 to 2% of global energy usage Including production and lifecycle of devices IT consumes 4% of global energy usage 2030 forecast: IT will consume 8% of global energy usage 2040 forecast: IT will consume 14% of global energy usage Harvard Business Review.  https://hbr.org/2020/09/how-green-is-your-software

5. The IT Carbon Footprint The carbon footprint of IT is larger than that of aviation If the Internet were a country, it would be 7th on the list of largest polluters

6. The AI Footprint 2020- 2023 Google, Amazon, Microsoft: +62% rise in GHG emissions +78% rise in electricity usage

7. The Challenge Climate- neutrality must be achieved by 2050 In order to reach that goal we must cut carbon emissions by at least 55% in 2030

8. Era of Economic Growth Era of Regeneration Short Term Limitlessness Independence Consumption Long Term Balance Interdependence Sustainability Limitless data storage Maximum performance Short hardware lifecycles Value for customers Waste Green Architecture, Principles & Standards Tuned resource usage Sustainable culture Balanced value Minimized waste A New Era of IT Jump !

9. Learnings of Agile Teams

10. Balancing business needs against environmental impact 1. Ask new questions Add the same value but emit less carbon

11. 2. Get started

12. 3. Small steps Actions - Working on/ Recently done : Cleaned up old code and repos E2E tests run less often ( only 1x per day ) Kubernetes memory and CPU resources are reduced to minimum requirements Test and acceptance environments disabled outside office hours Reduce number of deployments (via commit message ) DONE ( by several Scrum Masters): Add planet as a stakeholder to the user story template Limit CI/CD Pipeline " DependaBot " Clean up unused AWS stuff & data Analysis: When are our services used ? Insight into current energy consumption team FAAM

13. Teams’ small steps for the planet Dutch Bank Getting rid of development environments that are not used. Stopped unnecessary load and stress tests. Optimized the use of log files. This resulted in significant savings. The policy was that they transfered log files to cold storage after a month. But they kept the application log on disk for sixty days. Analysis showed that they no longer consulted those log files and so they chose to remove them from disk after fifteen days. One team offers a document (PDF) in many places in our customer journeys. They always check how many pages the PDF has and place a text with a leaf icon next to the document stating how much CO2 the customer saves by storing it digitally. We built a pipeline that allows us to shut down the test environments and all the applications we have running during the night and on weekends. We have made this pipeline so generic and dynamic that other teams can easily reuse and configure the template. We have now found a way to run our Java applications server-less. We compile the code to machine code so that the application can sleep and start up very quickly when a user needs it. We do this using GraalVM . Disabled one of the acceptance environments, because it cost time and resources to roll out new software without any benefits. That saved 12 servers and 2 TB of data, so 5 tons of CO2 savings per year. One team developed a script that disables applications at times when they are not needed. Dutch Railway company Planned a digital clean-up day . Dutch Power Grid Company Discuss the impact on the planet in refinements Sustainable IT challenge during the PI planning. A data team at Enexis has adjusted a setting in their Data Warehouse, so that after 1 minute of inactivity the warehouse (virtual server on which queries are executed) shuts down, saving us 10% on credit consumption. At Enexis , teams also continue to switch off/transfer old systems to 1 new stack - and they are looking to get rid of multiple platforms.

14. 4. Integrate in WoW Definition of Done The code has been reviewed and the review comments have been processed . The code is in GIT. Feature branches have been merged to main and cleaned up. The code has been rolled out to Acceptance and Production . The acceptance criteria have been met technically and functionally . End- to -end test has been created and all end- to -end tests pass. With regard to energy consumption , unnecessary resources are identified and shut down. Incorrect documentation will be updated . Security checks have been carried out. Jira User Story Template User Story Description As [customer/user] I want [ functionality ] So that [ value ] Planet as a stakeholder What actions do we carry out to reduce our impact on the planet ? Acceptance Criteria When is this story completed ? Dependencies & Risks What dependencies do we have from other teams? What user stories must be completed before we can start this one ? Transparancy Energy use metrics Tag stories with positive impact Share progress in the Sprint Review

15. Principles and guidelines for a Green architecture Scrum Master Growing a culture of sustainability Coaching and facilitating the team in a green way of working Promoting the green vision , ambitions and practices Product Owner Expressing and promoting a vision on sustainability Prioritizing value for the environment Include the planet as a stakeholder Developers Self -managing for sustainable products Adding green practices and tooling to the development standards Building and sharing knowledge on sustainable IT practices Sustainable product development & innovation Sustainability in value creation Sustainability in IT Sustainable Scrum Team Vision on sustainable value Providing value metrics for business sustainability Providing climate impact metrics Providing green tooling A vision and ambitions on sustainable IT Climate impact in Sprint Review & Retrospective Climate impact in Definition of Done Value for environment in Backlog Green IT Organization Embedding Green Ways of Working in the (IT) Org Visionary leadership Structure Team autonomy Continuous improvement

16. Interaction Round 1: Brainstorm What is needed to halve your company’s IT carbon footprint by 2030? Write your ideas on post-its (1 idea per post-it) Discuss your ideas with your table Plenary : present 2 or 3 ideas to the group Round 2: Circle of Influence How can you contribute from your role? Plot your ideas in the circle of control - influence - concern Discuss with your table: Which ideas in the outer circle(s) can you make smaller (or reformulate) and thus shift into your sphere of influence/control? Share your findings in plenary Round 3: First Steps What first steps can you take? Write your personal first steps Share them on the wall Don’t forget to write them for yourself and take them home!

17. Think big, start small Exchange with your neighbour : “How can the QA Test community help cut the IT carbon emissions ?” “ What are some small steps that you can take tomorrow ?” My flight (Amsterdam- Bilbao) emitted 270 kg CO₂. That is comparable to : 300 GB of log files stored for a year . Running 1 server for about 3-4 months

18. New perspective Deep Democracy

19. Inspiration & Resources https :// www.jeckstein.com / sustainability / https :// www.comparativeagility.com / capabilities /agile- sustainability -assessment/ https :// theplanetasastakeholder.com / materials /

20. Join the movement ! World Work