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.

Sign up for GitHub

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

docs(known-instances): Added SAP to RFC pattern #681

Merged
merged 3 commits into from
Dec 11, 2024
Merged

docs(known-instances): Added SAP to RFC pattern #681

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dfc24fb
docs(known-instances): Added SAP to RFC pattern
dellagustin-sap Apr 11, 2024
209dfd6
fix(markdown-lint): Fix missing newline at the end of RFC pattern
dellagustin-sap Apr 11, 2024
8c84b58
Various formatting changes.
spier Dec 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions patterns/2-structured/transparent-cross-team-decision-making-using-rfcs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,7 @@ Also for decision making outside of pure software design decisions, transparent
- **Uber** - According to this blog post by Gergely Orosz: [Scaling Engineering Teams via RFCs: Writing Things Down][uber].
- **Google Design Docs** - As described in this blog post by Malte Ubl [Design Docs at Google][google]
- **DAZN** (10/2021) - One way that DAZN makes technical decisions is via RFCs. RFCs are used for decisions that apply to engineering-wide processes only! The RFCs live in a GitHub repository, and technical standards are then gradually adopted within their tools and by their engineers. An RFC can be raised by any engineer, and voted on by all engineers. If upvotes exceed downvotes, the RFC is adopted. It’s worth noting, that the RFC voting process hasn’t yet been “stress-tested” by any contentious decisions. - As described in this blog post by Lou Bichard: [Building A DX Team: Lessons Learned][dazn]
- **SAP** - As described in the blog post [Cross-Product Architecture: Embracing Conway's Law for Better Software Architecture][sap-cpa], SAP has a mature tool-assisted process for document review across teams. It is primarily used for the review of Architecture Decision Records (ADR) originating from cross-team work done on the Cross-Product Architecture collaboration model. This means that the review process in not easily available for decisions on small projects. Also, the documents are not by rule related to InnerSource projects. That means it is not a universal solution for engineering decision making in the company and also not a 1:1 fit for this pattern, but close enough to be mentioned as known instance.
spier marked this conversation as resolved.
Show resolved Hide resolved

## Status

Expand All @@ -123,3 +124,4 @@ Structured
[bbc]: https://www.youtube.com/watch?v=U6zlghE0HcE
[google]: https://www.industrialempathy.com/posts/design-docs-at-google/
[dazn]: https://medium.com/dazn-tech/building-a-dx-team-lessons-learned-4a66446088bc
[sap-cpa]: https://community.sap.com/t5/technology-blogs-by-sap/cross-product-architecture-embracing-conway-s-law-for-better-software/ba-p/13648600
Loading