Should we consider incorporating an architecture decision record? #142
semantic-nomad
started this conversation in
General
Replies: 1 comment
-
|
I agree and think that this could be merged with the concept of a sociocracy policy log/book. I added the reference here: https://docs.google.com/document/d/1N7Y-sfYx9Cu2psJEcG2RsmniJaVV8f-IAU8Zyl_ALdw/edit?usp=sharing and And we are definitely overbuilding the project right now. Not saying we shouldn't, but yes this is getting process heavy in anticipation of growth. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is from the Birdaro course.
I like the idea of have an architecture decision record to keep track of what was implemented, or changed, and why.
This might be a bit overkill for this project, but a streamlined form to log (or vizualize via mermaid) decision points might be useful in the future as the project matures.
Might be worth running through at the next planning meeting.
Beta Was this translation helpful? Give feedback.
All reactions