Find information on the following topics What is an IT Architect? Different types of Architect roles. Different paths to Architect roles. Advice on how to becoming an IT Architect.

1. I want to be an
IT Architect
A talk by Diego del Yerro and Sponsored by Pitcheers

2. Who am I?
My name is Diego del Yerro and I am an IT nerd from
Argentina, living in New Zealand for the last 4 years.
I have over 10 years of experience as an IT Architect and I was
extremely lucky to work in different architecture roles for
multinational companies in several industries.
I am also a Systems Engineer with a Master degree in
Management of Technology and Telecommunication
companies.
https://www.linkedin.com/in/diegodelyerro

3. Let’s have a chat about becoming an...
and some tips based on my own experience
Picture by Nick Youngson - Alpha Stock Images - http://alphastockimages.com/

4. What is an IT Architect?

5. An IT Architect is...
A role within an IT team or structure that makes decisions and
recommendations of solutions; about the design and evolution of
components of a system (human, hardware and software) and their
interaction, based on requirements (Functionals and Non Functionals) and
restrictions.
In practice, as an IT Architect you will need to use many hats to solve a
problem. For example: Tech Lead, Project Manager, Process designer and
business analyst.
Your own experience and capability to learn new abilities will be
challenged, as well as your resilience when things do not go the way you
expected.

6. However...
Being an IT Architect does not mean you will lose contact with code. That is
why many architects define themselves as hands-on or hands-off.
It depends on the scope (or domain) of your role.

7. Accountability of an IT Architect
Not every context of work is the same, so accountability of IT Architects could vary
Advisor Delivery
Hands-on Architects
Leaders of Technical Vision
Responsible of Deliverables
Hands-off Architects
Consultants for teams and
Management
Educators
Jack of All Trades

8. https://www.careers.govt.nz/jobs-database/it-and-telecommunications/information-technology/information-technology-architect/
According to NZ Tertiary Education
Commission

9. IT Architect

10. Which one?
You might have seen job advertisements in LinkedIn, Seek or TradeMe, asking
for:
● .NET/Java Architect
● Solution Architect
● Enterprise Architect
● Product Architect
● Technical Architect
● Infrastructure Architect
● Data Architect
● and more…
Each of these positions work on different domains .
For this presentation we will focus on: Technical, Solution, Enterprise and
Information architecture roles
?

11. Skills for the job
We will be grouping skills for an architect role in these simple categories
● Communication: writing documents, modelling, presenting, facilitating
meetings, coaching, teaching and negotiating.
● Technical Expertise: coding, devops knowledge, time in operation of a
system and design, among others.
● Project management: management of stakeholder and sponsors, scope,
requirements and risks.
We will leave people management out for now, as an IT Architect does not
necessarily manage people.
A very good (and extensive) analysis on https://pubs.opengroup.org/architecture/togaf9-doc/arch/

12. Technical Architect
A technical architect is the closest role to execution of solutions.
● You might be an application architect, whose role is to design a
software application and its evolution.
● Or an Infrastructure architect, which main considerations are the
design of infrastructure, its reliability and availability for business
operations.
You are likely to be making decisions in a context you are comfortable
with and your technical skills are your primary weapons.
There might be people in the organisation with better communication
skills for presenting your ideas, and you will be their solid foundation.
Other roles like this could be: Data Architect, Java/.NET/<technology here> Architect

13. Solution Architect
A solution architect is the right hand of a Project or Program Manager.
Their scope is (normally) across more than one application and their
work could take them close to the code or as far as possible.
You might be making decisions out of the comfort zone, about an
application written in ABAP, R or Erlang… or a strange legacy system
written in FOX Pro.
You will need to feel comfortable communicating your ideas to people
that might not be as technical as you.
As a Solution architect, you require project management skills.

14. Enterprise Architect
An Enterprise Architect is a role that considers the companies’ assets
(software and hardware), structure (areas), processes and business
strategy as a whole.
Their work is focused on the technological strategy to support the
business, thus, long living and far from the execution domain. As an
Enterprise Architect your focus will be business knowledge.
Your Communication Skills are your main weapons and Project
management skills are important.
You will be making decisions out of your comfort zone and these roles
are normally hands-off code, so although being super fun they could be
frustrating for more technical people.

15. The term Information Architect could be a little confusing.
● This role structures the information so it can be easily managed and
discovered (knowledge management). Information architects are very
important in companies managing legal documentations as they often
require master data management techniques.
● Other people refer to the information architect as a subtype of
Enterprise architect, focused on the model of business entities. They
are very important in integration projects.
● In other cases they just refer to Data Architects, but that is a subtype
of Technical Architect.
In any case, communication is key and your technical expertise in your
domain is very important. You might be working with frameworks like DAMA,
SID, UBL and others.
Information Architect

