liveBook · Manning

Architecture board

As explained in Think Like a Software Engineering Manager

An architecture board is an organizational review group that evaluates proposed technical designs and provides architectural guidance.

An architecture board is an organizational review group made up of senior engineers from multiple teams. Teams present proposed technical designs before implementation to receive proactive guidance, align with best practices, and maintain a consistent architectural standard. section 12.2.3

Use an architecture board to:

  • Review new features or components before implementation. section 12.2.3
  • Give teams feedback from experienced engineers across the organization. section 12.2.3
  • Reduce technical debt by challenging design choices that may harm long-term system health. section 12.2.3

Dynamic pricing feature

A team adding dynamic pricing might present a choice between extending a legacy monolith and creating a new microservice. The board can help weigh future extensibility, available resources, delivery timelines, and the technical debt created by each option. section 12.2.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Defines membership, review timing, and purpose, but does not specify a detailed governance process or decision framework.
Examples
Uses a dynamic pricing decision comparing a legacy monolith with a new microservice.
What it assumes
Assumes familiarity with technical designs, teams, implementation, technical debt, monolithic architecture, and microservices.
What you can do after
Evaluate proposed designs with cross-team senior-engineer feedback before committing to implementation.
How it connects
Connects technical debt with technical design, best practices, microservices, monolithic architecture, and engineering operational excellence.
Cover of Think Like a Software Engineering Manager
liveBookmanning.com
Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.