diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ee4ea9c..4ced8ce 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,12 +3,12 @@ First off, thanks for taking the time to contribute! ❤️ -All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉 +All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it much easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉 -> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about: +> And if you like the project but don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about: > - Star the project > - Tweet about it -> - Refer this project in your project's readme +> - Refer to this project in your project's readme > - Mention the project at local meetups and tell your friends/colleagues @@ -16,30 +16,30 @@ All types of contributions are encouraged and valued. See the [Table of Contents - [I Have a Question](#i-have-a-question) - [I Want To Contribute](#i-want-to-contribute) - - [Reporting Bugs](#reporting-bugs) - - [Suggesting Enhancements](#suggesting-enhancements) +  - [Reporting Bugs](#reporting-bugs) +  - [Suggesting Enhancements](#suggesting-enhancements) - [Editing Content](#editing-content) - [Developing Locally](#developing-locally) - [Join The Project Team](#join-the-project-team) ## I Have a Question -> If you want to ask a question, we assume that you have read the available [Documentation](https://greensoftwarefoundation.atlassian.net/wiki/spaces/~612dd45e45cd76006a84071a/pages/82214913/Community+Green+Maturity+Matrix). +> If you want to ask a question, we assume that you have read the available [documentation](https://greensoftwarefoundation.atlassian.net/wiki/spaces/~612dd45e45cd76006a84071a/pages/82214913/Community+Green+Maturity+Matrix). -Before you ask a question, it is best to search for existing [Issues](https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first. +Before you ask a question, it is best to search for existing [Issues](https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues) that might help you. If you have found a suitable issue and still need clarification, you can write your question about this issue. It is also advisable to search the internet for answers first. If you then still feel the need to ask a question and need clarification, we recommend the following: - Open an [Issue](https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues/new). -- Provide as much context as you can about what you're running into. -- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant. +- Provide as much context as possible about what you're running into. +- Provide project and platform versions (Node.js, npm, etc), depending on what seems relevant. We will then take care of the issue as soon as possible. -> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license. +> When contributing to this project, you must agree that you have authored 100% of the content, you have the necessary rights to the content, and that the content you contribute may be provided under the project license. ### Suggesting Enhancements -This section guides you through submitting an enhancement suggestion for Green Software Maturity Matrix, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions. +This section guides you through submitting an enhancement suggestion for Green Software Maturity Matrix, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community understand your suggestions and find related suggestions. #### Before Submitting an Enhancement @@ -66,40 +66,40 @@ This section guides you through submitting an enhancement suggestion for Green S - Make sure that you are using the latest version. - Read the [documentation](https://greensoftwarefoundation.atlassian.net/wiki/spaces/~612dd45e45cd76006a84071a/pages/82214913/Community+Green+Maturity+Matrix) carefully and find out if the functionality is already covered, maybe by an individual configuration. - Perform a [search](https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. -- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library. +- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a solid case to convince the project's developers of the merits of this feature. Remember that we want features that will be useful to most of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library. #### How Do I Submit a Good Enhancement Suggestion? Enhancement suggestions are tracked as [GitHub issues](https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues). -- Use a **clear and descriptive title** for the issue to identify the suggestion. +- Identify the suggestion by using a **clear and descriptive title** for the issue. - Provide a **step-by-step description of the suggested enhancement** in as many details as possible. -- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you. -- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. +- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point, you can also tell which alternatives do not work for you. +- You may **include screenshots and animated GIFs** that help you demonstrate the steps or point out the part to which the suggestion is related. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. - **Explain why this enhancement would be useful** to most Green Software Maturity Matrix users. You may also want to point out the other projects that solved it better and which could serve as inspiration. - + ## Editing Content -This project is a static website based on the project https://docusaurus.io, you can find more information about docusaurus here: https://docusaurus.io/docs +This project is a static website based on the project [docusaurus](https://docusaurus.io). You can find more information about docusaurus here in the [docs](https://docusaurus.io/docs) -The `docs` folder contains all of the material in this project, editing any file there in the `main` branch will update the website. If you are only interested in editing content on the website then you should not need to leave the `docs` folder. +The `docs` folder contains all of the material in this project. Editing any file in the `main` branch will update the website. If you are only interested in editing content on the website, then you should not need to leave the `docs` folder. -The documentation files use a format called markdown and they end in `.md` which supports certain basic styling features like so: https://docusaurus.io/docs/markdown-features +The documentation files use a markdown format, with files ending in `.md`. These files support [certain basic styling features](https://docusaurus.io/docs/markdown-features). ## Developing Locally -To edit this project on your local machine and see the output as it would be rendered on the website you will need `node` at least version 14 installed. +To edit this project on your local machine and see the output as it would be rendered on the website you will need `node` at least version 18 installed. -We also recommend to use `yarn` as the package management solution as the deployment scripts use `yarn` not `npm`. +We also recommend using `yarn` as the package management solution, as the deployment scripts use `yarn` instead of `npm`. `npm -g install yarn` `yarn install` -Then to run the project locally type +Then, to run the project locally, type `yarn run docusaurus start` diff --git a/README.md b/README.md index b71c77f..ce4c78a 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Green Software Maturity Matrix -The Green Software Maturity Matrix is a self-assessment tool. It helps organisations understand the extent to which they have implemented green principles, patterns, and processes for building and operating their software systems. +The Green Software Maturity Matrix is a self-assessment tool. It helps organizations understand the extent to which they have implemented green principles, patterns, and processes for building and operating their software systems. This project is run through the [Community Working Group](https://grnsft.org/community-wg) in the [Green Software Foundation](https://greensoftware.foundation). @@ -18,11 +18,11 @@ The matrix addresses four problems. It answers the questions: This project entered the Green Software Foundation as a Draft on 27 October 2023. -> **This is a draft document only and has not been approved or adopted by the Green Software Foundation. this draft may not be relied upon for any purpose other than review of the current state of development.** +> **This is a draft document and has not been approved or adopted by the Green Software Foundation. This draft may not be relied upon for any purpose other than to review the current state of development.** ## Appointments -The project is lead by: +The project is led by: * [Anne Currie](https://github.com/aecurrie) * [Pini Reznik](https://github.com/pinireznik) @@ -31,6 +31,6 @@ The project is lead by: [Creative Commons Attribution 4.0](https://creativecommons.org/licenses/by/4.0/). ## Contributing -This project is open source and welcomes public contribution via issues, discussions and pull requests. +This project is open source and welcomes public contributions via issues, discussions, and pull requests. -Instructions for how to contribute to this project can be found in the [CONTRIBUTING.md](CONTRIBUTING.md) file. +The [CONTRIBUTING.md](CONTRIBUTING.md) file contains instructions for contributing to this project. diff --git a/SCOPE.md b/SCOPE.md index 964d81e..d3d0f0f 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -1,14 +1,14 @@ # Scope -The Green Software Maturity Matrix is a self-assessment tool. It helps organisations understand the extent to which they have implemented green principles, patterns, and processes for building and operating their software systems. +The Green Software Maturity Matrix is a self-assessment tool. It helps organizations understand the extent to which they have implemented green principles, patterns, and processes for building and operating their software systems. The matrix addresses four problems. It answers the questions: -* **"Where do I start?"** - for enterprises at level 1 of the GSMM, which tools and projects are available to help then achieve level 2 +* **"Where do I start?"** - for enterprises at level 1 of the GSMM, which tools and projects are available to help them achieve level 2 * **"Where am I now?"** - by using the checklists of the GSMM, enterprises can establish which level of the GSMM they are currently at for different axes * **"What am I heading towards?"** - by establishing their current level, they can understand what is a realistic next milestone -* **"How do I know I am making progress?"** - by tracking their progress they can check they are not stuck +* **"How do I know I am making progress?"** - by tracking their progress, they can check they are not stuck # Target Audience @@ -17,11 +17,11 @@ The matrix addresses four problems. It answers the questions: # Solution -A simple maturity matrix with 5-6 levels of carbon efficiency and awareness in a poster-style diagram, together with a short guide. Training courses including those offered by the GSF, and standards such as the SCI & ISO can be overlaid. +A simple maturity matrix with 5-6 levels of carbon efficiency and awareness in a poster-style diagram, together with a short guide. Training courses, including those offered by the GSF, and standards such as the SCI & ISO can be overlaid. # Objectives * Get all GSF Members to start reporting (at least internally) on their GSMM scores and progress on a company or org unit basis. -* Provide high level context and a way into the other projects of the GSF including the TOSS project and the patterns +* Provide high-level context and a way into the other projects of the GSF, including the TOSS project and the patterns # Deliverables @@ -34,13 +34,13 @@ A simple maturity matrix with 5-6 levels of carbon efficiency and awareness in a ## OKRs -Allow any organisation to understand their current green software maturity and know how to actively improve it -* KR: Number of orgs who have self-assessed / adopted standard? +Allow any organization to understand their current green software maturity and know how to actively improve it +* KR: What is the number of organizations that have self-assessed / adopted the standard? * KR: Digital badges issued? -* KR: Number of organisations who have moved levels? +* KR: What is the number of organizations that have moved levels? ## KPIs -* Online references / backlinks? +* Online references/backlinks? * Material downloads? * Case studies? * Demand for training? @@ -53,4 +53,4 @@ Allow any organisation to understand their current green software maturity and k * Q1 2024 - GSF Project Initiation * Q2 2024 - v1.0 Community Working Group approval * Q3 2024 - v1.0 Steering Committee ratification -* Q4 2024 - ? \ No newline at end of file +* Q4 2024 - ? diff --git a/docs/gsmm/index.md b/docs/gsmm/index.md index 284c6d7..59f496b 100644 --- a/docs/gsmm/index.md +++ b/docs/gsmm/index.md @@ -7,25 +7,25 @@ sidebar_label: Green Maturity Matrix # A Green Software Maturity Matrix -What does this mean in a green software context for an organization? Let’s be realistic. Almost all enterprises are at level 1 right now. Going green is the most difficult project our industry faces. +What does this mean for an organization in the green software context? Let's be realistic. Almost all enterprises are at level 1 right now. Going green is the most challenging project our industry faces. [![Green Software Maturity Matrix!](/img/maturity-matrix.svg "Green Software Maturity Matrix")](/img/maturity-matrix.svg) ## Level 1 - Aspiring -You have individuals in your organization who care about green targets for technology but no systemic interest, processes or commitments. Some development teams measure their carbon emissions. This is where almost all of us are today. +You have individuals in your organization who care about green technology targets but have no systemic interest, processes, or commitments. Some development teams measure their carbon emissions. This is where almost all of us are today. ## Level 2 - Aware -You know your organization’s scope 1 and 2 emissions. You have a few projects driving greenness within your organization and beyond it using this data (by putting pressure on suppliers, for example). Your engineers have had some training in green systems, operations and patterns. +You know your organization's scope 1 and 2 emissions. You have a few projects using this data to drive greenness within and beyond your organization (by putting pressure on suppliers, for example). Your engineers have had some training in green systems, operations, and patterns. ## Level 3 - Acting -You know your scope 1, 2 and 3 emissions on a daily, weekly, monthly or annual basis. You have been acting on reducing the scope 1 and 2 emissions for a while and your carbon footprint is going down per some consistent, org-specific unit of output, e.g per order. You have defined processes for every team including regular reporting and reviewing of CO2 equivalent emissions for all IT related operations. Your PM teams have a remit to avoid waste, for example saving no more data than is necessary or implementing any functionality before need, and you can switch off zombie or low use services immediately (“Lightswitch Ops”). You have automatic resilience to weather-related operational risks (e.g. DC outages). You are aware of and discuss the tradeoffs between embodied carbon and carbon generated by energy usage. You have plans in place to minimize your embodied carbon footprint, including significantly extending the life expectancy of both the servers and end user devices you run on. +You know your scope 1, 2, and 3 emissions on a daily, weekly, monthly, or annual basis. You have been acting on reducing the scope 1 and 2 emissions for a while, and your carbon footprint is going down per some consistent, org-specific unit of output, e.g., per order. You have defined processes for every team, including regular reporting and reviewing of CO2 equivalent emissions for all IT-related operations. Your PM teams have a remit to avoid waste, for example, saving no more data than is necessary or implementing any functionality before needed, and you can switch off zombie or low-use services immediately ("Lightswitch Ops"). You have automatic resilience to weather-related operational risks (e.g., DC outages). You are aware of and discuss the tradeoffs between embodied carbon and carbon generated by energy usage. You have plans in place to minimize your embodied carbon footprint, including significantly extending the life expectancy of both the servers and end-user devices you run on. ## Level 4 - Awesome -You have a measurement system in place that is producing good real-time scope 1, 2, and 3 data and although it’s not currently driving the business day-to-day, the business is very aware of it. Using the more limited scope 1, 2, and 3 data you have had for a while, you have already achieved net carbon zero using no more than 10% offsets. (Note offsets are highly problematic but they demonstrate you are regularly measuring). You perform demand shaping; pre-calculation and caching; and time and location shifting, for example, to adapt your workloads to current conditions. You automatically delete or archive data that isn’t in regular use. Services no longer in use are automatically turned off and rightsizing happens automatically (i.e. you apply SRE principles). Your applications are Lean and you constantly review and retire functionality that is insufficiently used. Your organizational strategy has been aligned with being green as a business goal - perhaps for reasons of ESG, cost, resilience, or market access to the EU - and delivery on CO2 targets is regularly discussed and reported at senior level. Your total carbon footprint is going down even as you grow. You are also actively driving the carbon footprint of your suppliers to go down. You never cause hardware less than ten years old to become end of life either by lack of security patches or lack of backwards compatibility in your applications. You are actively driving the carbon footprint of your customers to go down (beyond simply their use of your services and devices) for example by providing scope 3 reporting for your goods and services. Examples (for some of it): Google, AWS, MS. +You have a measurement system in place that produces good real-time scope 1, 2, and 3 data, and although it's not currently driving the business day-to-day, the business is very aware of it. Using the more limited scope 1, 2, and 3 data you have had for a while, you have already achieved net carbon zero using no more than 10% offsets. (Note offsets are highly problematic, but they demonstrate that you are regularly measuring.) You perform demand shaping, pre-calculation, caching, and time and location shifting, for example, to adapt your workloads to current conditions. You automatically delete or archive data that isn't in regular use. Services no longer in use are automatically turned off, and rightsizing happens automatically (i.e., you apply SRE principles). Your applications are Lean, and you constantly review and retire insufficiently used functionality. Your organizational strategy has been aligned with being green as a business goal - perhaps for reasons of ESG, cost, resilience, or market access to the EU - and delivery on CO2 targets is regularly discussed and reported at the senior level. Your total carbon footprint is going down even as you grow. You are also actively driving your suppliers' carbon footprint down. You never cause hardware less than ten years old to become the end of life either by lack of security patches or lack of backward compatibility in your applications. You are actively driving the carbon footprint of your customers to go down (beyond simply their use of your services and devices), for example, by providing scope 3 reporting for your goods and services. Examples (for some of it): Google, AWS, MS. ## Level 5 - Inspiring -You’ve got there. You have achieved 24/7 CFE and require no more than 1% offsets to handle hard to shift embodied carbon. You have team level measurable goals (OKRs etc) for your CO2 measurements. You are optimizing for minimal CO2 emissions using your dynamic, real-time data. You and the services you rely on use real-time information including dynamic grid energy data to make rapid, quantitative decisions that allow you to be greener. This could (and probably will) be via a service you use rather than something you built yourself. You are already an SRE-aware organization that thinks in terms of [error budgets](https://cloud.google.com/blog/products/management-tools/sre-error-budgets-and-maintenance-windows) for outages and downtime and you now think about carbon budgets in the same way. Using predictions based on factors such as weather and grid congestion, you change and move almost all of your workloads ahead of time to match your electricity requirements to local green power availability (aka 24/7 CFE) and any time sensitive workloads are highly optimized for minimal electricity use. You never cause hardware to become end of life either by lack of security patches or lack of backwards compatibility. You are ready for the energy transition and won’t be caught by surprise by sudden new rules or constraints. +You've got there. You have achieved 24/7 CFE and require no more than 1% offsets to handle hard-to-shift embodied carbon. You have team-level measurable goals (OKRs, etc) for your CO2 measurements. You are optimizing for minimal CO2 emissions using your dynamic, real-time data. You and the services you rely on use real-time information, including dynamic grid energy data, to make rapid, quantitative decisions that allow you to be greener. This could (and probably will) be via a service you use rather than something you built yourself. You are already an SRE-aware organization that thinks in terms of [error budgets](https://cloud.google.com/blog/products/management-tools/sre-error-budgets-and-maintenance-windows) for outages and downtime, and you now think about carbon budgets in the same way. Using predictions based on factors such as weather and grid congestion, you change and move almost all of your workloads ahead of time to match your electricity requirements to local green power availability (aka 24/7 CFE), and any time-sensitive workloads are highly optimized for minimal electricity use. You never cause hardware to become end-of-life either by a lack of security patches or a lack of backward compatibility. You are ready for the energy transition and won't be caught by surprise by sudden new rules or constraints.
@@ -36,7 +36,7 @@ You’ve got there. You have achieved 24/7 CFE and require no more than 1% offse * CO2 equivalent metrics * Server resource management * Energy resource management -* Minimize end user device embodied carbon waste (assume circular economy) +* Minimize end-user device embodied carbon waste (assume circular economy) * Minimize server hardware embodied carbon waste * Product management * Education @@ -46,4 +46,4 @@ You’ve got there. You have achieved 24/7 CFE and require no more than 1% offse ## Scope * **Small business:** Maturity matrix per company * **Small and Midsize Enterprise (SME):** Maturity matrix per company -* **Larger organization:** Maturity matrix per business unit rather than per company \ No newline at end of file +* **Larger Organization:** Maturity matrix per business unit rather than per company diff --git a/docs/gsmm/level-1.md b/docs/gsmm/level-1.md index 1074049..dcd09ae 100644 --- a/docs/gsmm/level-1.md +++ b/docs/gsmm/level-1.md @@ -6,16 +6,16 @@ sidebar_label: Level 1 # Level 1 - Aspiring -You have individuals in your organization who care about green targets for technology but no systemic interest, processes or commitments. Some development teams measure their carbon emissions. This is where almost all of us are today. +You have individuals in your organization who care about green technology targets but have no systemic interest, processes, or commitments. Some development teams measure their carbon emissions. This is where almost all of us are today. -| Axis | State | +| Axis      | State | | ----------- | ----------- | -| Whole organization energy commitments | none/CZero by 2050 | -| Carbon footprint | you don’t know what it is | +| Whole organization energy commitments | None/net carbon zero by 2050 | +| Carbon footprint | You don’t know what it is | | CO2 equivalent metrics | No metrics | -| Server resource management | No rightsizing takes place and zero knowledge about unused ”zombie” systems | +| Server resource management | No rightsizing takes place, and zero knowledge about unused ”zombie” systems | | Energy resource management | None - running on demand | -| Minimize end user device embodied carbon waste (assume circular economy) | No end user device longevity targets | +| Minimize end-user device embodied carbon waste (assume circular economy) | No end-user device longevity targets | | Minimize server hardware embodied carbon waste | No server utilization targets | | Product management | Not carbon aware | -| Education | None/ad-hoc, individual | \ No newline at end of file +| Education | None/ad-hoc, individual | diff --git a/docs/gsmm/level-2.md b/docs/gsmm/level-2.md index 8c12b0b..a855904 100644 --- a/docs/gsmm/level-2.md +++ b/docs/gsmm/level-2.md @@ -6,16 +6,16 @@ sidebar_label: Level 2 # Level 2 - Aware -You know your organization’s scope 1 and 2 emissions. You have a few projects driving greenness within your organization and beyond it using this data (by putting pressure on suppliers, for example). Your engineers have had some training in green systems, operations and patterns. +You know your organization's scope 1 and 2 emissions. You have a few projects using this data to drive greenness within and beyond your organization (by putting pressure on suppliers, for example). Your engineers have had some training in green systems, operations, and patterns. -| Axis | State | +| Axis      | State | | ----------- | ----------- | -| Whole organization energy commitments | CZero for scope 1, 2 and 3 by 2040 (note you may already be so-called “Carbon neutral”) | -| Carbon footprint | you know what it is (scope 1 and 2) | -| CO2 equivalent metrics | annual, quarterly or monthly numbers from all suppliers (including outsourcers) and own systems for scope 1/2 | -| Server resource management | occasional spring cleans where you manually turn off idle or low value systems and delete/archive unneeded data | -| Energy resource management | hosting in green regions/buying renewable energy | -| Minimize end user device embodied carbon waste (assume circular economy) | some adhoc targets in place | -| Minimize server hardware embodied carbon waste | some adhoc systems and some systems using multi-tenancy to improve utilization | -| Product management | carbon awareness part of product design | -| Education | basic training for all engineers & PMs. Champions are trained | \ No newline at end of file +| Whole organization energy commitments | Net carbon zero for scope 1, 2, and 3 by 2040 (note you may already be so-called "Carbon neutral") | +| Carbon footprint | You know what it is (scope 1 and 2) | +| CO2 equivalent metrics | Annual, quarterly, or monthly numbers from all suppliers (including outsourcers) and own systems for scope 1/2 | +| Server resource management | Occasional spring cleans where you manually turn off idle or low-value systems and delete/archive unneeded data | +| Energy resource management | Hosting in green regions/buying renewable energy | +| Minimize end-user device embodied carbon waste (assume circular economy) | Some ad-hoc targets in place | +| Minimize server hardware embodied carbon waste | Some ad-hoc systems and some systems using multi-tenancy to improve utilization | +| Product management | Carbon awareness part of product design | +| Education | Basic training for all engineers & PMs. Champions are trained | \ No newline at end of file diff --git a/docs/gsmm/level-3.md b/docs/gsmm/level-3.md index ebf4bda..669e9a7 100644 --- a/docs/gsmm/level-3.md +++ b/docs/gsmm/level-3.md @@ -6,16 +6,16 @@ sidebar_label: Level 3 # Level 3 - Acting -You know your scope 1, 2 and 3 emissions on a daily, weekly, monthly or annual basis. You have been acting on reducing the scope 1 and 2 emissions for a while and your carbon footprint is going down per some consistent, org-specific unit of output, e.g per order. You have defined processes for every team including regular reporting and reviewing of CO2 equivalent emissions for all IT related operations. Your PM teams have a remit to avoid waste, for example saving no more data than is necessary or implementing any functionality before need, and you can switch off zombie or low use services immediately (“Lightswitch Ops”). You have automatic resilience to weather-related operational risks (e.g. DC outages). You are aware of and discuss the tradeoffs between embodied carbon and carbon generated by energy usage. You have plans in place to minimize your embodied carbon footprint, including significantly extending the life expectancy of both the servers and end user devices you run on. +You have been acting on reducing the scope 1 and 2 emissions for a while, and your carbon footprint is going down per some consistent, org-specific unit of output, e.g., per order. You have defined processes for every team, including regular reporting and reviewing of CO2 equivalent emissions for all IT-related operations. Your PM teams have a remit to avoid waste, for example, saving no more data than is necessary or implementing any functionality before needed, and you can switch off zombie or low-use services immediately ("Lightswitch Ops"). You have automatic resilience to weather-related operational risks (e.g., DC outages). You are aware of and discuss the tradeoffs between embodied carbon and carbon generated by energy usage. You have plans in place to minimize your embodied carbon footprint, including significantly extending the life expectancy of both the servers and end-user devices you run on. -| Axis | State | +| Axis      | State | | ----------- | ----------- | -| Whole organization energy commitments | already net CZero with offsets | -| Carbon footprint | you know what it is (scope 1, 2 and 3) and it is reducing per unit of output, e.g. orders | +| Whole organization energy commitments | already net carbon zero with offsets | +| Carbon footprint | You know what it is (scope 1, 2, and 3), and it is reducing per unit of output, e.g., orders | | CO2 equivalent metrics | daily numbers from all suppliers and own systems for scope 1/2/3 and embodied carbon | -| Server resource management | all systems can be safely switched off (aka Lightswitch Ops) and there are processes for doing so. You have knowledge of what is running on all your machines and there are no zombie services. You save no unnecessary data and it is maintained in the optimal medium (e.g. tape if the data is not required for real time queries) | -| Energy resource management | at least part of your systems are dynamically managed based on green electricity availability (either via direct orchestration or through a cloud service) | -| Minimize end user device embodied carbon waste (assume circular economy) | defined processes in place that ensure ten year old hardware is supported by your software for most commonly used devices (90%+) | -| Minimize server hardware embodied carbon waste | defined utilization targets. All systems use some form of multi-tenancy. Servers all have a 5 year life expectancy | -| Product management | all new product design supports demand shifting/shaping and Lean concepts are followed. End user devices prompt for green/off peak charging. No more data is saved than necessary | -| Education | advanced training for all engineers & PMs | \ No newline at end of file +| Server resource management | All systems can be safely switched off (aka Lightswitch Ops), and there are processes for doing so. You know what is running on all your machines, and there are no zombie services. You save no unnecessary data, and it is maintained in the optimal medium (e.g., tape if the data is not required for real-time queries) | +| Energy resource management | At least part of your systems are dynamically managed based on green electricity availability (either via direct orchestration or through a cloud service) | +| Minimize end-user device embodied carbon waste (assume circular economy) | Defined processes in place that ensure ten-year-old hardware is supported by your software for most commonly used devices (90%+) | +| Minimize server hardware embodied carbon waste | Defined utilization targets. All systems use some form of multi-tenancy. Servers all have a five-year life expectancy | +| Product management | All new product designs support demand shifting/shaping, and Lean concepts are followed. End-user devices prompt for green/off-peak charging. No more data is saved than necessary | +| Education | advanced training for all engineers & PMs | diff --git a/docs/gsmm/level-4.md b/docs/gsmm/level-4.md index 9696f84..dd259aa 100644 --- a/docs/gsmm/level-4.md +++ b/docs/gsmm/level-4.md @@ -5,16 +5,16 @@ sidebar_label: Level 4 --- # Level 4 - Awesome -You have a measurement system in place that is producing good real-time scope 1, 2, and 3 data and although it’s not currently driving the business day-to-day, the business is very aware of it. Using the more limited scope 1, 2, and 3 data you have had for a while, you have already achieved net carbon zero using no more than 10% offsets. (Note offsets are highly problematic but they demonstrate you are regularly measuring). You perform demand shaping; pre-calculation and caching; and time and location shifting, for example, to adapt your workloads to current conditions. You automatically delete or archive data that isn’t in regular use. Services no longer in use are automatically turned off and rightsizing happens automatically (i.e. you apply SRE principles). Your applications are Lean and you constantly review and retire functionality that is insufficiently used. Your organizational strategy has been aligned with being green as a business goal - perhaps for reasons of ESG, cost, resilience, or market access to the EU - and delivery on CO2 targets is regularly discussed and reported at senior level. Your total carbon footprint is going down even as you grow. You are also actively driving the carbon footprint of your suppliers to go down. You never cause hardware less than ten years old to become end of life either by lack of security patches or lack of backwards compatibility in your applications. You are actively driving the carbon footprint of your customers to go down (beyond simply their use of your services and devices) for example by providing scope 3 reporting for your goods and services. Examples (for some of it): Google, AWS, MS. +You have a measurement system in place that produces good real-time scope 1, 2, and 3 data, and although it's not currently driving the business day-to-day, the business is very aware of it. Using the more limited scope 1, 2, and 3 data you have had for a while, you have already achieved net carbon zero using no more than 10% offsets. (Note offsets are highly problematic, but they demonstrate that you are regularly measuring.) You perform demand shaping, pre-calculation, caching, and time and location shifting, for example, to adapt your workloads to current conditions. You automatically delete or archive data that isn't in regular use. Services no longer in use are automatically turned off, and rightsizing happens automatically (i.e., you apply SRE principles). Your applications are Lean, and you constantly review and retire insufficiently used functionality. Your organizational strategy has been aligned with being green as a business goal - perhaps for reasons of ESG, cost, resilience, or market access to the EU - and delivery on CO2 targets is regularly discussed and reported at the senior level. Your total carbon footprint is going down even as you grow. You are also actively driving your suppliers' carbon footprint down. You never cause hardware less than ten years old to become the end of life either by lack of security patches or lack of backward compatibility in your applications. You are actively driving the carbon footprint of your customers to go down (beyond simply their use of your services and devices), for example, by providing scope 3 reporting for your goods and services. Examples (for some of it): Google, AWS, MS. -| Axis | State | +| Axis      | State | | ----------- | ----------- | -| Whole organization energy commitments | already net CZero with no more than 10% offsets | -| Carbon footprint | it is reducing full stop and so is that of your suppliers | -| CO2 equivalent metrics | Real time through easy standardized APIs together with projections | -| Server resource management | all turning off and rightsizing happens automatically and data that is not regularly accessed is automatically deleted or archived | -| Energy resource management | all your systems support demand shifting and shaping based on energy data | -| Minimize end user device embodied carbon waste (assume circular economy) | automated processes ensure ten year old hardware is supported by your software for all devices | -| Minimize server hardware embodied carbon waste | optimal utilization achieved for every server using automated orchestration. Servers all have a 10 year life expectancy | -| Product management | carbon emissions are tracked per feature. Feature use is monitored and low use/poor carbon ROI features retired | -| Education | only basic training needed - everything is green by default | \ No newline at end of file +| Whole organization energy commitments | already net carbon zero with no more than 10% offsets | +| Carbon footprint | It is reducing full stop, and so is that of your suppliers | +| CO2 equivalent metrics | Real-time through easy standardized APIs together with projections | +| Server resource management | All turning off and rightsizing happens automatically, and data that is not regularly accessed is automatically deleted or archived | +| Energy resource management | All your systems support demand shifting and shaping based on energy data | +| Minimize end-user device embodied carbon waste (assume circular economy) | Automated processes ensure your software for all devices supports ten-year-old hardware | +| Minimize server hardware embodied carbon waste | Optimal utilization achieved for every server using automated orchestration. Servers all have a ten-year life expectancy | +| Product management | Carbon emissions are tracked per feature. Feature use is monitored, and low use/poor carbon ROI features are retired | +| Education | Only basic training needed - everything is green by default | \ No newline at end of file diff --git a/docs/gsmm/level-5.md b/docs/gsmm/level-5.md index 765914c..b17f751 100644 --- a/docs/gsmm/level-5.md +++ b/docs/gsmm/level-5.md @@ -5,16 +5,16 @@ sidebar_label: Level 5 --- # Level 5 - Inspiring -You’ve got there. You have achieved 24/7 CFE and require no more than 1% offsets to handle hard to shift embodied carbon. You have team level measurable goals (OKRs etc) for your CO2 measurements. You are optimizing for minimal CO2 emissions using your dynamic, real-time data. You and the services you rely on use real-time information including dynamic grid energy data to make rapid, quantitative decisions that allow you to be greener. This could (and probably will) be via a service you use rather than something you built yourself. You are already an SRE-aware organization that thinks in terms of [error budgets](https://cloud.google.com/blog/products/management-tools/sre-error-budgets-and-maintenance-windows) for outages and downtime and you now think about carbon budgets in the same way. Using predictions based on factors such as weather and grid congestion, you change and move almost all of your workloads ahead of time to match your electricity requirements to local green power availability (aka 24/7 CFE) and any time sensitive workloads are highly optimized for minimal electricity use. You never cause hardware to become end of life either by lack of security patches or lack of backwards compatibility. You are ready for the energy transition and won’t be caught by surprise by sudden new rules or constraints. +You've got there. You have achieved 24/7 CFE and require no more than 1% offsets to handle hard-to-shift embodied carbon. You have team-level measurable goals (OKRs, etc) for your CO2 measurements. You are optimizing for minimal CO2 emissions using your dynamic, real-time data. You and the services you rely on use real-time information, including dynamic grid energy data, to make rapid, quantitative decisions that allow you to be greener. This could (and probably will) be via a service you use rather than something you built yourself. You are already an SRE-aware organization that thinks in terms of [error budgets](https://cloud.google.com/blog/products/management-tools/sre-error-budgets-and-maintenance-windows) for outages and downtime, and you now think about carbon budgets in the same way. Using predictions based on factors such as weather and grid congestion, you change and move almost all of your workloads ahead of time to match your electricity requirements to local green power availability (aka 24/7 CFE), and any time-sensitive workloads are highly optimized for minimal electricity use. You never cause hardware to become end-of-life either by a lack of security patches or a lack of backward compatibility. You are ready for the energy transition and won't be caught by surprise by sudden new rules or constraints. -| Axis | State | +| Axis      | State | | ----------- | ----------- | | Whole organization energy commitments | already 24/7 CFE with no more than 1% offsets, monitored by a tight carbon error budget | -| Carbon footprint | it is as close to zero as achievable | -| CO2 equivalent metrics | Real time through easy standardized APIs together with projections | -| Server resource management | you have a rigorous carbon error budget including your scope 3 embodied carbon and all your resource use is tracked and managed through it | +| Carbon footprint | It is as close to zero as achievable | +| CO2 equivalent metrics | Real-time through easy standardized APIs together with projections | +| Server resource management | You have a rigorous carbon error budget, including your scope 3 embodied carbon, and all your resource use is tracked and managed through it | | Energy resource management | you run 24/7 CFE with a rigorous carbon error budget | -| Minimize end user device embodied carbon waste (assume circular economy) | automated processes ensure backwards compatibility and security patches for all devices (software never kills a working device). Devices last forever al la [Theseus’ ship](https://yandoo.wordpress.com/2013/08/17/theseuss-paradox/)/George Washington’s axe/Trigger’s broom | -| Minimize server hardware embodied carbon waste | hardware use is minimized by using full grid-aware integration with end user devices including phones, laptops, smart clothing, fridges… | +| Minimize end-user device embodied carbon waste (assume circular economy) | Automated processes ensure backward compatibility and security patches for all devices (software never kills a working device). Devices last forever al la [Theseus’ ship](https://yandoo.wordpress.com/2013/08/17/theseuss-paradox/)/George Washington’s axe/Trigger’s broom | +| Minimize server hardware embodied carbon waste | Hardware use is minimized by using full grid-aware integration with end-user devices including phones, laptops, smart clothing, fridges… | | Product management | your features are tracked against your scope 1/2/3 carbon error budget | -| Education | you train others in what you have achieved | \ No newline at end of file +| Education | You train others in what you have achieved | diff --git a/docs/history.md b/docs/history.md index 44c9c6e..ec7ad48 100644 --- a/docs/history.md +++ b/docs/history.md @@ -8,31 +8,31 @@ hide_table_of_contents: true # What is a Maturity Matrix? -Maturity matrices are used in fields like project management and cybersecurity to help organizations grok where they currently stand in terms of best practices, as well as the steps they can take to achieve higher levels of performance. The green software maturity matrix is a framework for assessing the level of a tech organization’s ability to handle the energy transition. +Maturity matrices are used in fields like project management and cybersecurity to help organizations understand their current state of best practices and available steps to achieve higher performance levels. The green software maturity matrix is a framework for assessing the level of a tech organization's ability to handle the energy transition. -The purpose of moving up the GSMM levels is not merely to be “ethical” or good. It is a risk management strategy to provide resilience to: +The purpose of moving up the GSMM levels is not merely to be "ethical" or "good." It is a risk management strategy to provide resilience to: -* Tightening ESG and other (e.g. EU) reporting requirements around sustainable IT. +* Tightening ESG and other (e.g., EU) reporting requirements around sustainable IT. * Physical disruption to IT systems caused by climate change. -* Pricing changes, for example the impact of highly differential dynamic electricity tariffs or reuse, repair, and recycle rules from the EU. -* Hiring and retaining employees who want to be part of the solution to humanity’s greatest challenge. This is particularly true for younger staff. +* Pricing changes, for example, the impact of highly differential dynamic electricity tariffs or reuse, repair, and recycle rules from the EU. +* Hiring and retaining employees who want to be part of the solution to humanity's greatest challenge, which is particularly relevant for younger staff. ## The history of maturity matrices -The Capability Maturity Model Integration (CMMI), which is a bit of a mouthful, was originally developed by the Software Engineering Institute (SEI) at Carnegie Mellon University. The CMMI is a framework for assessing and guiding organizations' process improvement efforts, and has 5 maturity levels: +The Capability Maturity Model Integration (CMMI) was initially developed by the Software Engineering Institute (SEI) at Carnegie Mellon University. The CMMI is a framework for assessing and guiding organizations' process improvement efforts and has five maturity levels: *[[PLACEHOLDER FOR CMMI IMAGE]]* - **Level 1 - Initial:** Processes are unpredictable, poorly controlled, and reactive at best. - **Level 2 - Reactively managed:** Per-project processes. Often still reactive. -- **Level 3 - Defined:** Processes are standardized, documented, well understood and reviewed. +- **Level 3 - Defined:** Processes are standardized, documented, well understood, and reviewed. - **Level 4 - Quantitatively Managed:** Processes are measured and controlled. - **Level 5 - Optimizing:** Continuous improvement occurs based on quantitative feedback. We reckon this broadly means: -- **Level 1:** You are floundering. No organization level strategy. Maybe a few individuals who care and/or are knowledgeable. Purely reactive. This is where most of us are on being green at this point. -- **Level 2:** You are starting to get some handle on it but without consistency. Mostly reactive. How advanced you are varies by project and team. You have the bare minimum of data. -- **Level 3:** You are good. You have decent, basic org-wide green tech knowledge and data. You have defined processes for handling that data that are applied across your organization. -- **Level 4:** You are awesome. You can measure your progress dynamically (i.e. you have real -time data). -- **Level 5:** You have ascended to the next plane of existence. You monitor and improve based on your real-time data. You give aspirational talks at tech conferences and what people are aspiring to is what you have been doing for ages. You are the tech equivalent of a being of pure energy. Think Yoda with a keyboard. \ No newline at end of file +- **Level 1:** You are floundering. There is no organization-level strategy. Maybe a few individuals who care and/or are knowledgeable. Purely reactive. This level is where most of us are on being green at this point. +- **Level 2:** You are starting to get some handle on it, but it is primarily reactive and without consistency. How advanced you are varies by project and team. You have the bare minimum of data. +- **Level 3:** You are good. You have decent, basic, organization-wide green tech knowledge and data. You have defined processes for handling that data, which are applied across your organization. +- **Level 4:** You are awesome. You can measure your progress dynamically (i.e., you have real-time data). +- **Level 5:** You have ascended to the next plane of existence. You monitor and improve based on your real-time data. You give aspirational talks at tech conferences, and people aspire to do what you have been doing for ages. You are the tech equivalent of a being of pure energy. Think Yoda with a keyboard. diff --git a/docs/index.md b/docs/index.md index 8100b4f..c4be868 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,6 +1,6 @@ --- title: Green Software Maturity Matrix -description: The Green Software Maturity Matrix is a self-assessment tool. It helps organisations understand the extent to which they have implemented green principles, patterns, and processes for building and operating their software systems. +description: The Green Software Maturity Matrix is a self-assessment tool. It helps organizations understand the extent to which they have implemented green principles, patterns, and processes for building and operating their software systems. sidebar_position: 1 sidebar_label: Home hide_table_of_contents: true @@ -10,7 +10,7 @@ hide_table_of_contents: true ## Executive Summary -The Green Software Maturity Matrix (GSMM) is a self-assessment tool. It helps organizations understand the extent to which they have implemented green principles, patterns, and processes for building and operating their software systems. The purpose is to “raise the floor and the ceiling.” I.e. to lift the behavior of the laggards on sustainable strategy and inspire those doing well to achieve more by showing what the leaders in this area are aiming for. +The Green Software Maturity Matrix (GSMM) is a self-assessment tool. It helps organizations understand the extent to which they have implemented green principles, patterns, and processes for building and operating their software systems. The purpose is to “raise the floor and the ceiling.” I.e., to lift the behavior of the laggards on sustainable strategy and inspire those doing well to achieve more by showing what the leaders in this area aim for. ### Quick Links The Green Software Maturity Matrix is a project run through the [Community Working Group](https://grnsft.org/community-wg) in the [Green Software Foundation](https://greensoftware.foundation/). diff --git a/docs/solutions.md b/docs/solutions.md index e0e548d..e402d73 100644 --- a/docs/solutions.md +++ b/docs/solutions.md @@ -7,23 +7,23 @@ sidebar_label: Solutions # Solutions -Start to list tools that are available that can help get to each level +Start to list available tools that can help get to each level. ## Level 1 > 2 Challenge - cut your resource use by 50%: -* Identify and switch off those zombie servers that aren’t doing anything (or anything much). Remember, this alone saved VMWare 66% on their emissions when they moved one DC in Singapore. -* Do a one-off right-sizing exercise on all your servers because everything tends to be overprovisioned to start with. +* Identify and switch off those zombie servers that aren't doing anything (or anything much). Remember, when they moved one DC in Singapore, this alone saved VMWare 66% of their emissions. +* Do a one-off right-sizing exercise on all your servers because there is a tendency to overprovision them. * Are you turning off your test systems in the evening and on weekends? -* Because of its extreme multi-tenancy, the cloud already uses only a fraction of the electricity of an on prem DC. AWS claims to be 3.4 times more energy efficient than an average US DC and 5 times more efficient than a European one. Move some stuff there. (Note - you could also call on your non-cloud hosting providers to be more efficient. That isn’t likely to pay off inside 6 months but you need to play the long game if you want to stay out of the cloud). +* Because of its extreme multi-tenancy, the cloud already uses only a fraction of the electricity of an on-prem DC. AWS claims to be 3.4 times more energy efficient than an average US DC and 5 times more efficient than a European one. Move some stuff there. (Note - you could also call on your non-cloud hosting providers to be more efficient. That isn't likely to pay off within six months, but you need to play the long game if you want to stay out of the cloud). * If you are already in the cloud, review your instance types. Could you be using Burstable instances or autoscaling? Pini Reznik of GreenOps consultancy re:cinq told us that, in his experience, "An average cloud system can cut its resource consumption by up to 50% just using ops best practice tuning and optimization." This is relatively straightforward stuff. -You can measure the scale of cut you’ve achieved by the reduction in your like-for-like hosting bills. Hosting cost is only a rough proxy for emissions but it’s good enough at this stage and it’s simple to explain and track. No clever tools required! +You can measure the scale of the cut you've achieved by reducing your like-for-like hosting bills. Hosting cost is only a rough proxy for emissions, but it's good enough at this stage, and it's simple to explain and track—no clever tools required! -Hurray! You’ve saved loads of money and you are now working on level 2 of the maturity matrix. +Hurray! You've saved loads of money and are now working on level 2 of the maturity matrix. ## Level 2 > 3 @@ -31,22 +31,22 @@ Challenge - cut your resource use by another 30%: * Make sure your hosting provider or operations team has extremely tough carbon zero hosting targets. Compare them with the cloud and pile on some pressure. * Ensure machines are hosted on grids and in regions with a high renewable or nuclear mix (AWS currently has 19 100% renewable regions, for example). -* Choose only green platforms that are committed to a low carbon future and have a community that will hold them to that commitment. Move to those platforms if necessary. -* Choose an architecture that will support demand shifting and shaping (i.e. usually not on demand monoliths). -* Set high bars for operational efficiency and machine utilization because the best way to both cut emissions and embodied carbon is to use fewer servers. The public clouds are comparatively very efficient. Again, that is because of scale and incentives rather than saintliness. We don’t care. In most cases we can cut our emissions very significantly by moving to a public cloud and using its services well (‘lift and shift’ buys you something but you can move beyond it). +* Choose only green platforms that are committed to a low-carbon future and have a community that will hold them to that commitment. Move to those platforms if necessary. +* Choose an architecture that supports demand shifting and shaping (i.e., usually not on-demand monoliths). +* Set high bars for operational efficiency and machine utilization because the best way to both cut emissions and embodied carbon is to use fewer servers. Public clouds are comparatively very efficient. Again, that is because of scale and incentives rather than saintliness. We don't care. In most cases, we can cut our emissions significantly by moving to a public cloud and using its services well ('lift and shift' buys you something, but you can move beyond it). * Design products and systems to support demand shaping and shifting for carbon awareness. -* Do less and be LEAN in approach. Don’t build and save stuff before need. -* Make sure your software is never the final nail in the coffin for working end user devices because of the lack of backwards compatibility or security patches. -* Build basic performance metrics into your systems and do at least basic performance analysis. Resolve any egregious bottlenecks that you find (and you will). They are just bugs that are slowing you down, costing you money and emitting greenhouse gasses. Performance is often a good proxy for carbon emissions. -* Start to automate the right-sizing you did at level 1 and look at LightswitchOps so you can turn off systems at will if you think they are no longer used. You’ll need some simple metrics for that too so you can spot low activity servers. +* Do less and be LEAN in approach. Don't build and save stuff before you need it. +* Ensure that your software never becomes the final nail in the coffin for working end-user devices because of a lack of backward compatibility or security patches. +* Build basic performance metrics into your systems and do at least a basic performance analysis. Resolve any egregious bottlenecks that you find (and you will). They are just bugs slowing you down, costing you money, and emitting greenhouse gases. Performance is often a good proxy for carbon emissions. +* Start automating the right-sizing you did at level 1 and look at LightswitchOps so you can turn off systems at will if you think they are no longer used. You'll need some simple metrics for that, too, so you can spot low-activity servers. * For code that has to run on demand, make it efficient. ## Level 3 > 4 -* You analyze cloud builds e.g. cloud carbon footprint tool. +* You analyze cloud builds, e.g., cloud carbon footprint tool. ## Level 4 > 5 -## Level 5 \ No newline at end of file +## Level 5