16. Other possible IT Architect roles
There are other types of architects which are less common in the market
● Product Architect: A mixture between a solution and enterprise architect with scope
in a specific business product, which could have multiple applications. You might get
involved in projects outside your comfort zone.
● Business Architect: You will be focused mainly on business decisions and arguably
could be considered IT. Your main focus are business strategy and processes.
● Security Architect: the equivalent to a Solution Architect specialised in IT Security.
+

17. What is the Path?

18. You can be an IT Architect through any path
I have seen IT Architects of each type coming from these paths

19. Path to Technical Architect
Developer
Operations
Engineer
Sr. Developer
Technical Lead
Infrastructure Lead
Database/Storage
Administrator
Devops
Network
Engineer
Technical
Architect
Infrastructure Architect
Data Architect
Java/.Net/* Architect

20. Path to Solution Architect
Developer
Operations
Engineer
Sr. Developer
Technical Lead
Infrastructure Lead
Database/Storage
Administrator
Devops
Network
Engineer
Technical
Architect
Solution
Architect
Product Analyst
Product
Specialist

21. Path to Enterprise Architect
Sr. Developer
Technical Lead
Infrastructure Lead
Devops
Technical
Architect
Solution
Architect
Product Analyst Product
Specialist
Business Analyst
Enterprise
Architect
Business
Specialist

22. Path to Information Architect
Sr. Developer
Solution
Architect
Product Analyst
Product
Specialist
Business Analyst
Enterprise
ArchitectBusiness
Specialist
Information
Architect
Knowledge
Management
Specialist
Developer

23. Yes! I want to be an IT
Architect!

24. Masters of your domain: Specialisation
● Infrastructure: http://www.devopsbookmarks.com, https://acloud.guru
● Data: Certify in main platforms. Learn about data lifecycle in your business.
● Application Architects: Learn about application design and integration patterns
https://docs.microsoft.com/en-us/azure/architecture/patterns, https://microservices.io/patterns, and
use the references and categories of wikipedia articles like
https://en.wikipedia.org/wiki/Category:Software_design_patterns
Understand concepts outside your domain
● Follow the lessons on https://www.developertoarchitect.com, and learn about architecture
perspectives for documentation like described in TOGAF,
https://en.wikipedia.org/wiki/ISO/IEC_42010 or the 4+1 model.
● Learn about how to communicate and manage technical debt reading Martin Fowler’s
Tech Debt Quadrant (https://martinfowler.com/bliki/TechnicalDebtQuadrant.html) and Steve
McConnell explanation (https://www.youtube.com/watch?v=lEKvzEyNtbk). Look for tools like
SonarQube
!Technical
Architects
Tips

25. Apart from what was mentioned for technical architects…
Improve your Communication and Project Management Skills
● Read about Prince and PMI methodologies. Main takeaways are scope, estimation of
work (WBS), risk and stakeholder management.
● Learn about MoSCoW lists, Non Functional Requirements, Architecture Drivers
● Read tips about making effective presentations and always keep in check who is your
audience (for written documents and oral presentations)
● Learn how to negotiate,
https://www.amazon.es/Getting-Yes-Negotiating-Agreement-Without/dp/0140157352 is a good
starting point.
!Solution
Architects
Tips

26. You will not need as much technical knowledge as a technical architect, but reading about
integration patterns would be a must.
● Integration Patterns: An oldie but goodie on top of the ones seen before are
https://www.enterpriseintegrationpatterns.com. Learn about SOA and definitely go through
this page https://www.developertoarchitect.com.
● Look for architecture frameworks like TOGAF, DoDAF and FEAF.
Same as Solution Architects, improve your Communication and Project management skills
● Familiarise with Gartner publications like Magic Quadrant and Hype-cycles, Forrester
Waves and ThoughtWorks Tech Radar
Depending on the industry domain you work on, you might need to learn specific processes
frameworks (like TMForum frameworks for telecommunications).
!
Tips
Enterprise
Architects

27. Additional Tips
Becoming an IT Architect will take you out of your comfort zone, sometimes
asking you to formulate decisions in unknown contexts. Learn how to ask the
proper questions and be honest when you do not know the answers.
Learn how to manage your EQ, specially under pressure or frustrating
situations. As an architect you could be exposed to criticism.
Once you are an IT Architect, learn how to help your teammates to be at their
bests. Learn the difference between coaching and mentoring and exercise those
according to the situation.

28. I have more questions

29. Get in touch
Email Santiago (Santiago@pitcheers.com) or
give him a call on +642108198922
Hope to hear from you!
www.pitcheers.com

30. Thanks!