Architecture – I’d like to define IT Architecture as the glue between management and propellor heads.
Business managers are not always up to speed on technology, like engineers, developers, or technical leads. Often an architect will capture a manager’s business goal and requirements and translate them into technical solutions. Architects then deliver the technological solutions as blueprints to the engineers, developers, and technical leads. Inversely, architects explain the technology that engineers, technical leaders, and developers will deliver, into a language understood by business managers.
IT Architecture
An Information Technology architect’s primary goal at the beginning of any project would be to capture business goals, project requirements and understand the business processes necessary to help deliver business objectives.
I’d like to think that an architect delivers the blueprints for construction.
Anyone can build a Shack
To build a castle, you’ll need an architect in your team
My intent is to cover the following topics regarding Architecture:
- Why architecture is important (purpose, goals, business importance)
- Intent of architecture
- What a solutions architect provides and what solutions architecture doesn’t provide
- Today’s architect vs. yesterday’s architect
- Where does an architect fit into an organization
- When moving from waterfall projects into Dev/Ops and Agile planning, how does an architect still provide value within speedy agile programs
- Architecture as an organization
- Yes, if a business is large enough, it probably should be an organization
- Architecture framework
- Deliverables
- Important Elements of deliverables
- Methods
- Structure
- Deliverables
- Architectural reviews
- Development and then Blueprints
