Architecture
I could not resist posting this because I'm overly involved with a crucial business project that is planned to increase our company's revenue by $1 BILLION. Unfortunately, we have had each of these signs in the order they are listed. 7 signs of a challenging projectTime constraintsSolution changesLimited process knowledgeLimited requirements availableTraining needsResource needsCustomer changes ......
Over time I've constructed the following general outline for creating executive summary presentations.
- Overview
- Case for change (drivers: business & IT)
- Current State (key observations and issues)
- Future State (alternatives & recommendation)
- Gap Analysis (current, recommended, and future capabilities)
- Roadmap
- Summary (Key... takeaways, recommendations, next steps, measures of success)
Why is this important to our business? How is this different than how we develop today? Why now? What new skills and technologies are required? What devices and standards should we target? Is context-awareness important? Where will applications be deployed? What enterprise capabilities are required to support mobile? What is the roadmap? How is this related or not related to the portal? Are we targeting internal apps, external apps, or both? Who will consume the apps and with what? How does this ......
Here is my general guidance in regards to solutions architecture: Leverage what we have first Gather facts, not opinions when assessing solutions Avoid making early assumptions Prove that issues are real before escalating concerns Present issues or concerns within proper context If prototypes reveal concerns, consider alternative solutions ......
1. State your initial point of view
2. Define your point of view more clearly
3. Give an example of your point of view
4. Explore the origin of your point of view
5. Identify your assumptions
6. Offer supporting reasons, evidence, and arguments
7. Consider other points of view
8. Arrive at a conclusion, decision, solutions, or prediction
9. Consider the consequences
I started taking a philosophy class at school this week and discovered a critical thinking model that I believe can be applied to Enterprise Architecture to better communicate thought leadership on controversial topics. The critical thinking model is incredibly simple, yet powerful. 1. State your initial point of view 2. Define your point of view more clearly 3. Give an example of your point of view 4. Explore the origin of your point of view 5. Identify your assumptions 6. Offer supporting reasons, ......
According to BusinessWeek (2008)... In 2007, a new form of attack, using sophisticated technology, deluges outfits from the State Dept. to Boeing. Military cyber security specialists find the "resources of a nation-state behind it" and call the type of attack an "advanced persistent threat." The breaches are detailed in a classified document known as an Intelligence Community Assessment. The source of many of the attacks, allege U.S. officials, is China. China denies the charge. Below are some recent ......
I don't know if it's a revelation or simply the fact that I'm through with my heavy workload time of the year... but I had good thoughts and conversations today. As an Enterprise Architect, part of my job is facilitating strategies. Until now, I've sought the right outlines, formats, etc to communicate strategies. Over the past 2 years I've facilitated multiple strategies, but executive leadership keeps asking for plans. I've always taken their requests for plans as a negative, thinking that we missed ......
The following graphic is my attempt to define the evolution of the web in a graphical manner.
