Presentation on growing architects presented at the Australian Architecture Forum 2009. This is a further developed concept from the similar SAF presentation.

1. Growing Architects
Kevin Francis
Practices Manager
Object Consulting

2.  My journey
 Architecture:
• Types of Architects
• Architecture Career Paths
• Architect skill requirements
 Growing Architects:
• Skills development
• Organisational requirements
What We Will Cover
Are you in the right session?

3. My Background
Why should I be talking about this?
 Developer and Operations
 Architect and Consultant
 Enterprise Architect
 Project Manager and Business Owner
 Principal Architect
 Delivery Manager
 Executive – Strategic Management
 MVP and Community Work

4. Architecture Career Paths

5. 5
Solution Architect
Application
Architect
Application
Architect
Application
Architect
Data Architect
User Interface
Architect
Application
Architect
Types of Architects
It isn't all about code…
User
Interface
Business
Layer
Application
Application
Supplier
Database
Business
Layer
Business
Layer
Business
Layer
Integration
Architect
Infrastructure
Architect

6. 6
Paths into Architecture
It still isn't all about code…
Developer
Solution
Architect
UI
Architect
Business
Analyst
Almost
Anyone
Business
Analyst
IT Support
Snr Data
Architect
SOA
Architect
Snr
Project
Manager
Infrastructure
Manager
Integration
Architect
Data
Architect
Project
Manager
Infrastructure
Architect
Application
Architect

7. 7
Paths from Architecture
You can't be an architect forever
Delivery
Manager, etc
Infrastructure
Manager, etc
CTOCIO Other Executive
Infrastructure
Manager
SOA
Architect
Snr Data
Architect
Snr
Project
Manager
Solution
Architect
Enterprise Architect or Consultant

8. Architecture Skills

9. 9
What is Architecture?
It's all about technology, right?
 Designing all or part of a system to meet the
functional and non-functional requirements
 Designing the delivery approach
 Managing risk
 Delivering to budget
 Managing stakeholders
 Managing change
 Contracts
 Explaining what needs to be done
 Managing the development team

10. 10
Intrinsic Architect Traits
 Inventive - can see through the problem
 Good communicator – can sell the solution
 Strategic thinker – can see the big picture
 Forthright – can push forwards when the going
gets hard.

11. 11
What Makes a Good Architect?
The hard stuff
 Technology knowledge:
• Technologies – broad and narrow
• Product stack
• Scalability
• Security – inside and outside the network
• Reliability
 Design capabilities:
• Patterns and practices
• SOA, UI design, workflow

12. 12
What Makes a Good Architect?
The sort-of soft stuff
 Project Management skills:
• Scope management
• Change management
• Requirements management
• Contract management
• Estimation
• Schedule management
 Methodologies. That’s plural.
 Test Approaches & Management

13. 13
What Makes a Good Architect?
The soft stuff
 Presentation skills
 Team leading skills
 Mentoring skills
 Excellent writing skills
 Excellent communication skills

14. Growing Architects

15. 15
Developers to Architects
An Architect isn't just a smart Developer
 Technical things Architects need:
• The whole picture
• Detail in part of the picture
• Patterns and practices
• The product stack
 Non-technical things:
• Leadership skills
• Communication skills
• Project management

16. 16
Developers to Architects
What should developers learn?
 Patterns and Practices
 The product stacks etc
 Methodologies
 Architecture Training
 Project Management Training
 Consider communications training
 Encourage involvement within and outside
projects
 Encourage developers to grow beyond code

17. 17
Creating an Architecture Team
 Build a team structure
 Put the right people at the top of the structure
 Build a career progression plan
• Training
• Skills
• Projects
 Encourage the right behaviours
• KPIs
• Recognition

18. 18
Creating an Architecture Team
 Build an Architecture Practice
 Build a Mentoring framework
 Use progression plans to encourage broader
skills.
 Develop KPI’s to encourage behaviour
 Use Web 2.0 tools to encourage interaction
 Architecture BOK – Process Mentor

19. 19
Contact Points
 Email: kevin.francis@objectconsulting.com.au
 Blog: http://msmvps.com/blogs/architecture/
 Object: www.objectconsulting.com.au
 Process Mentor: www.processmentor.com