Skip to content

Adoption Stories

Jump to bottom
Russell Trow edited this page Nov 22, 2024 · 1 revision

AVEVA

https://github.com/Green-Software-Foundation/patterns/issues/247

Context

  • Used the patterns as a way to measure the green software maturity of products teams.
  • Started with measurement
  • Internal group reviewed, revised and compacted the GSF catalogue.
    • Identified the relevant patterns.
    • See them as Practises not just Patterns
  • Packaged up as “Maturity Scoring for Green Product Design” handbook
  • Asked each team to self-evaluate their maturity by whether they had adopted each of the identified patterns
  • Shared the handbook with the patterns and a scorecard

Results

TBC

Assets

Mastercard

https://github.com/Green-Software-Foundation/patterns/issues/265

Context

  • Developed own catalogue based on the GSF one
    • Build upon what already exists. GSF catalogue is reference
    • Came with with own set of Mastercard specific patterns
    • Followed the same pattern template with a small tweak (examples)
    • Created a style guide
  • Have 5 categories, with the following descriptions:
    • Architectural Patterns
      • Patterns that can be applied when designing and architecting your application to ensure that it is the most efficient, and reduces waste that result in CO2 emissions.
    • Technology Stack & Tooling Pattern
      • Patterns related to technology stacks, what choices to make when you are starting off a project, and what tradeoffs you need to consider.
      • Feel we will need Frontend/Backend subsections.
      • Considering adding a Persistence and Storage Patterns section, for database and cache-related patterns.
    • Code and Algorithm Patterns
      • Patterns that can be applied when writing code for your application to ensure it is as efficient as possible. Remember that the code that is not written is the greenest of all!
    • Methodology Patterns
      • Patterns that are related to Software Development methodology, which have a direct impact on Green Software principles. For example Agile Practices encourage an iterative and incremental approach to building software, ensuring that the features that are built first are the ones most valuable to customers, and not more, therefore reducing wastes.
    • Operational Patterns
      • Patterns that are related to the running software in Production, including management of the hardware and equipment required to execute systems.
  • As much as possible we are trying to make this catalogue a complement of the GSF one, with patterns relevant to teams in Mastercard.

Results

  • Early days - Catalog is being published People are curious - Asking questions - Becoming aware - Be more conscious - Be more responsible

Assets

EPAM

Context

  • Setup a working group of Developers, Architects, Engineers, DevOps, Consultants, PM
  • Critical audit of the patterns
    • Like, love, adapt
  • Sit alongside and compliment stand ways of working e.g Development approaches
  • Evolving Patterns into Practises
  • “Formed a working group to review and adapt GSF practices, and aligning these practices with existing delivery processes”
  • Help us build greener software for our clients

Results

TBC

Assets

Clone this wiki locally