Saf08 Growing Architects Kevin Francis

Post on 24-Jun-2015

629 views 0 download

Tags:

description

Presentation from SAF08 - Managing Architect Careers for Managers

transcript

Growing Architects

Kevin FrancisPractices & Productivity ManagerObject Consulting

Background – me and architectureTypes of ArchitectsArchitecture Career PathsArchitect skill requirements

What We Will CoverAre you in the right session?

My BackgroundWhy should I be talking about this?

Developer and OperationsArchitect and ConsultantEnterprise ArchitectProject Manager and Business OwnerPrincipal ArchitectDelivery ManagerExecutive – Strategic ManagementMVP and Community Work

Solution Architect

Application Architect

Application Architect

Application Architect

Data Architect

User Interface Architect

Application Architect

Types of ArchitectsIt isn't all about code…

User Interface

Business Layer

Application

Application

SupplierDatabase

Business Layer

Business Layer

Business Layer

Integration Architect

Infrastructure Architect

Paths into ArchitectureIt still isn't all about code…

Developer

Solution Architec

t

UI Archite

ct

Business Analyst

Almost Anyone

Business Analyst

IT Support

Snr Data

Architect

SOA Architect

Snr Project

Manager

Infrastructure Manager

Integration

Architect

Data Architec

t

Project Manager

Infrastructure Architect

Application

Architect

What is Architecture?It's all about technology, right?

Designing all or part of a system to meet the functional and non-functional requirementsDesigning the delivery approachManaging riskDelivering to budgetManaging stakeholdersManaging changeContractsExplaining what needs to be doneManaging the development team

Making Developers into ArchitectsAn Architect isn't just a smart DeveloperTechnical things Architects need:

The whole pictureDetail in part of the picturePatterns and practicesThe product stack

Non-technical things:Leadership skillsCommunication skillsProject management

Making Developers into ArchitectsWhat should developers learn?Patterns and Practices

The product stacks etcMethodologiesArchitecture TrainingProject Management TrainingConsider communications trainingEncourage involvement within and outside projectsEncourage developers to grow beyond code

So What Makes a Good Architect?The hard stuffTechnology knowledge:

Technologies – broad and narrowProduct stackScalabilitySecurity – inside and outside the networkReliability

Design capabilities:Patterns and practicesSOA, UI design, workflow

So What Makes a Good Architect?The sort-of soft stuffProject Management skills:

Scope managementChange managementRequirements managementContract managementEstimationSchedule management

Methodologies. That’s plural.Test Approaches & Management

So What Makes a Good Architect?The soft stuff

Presentation skillsTeam leading skillsMentoring skillsExcellent writing skillsExcellent communication skills

Creating an Architecture TeamThe things that have worked for me

Build a team structurePut the right people at the top of the structureBuild a career progression plan

TrainingSkillsProjects

Encourage the right behavioursKPIsRecognition

Creating an Architecture TeamThe things that have worked for me

Build an Architecture PracticeBuilt career progression process & plansBuild a Mentoring frameworkUse progression plans to encourage broader skills.Develop KPI’s to encourage behaviourUse Web 2.0 tools to encourage interactionArchitecture BOK – Process Mentor

Contact Points

Email: kevin.francis@objectconsulting.com.auBlog: http://msmvps.com/blogs/architecture/

Object: www.objectconsulting.com.auProcess Mentor: www.processmentor.com

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after

the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.