Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Case Study] Case study of Mastercard's Adoption & Adaption of the Green Software Patterns #243

Open
1 of 12 tasks
russelltrow opened this issue Jun 7, 2024 · 5 comments
Open
1 of 12 tasks
Assignees
Labels
articles Member-Contributed Articles written/proposed by member organizations

Comments

@russelltrow
Copy link
Member

russelltrow commented Jun 7, 2024

Case Study Details

Mastercard have developed their own patterns catalogue based on ours:

Green-Software-Foundation/patterns#265

They are now ready to share what they have produced.

Proposer: Sébastien Le Callonnec, Daniel Vaughan (Mastercard) + Russ (GSF)
Abstract: (50 word summary of the article)
Why: (Why is this article an important topic to discuss and how is it related to the work/mission/theory of change of the GSF)
Audience: Software practitioners
Timeline: [TENTATIVE] October 2024

Important Information

To be filled out later

Author: TBD
Other contributors: @NAMRATA-WOKE @Green-Software-Foundation/patterns-contributors @Green-Software-Foundation/patterns-leads
Article Link: (Link to the doc, must be in our official GSF drive)
Graphics Link: (Link to the design assets for this article, must be in our official GSF drive)
Published Link: (The link the article was published to for memory)

Checklist

  • Idea discussed and selected for writing. After checking this box, set Status to "Todo" under "Articles" project
  • Author identified. After checking this box Assign issue to the Author
  • Scheduled in calendar
  • Google doc link created in GSF drive.
  • In progress. After checking this box, set Status to "In Progress" under "Articles" project
  • Draft created. After checking this box, set Status to "In Review" under "Articles" project. Assign issue to Reviewer/Author during the back-and-forth
  • Draft reviewed. After checking this box, set Status to "In Publishing" under "Articles" project. Assign issue to Graphic Designer and add "Graphic Design" to issue's Projects
  • Graphics created. After checking this box, assign to TBC for approval.
  • Approved. After checking this box, assign to TBC for publishing.
  • Published. After checking this box, set Status to "Ready" under "Articles" project. Assign to Marketing and add "D: Marketing" to issue's Projects
  • Shared on socials
  • Shared on newsletter. After checking this box, set Status to "Done" under "Articles" project and close issue.
@russelltrow russelltrow added the Member-Contributed Articles written/proposed by member organizations label Jun 7, 2024
@russelltrow
Copy link
Member Author

Hey @NAMRATA-WOKE I caught up with Mastercard and they would like to write a case study/article about their adoption of the Green Software Patterns. I'll make a connection over email.

@NAMRATA-WOKE
Copy link
Contributor

@NAMRATA-WOKE
Copy link
Contributor

August 14 Meeting Notes:

  • Mastercard cannot share measurable outcomes numbers yet
  • The case study will cover the development of green software practices and how adapting and rebuilding a green software patterns catalogue has enabled the team to conduct an internal roadshow and scale adoption.
  • Some Mastercard patterns might be bound to IP
  • Mastercard plans to organize a GSF Summit in Dublin on October 8

Next Steps

  • Sébastien will join the Patterns Project meeting in September to briefly share Mastercard's work and open the floor to questions (and provide a high-level written overview)
  • Erik and Sébastien will coordinate internally to:
  • Sanitize the patterns catalogue before the call
  • Assess if the team can work towards an October 7 deadline
  • Erik will revert back on whether they can share how the team will be evaluating success assessing the effectiveness of their work
  • Namrata and Russ will connect to determine if the GSF can meet an October 7 deadline

@NAMRATA-WOKE NAMRATA-WOKE moved this to In Progress in Patterns Aug 14, 2024
@NAMRATA-WOKE
Copy link
Contributor

@russelltrow how would you like to assess whether we can make the October 7 deadline? Some things to consider:

  • Distribution of labour between us and Mastercard in drafting the case study
  • Template
  • Feedback process, including patterns project and WG Chairs (if required?)
  • Asim's role?
  • OKRs for Q4

@NAMRATA-WOKE NAMRATA-WOKE changed the title [Article] Case study of Mastercard's Adoption & Adaption of the Green Software Patterns [Case Study] Case study of Mastercard's Adoption & Adaption of the Green Software Patterns Aug 14, 2024
@NAMRATA-WOKE
Copy link
Contributor

August 14 Meeting Notes:

  • Mastercard cannot share measurable outcomes numbers yet
  • The case study will cover the development of green software practices and how adapting and rebuilding a green software patterns catalogue has enabled the team to conduct an internal roadshow and scale adoption.
  • Some Mastercard patterns might be bound to IP
  • Mastercard plans to organize a GSF Summit in Dublin on October 8

Next Steps

  • Sébastien will join the Patterns Project meeting in September to briefly share Mastercard's work and open the floor to questions (and provide a high-level written overview)
  • Erik and Sébastien will coordinate internally to:
  • Sanitize the patterns catalogue before the call
  • Assess if the team can work towards an October 7 deadline
  • Erik will revert back on whether they can share how the team will be evaluating success assessing the effectiveness of their work
  • Namrata and Russ will connect to determine if the GSF can meet an October 7 deadline

At the moment, every Case Study we produce needs to be a detailed examination of how an organization has improved its SCI Score by applying/adopting a graduated green software project, including calculations using Impact Framework, benefits and challenges experienced during implementation and lessons learned​. As a result, we will inform Mastercard and work towards this deliverable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
articles Member-Contributed Articles written/proposed by member organizations
Projects
Status: In Progress
Development

No branches or pull requests

2 participants