A "Brick" is a EA tool used in planning and communication. It is based on the NIH Enterprise Architecture Brick.
- In the technical space, "things" refer to technologies, tools, and protocols.
- A thing can exist in one or more brick categories. For example, "HTTP" may be both baseline and containment, while "HTTPS" is both baseline and "tactical".
- "tactical" and "strategic" can provide roadmap qualifications to baseline things
- Typical lifecycle of things in a brick: emerging -> baseline -> containment -> retirement
- Scope of a brick can vary, but the brick becomes less useful when it is too big or too small.
- Strive for an open environment with one brick per domain area rather one brick to communicate to customers and one brick for internal team communication
- How to track pilots?
- How to track things that have been evaluated and dismissed ("misfit bricks")?
- How do we capture investment levels?
- How does a brick communicate service levels?