Writing enablers in a #SAFe #agile project for quality attributes.

For convincing everybody I made the experience to write strictly logically based on method and principles is the best and all stakeholders (business, architects, compliance, engineers, developers) are happy.

https://12factor.net/
and
https://www.reactiveprinciples.org/principles/index.html

If things are strictly methodic expressed (written) business can do informed decisions about priority.

#12factor #reactivemanifesto #edgecomputing

For the distributed system I am working on I finished the first iteration of defining and clustering failure scenarios.
I gave it to the other architects for review and feedback.

Just now realized that I identified and described 42 scenarios.

Isn't that a wonderful number.

#kubernetes #edgecomputing #reactivemanifesto

I wonder if #EventModeling or #Eventsourcing provides a methodic approach or something similar to describe failure #scenarios for a #distributedsystem. I made already a mapping of the #k8s based #distributedsystem to #12factor and the #reactive principles as described in the #reactivemanifesto.
I also collected all possible failure events that came to my mind with a mindmap.
So, now I search for a good way to describe the failure scenarios.

Ideas and hints very welcome.