Regenerative software metric model

[gonzaloortega1993]

The Problem
How regenerative is any given company? There is yet no specific guideline on how to measure if they are actually moving in the right direction. Without metrics, regenerative software risks having no accountability.

What Are We Hoping to Achieve
A self-assessment model that any organization can access on the website to understand where they stand today, with the possibility at the end of getting a tailored solution to become more regenerative.

The Products
A Regenerative Software Metric Model defining what sustainable, adaptive and world-positive software looks, (measurable).
A self-assessment tool organizations run to get their baseline score on the website.
A consultancy offer where we help organizations redesign their development culture, tooling and architecture.
A certification organizations can earn and display signaling to customers, partners and regulators that their software is built responsibly.

Who Do We Have in Mind
Organizations, CTOs and product leaders who want their software to create lasting value for people, communities and the planet.

---

June 17^th

Today in the MoM Office Hours we discussed this approach.

We came up with the contour of a plan, which I will lay out here and then everyone is welcome to join and contribute.

Previous work

@buep and I have have previously developed a Continuous Delivery Metric Model. A copy of it live at https://www.lakruzz.com/codememo/ it needs a few word to explain it:

• It's built as a static website (using Jekyll, extending the minimalmistakes template).
• It's a five-by-something template. The five "columns" refer to the Dreyfus brother's model for skill acquistion — Presented in the book "Mind over Machine".
• The "areas" or "knowledge domains" can be any and each area can easily be hidden/shown for a given context usage, so it's quite literally at 5-by-any model
• Actually the layout supports that more cards live in the same level (they will rotate) this is more a feature to support the development process, but actually it becomes an any-by-any matrix.
• The current model is old (not updated sinde 2019) so some reuse could (perhaps) occur, but mostly it needs a complete run-over
• Each tile/index card is clickable and will reveal the "b-side" with a title, an excerpt of the concepts but most interestingly a "scoring" on four different parameters.
• It's originally designed to be a workshop tool (for running Value Stream Mappings and then developing Roadmaps for necessary actions).
• The cards can be printed as index cards and used for tactile gamification (https://www.lakruzz.com/codememo/print/ will generate the pdf output to send to print.)
• Each card can have an extende and more elaborated text (suitable for web, but not for print - (see example)

Skill Level	Components	Perspective	Action	Commitment
1. Novice	Context-free	None	Analytic	Detached
2. Advanced beginner	Context-free and situational	None	Analytic	Detached
3. Competent	Context-free and situational	Chosen	Analytic	Detached choice of saliences and of action; involved in outcome
4. Proficient	Situational and context-free	Experienced	Analytic	Involved experience of saliences; detached choice of action
5. Expert	Situational and context-free	Experienced	Intuitive	Involved

Upcoming work

So what we should do is to brainstorm new index cards that makes up the "Regenerative Software Model"

Obvious input points are:

• https://docs.mindovermachine.dk/en/methodology/how-we-work/
• https://github.com/mindovermachine-dev#open-source-stewardship/

But these sources are also preliminary, and definitely not finite.

Organization (game rules)

We should organize in relevant areas (probably four, to issues a 5-by-4 matrix)

We will setup

• A dedicated channel #regenerative-model in slack
• A dedicated folder on Google Drive MoM Data Room/Projects/Regenerative Model
• A Model Card Template to take offset from

[lakruzz]

Love this idea.

Back in the days we build a "Continuous Delivery Metric Matrix" https://www.lakruzz.com/codememo/

It's old now and not very contemporary, but redoing something like this; describe a model and self-assessment tool for Regenerative SW and processes could be really cool!

[keozx]

DORA came to my mind :)
Someone did a "MORA" metrics based on DORA metrics but for MobileOps.
So we can do the DORA for regenerative software, RORA metrics for RegenerativeOps? And stemming from actual research? Maybe in the future!