Engineering Strategy
How to write good engineering strategies
Good Engineering Strategy should:
- Be connected to company and product strategies, not a standalone document.
- Contain tangible actions on what should be done.
- Have an overarching narrative addressing the most important challenges.
- Use accessible language so everyone can participate in the discussion.
Three Pillars
- Architecture
- Technology
- Organization
Tools
- [[Wardley Maps]]
Concepts
References
22 notes link here
- 6 Archetypes of Broken Ownership Explores six archetypes of broken ownership when knowledge, mandate, or …
- Architecturally-significant Requirement (ASR) A requirement that measurably influences a software system’s architecture.
- Architecture Decision (AD) A software design choice that addresses an architecturally-significant …
- Architecture Decision Log (ADL) A collection of all Architecture Decision Records for a project or organization.
- Theory of Constraints A system is only as strong as its weakest point. Focus on the bottleneck and …
- AI Adoption The process of integrating AI tools and practices into an organization.
- Amazon's 6-Pager Amazon's narrative-driven decision document format for meetings and proposals.
- Architecture Decision Records (ADRs) Lightweight documentation format for recording architectural decisions and their …
- Bazel BUILD Style Guide Official Bazel style guide recommending DAMP over DRY for BUILD files.
- Coachable, Learnable, and Intrinsic - Hiring Framework Framework for understanding which skills are coachable, learnable, or intrinsic …
- Decision Document Framework by Arnav Kumar Arnav Kumar's framework for writing comprehensive decision documents to get …
- DORA DevOps Research and Assessment - research program studying software delivery …
- Internal Platform Infrastructure and tooling built for internal developer use within an …
- One OS to Rule Them All - Linux Parody Parody of Tolkien's Ring Verse celebrating Linux and open source.
- Platform Engineering Building internal platforms as products to improve developer experience and …
- RACI Matrix Responsibility assignment framework defining who is Responsible, Accountable, …
- Request for Comments (RFC) Collaborative decision-making process where proposals are shared for feedback …
- Value Stream Mapping A lean management technique for visualizing and analyzing the flow of work …
- Wardley Maps A strategy visualization tool.
- Minimum Viable Product (MVP) A version of a product with just enough features to be usable by early …
- Proof of Concept (POC) A realization of a certain method or idea to demonstrate its feasibility.
- Prototype An early sample or model of a product built to test a concept.