What if there were no architects in IT?
posted by Anna Mar, December 07, 2011It's hard to deny — there's been a rapid proliferation of architects in IT: business architects, enterprise architects, security architects, technology architects, data architects, application architects, solution architects etc.
These architecture job titles didn't exist 20 years ago. Today, many IT organizations have hundreds of architects. Is it time to reconsider the role of IT architects?
Skin in the game
Architecture roles are often defined in such a way that architects are responsible for design but not implementation.Is the separation of design and implementation responsibilities a mistake?
A flat organizational structure for architecture
Design and implementation of technology takes place at the enterprise, business vertical and business horizontal levels.A world without IT architects might look something like this.
Under this organizational model, a architecture council manages enterprise architecture. Team leaders manage solution architectures. The potential benefit of this model is that everyone in the organization is responsible for delivery.
Recently on Simplicable
5 Common Current State Architectural Blueprint Mistakesposted by Anna MarA current state architectural blueprint is essential to your success as an IT organization. After all, you can't effectively manage a complex architecture that's not documented. |
9 Reasons You Need a Current State Architectural Blueprintposted by Anna MarA current state enterprise architecture blueprint represents your organization's high level architecture. It's probably the most important documentation that any IT organization can create and maintain. |
10 Big Data Definitions: Take Your Pickposted by John SpaceyAs with any emerging field, the definition of big data is always in flex. |
9 ITIL Implementation Challengesposted by Anna MarITIL implementation is no cakewalk. ITIL impacts your entire organization — your business, your IT department and your inflight projects. |