Playbooks are so hot right now! Seems like there are security playbooks, commercial playbooks, all types of playbooks floating around.
Recently I’ve been building enterprise architecture playbooks for large programs of work and was wondering what everyone else put’s in their EA playbooks?
Here’s a quick rundown of what I usually include in mine:
-
Business objectives: A clear statement of the business goals and objectives that the program of work is intended to achieve.
-
Architecture principles: A set of guiding principles that will inform the design and development of the program of work. These principles may include things like security, scalability, maintainability, and interoperability.
-
Architecture frameworks: A set of frameworks that will be used to guide the design and development of the program of work. These frameworks may include things like the Zachman Framework, the TOGAF framework, or the Gartner EA framework.
-
Architecture governance: A set of processes and procedures that will be used to ensure that the program of work adheres to the established architecture principles and frameworks.
-
Architecture documentation: A set of documents that describe the various components of the program of work, including the business processes, data models, application architectures, and technical architectures.
-
Architecture review: A process for reviewing and approving changes to the program of work to ensure that they are aligned with the established architecture principles and frameworks.
-
Architecture roadmap: A plan for implementing and evolving the program of work over time, including a timeline for key milestones and deliverables.
-
Architecture metrics: A set of metrics that will be used to measure the progress and success of the program of work, including things like cost savings, increased efficiency, and improved customer satisfaction.
Missing anything? How do you build your playbooks?