Almost every EA/ITG "frequently asked question" compilation includes a FAQ asking how to measure EA/ITG maturity. The answers invariably include a maturity scale, a set of qualifications and perhaps some average benchmark data. Armed with this basic information about measuring maturity, should every organization immediately complete an assessment? The answer is: not necessarily.
Today’s Enterprise Architecture (EA) programs often “hit a wall” when attempting to demonstrate their value to the business. While EA teams may be effective at launching a program and perhaps creating initial deliverables, other stakeholder communities within IT and the business often do not directly appreciate the value of EA work.
As a native son of the Mid-Atlantic, Gary Washington, who serves as the Chief Architect of the FDA, has the DNA to make a success of his position. Raised in Southeast Washington DC, Gary joined the Air Force right out of high school and spent ten years immersed in networks, mainframes and databases.
Control systems and the U.S. Air Force NCO Leadership School. After leaving the Air Force, Gary then went on to a 6-year stint in the private sector followed by a return to the Federal Government.
You think you have a tough job - how about taking care of the health of all Americans, from infant to elderly? The Food and Drug Administration (FDA), is an operating division of the Department of Health and Human Services with 10,000 employees. Their mission? To ensure that all foods, drugs, and cosmetics are safe and properly labeled; that drugs and medical devices are safe and effective; that the American blood supply is safe and adequate; and finally that equipment that uses radiant energy, such as X-ray machines, is safe. Whew.
Mark Twain is noted for commenting that there are three kinds of lies: Lies, Damn Lies and Statistics. Famed in reflecting the ironies of his own time, Twain would have equally embraced a current truth - that shading the truth to meet operational and visual needs is a common, yet never a productive tactic. That reluctant reality holds true for today’s Enterprise Architects as well.
Many companies are starting to realize the benefits to managing their vast collections of IT resources as services provided to users. This is in contrast to the traditional approach of developing and managing applications that provide capabilities to users. The structure of the Service Level Agreements (SLAs) can vary greatly depending on your business needs. Here are some best practices for creating different types of SLAs.
Plan the SLA structure