Get it done faster! If you just can’t get started, there has got to be a better way. I’d love to see more agile EA get done, so today I’ll share the most common and critical parts of an EA Plan. Here is the checklist I use when creating plans for my clients and customers.
The Enterprise Architecture plan is a process as well as document set or repository that contains the written plans for the vision and development of the Enterprise Architecture.
There are many recommended components, of which many are included here. It is my recommendation that you consider creating a shell document/presentation with the following titles in order to keep the information you collect.
As Well, It Can Act As A Quick Guidepost For Your Endeavors.
- Vision Statement including Strategy
- Business Drivers & Goals for the Enterprise
- Participants/Contributors in the Planning process
- Leadership & Sponsorship
- Guiding Principles
- Approach & Strategy to the EAP
- Current State Section
- Target State Section
- Transition Plan/Roadmap
- Next steps/Issues/Outstanding
If you include all of these in your shell document, the rest is fill in the blank. Even if you have to go through and fill in what you know for sure, or your team can collect, you can always go back and validate what you’ve added.
Don’t spend a lot of time on the sections that you are “surmising”. Put a few key points down and find a stakeholder to validate. It’s easier to throw darts at the wall than start with a blank page.
Tell me what you think? Do you use all of these sections? Have some of your own you’d like to add?