2014 workshop and plenary sandra hoskins, i.s.p, itcp, pmp, mba cips – canada’s it professional...
TRANSCRIPT
2014 Workshop and Plenary
EA Role Workshop
Sandra Hoskins, I.S.P, ITCP, PMP, MBACIPS – Canada’s IT Professional OrganizationIIBA – International Institute of Business AnalysisFEAPO - Secretariat
2014 Workshop and Plenary
Goal – Process – Decisions
ProcessDetermine next stepsValidate initial roles
DecisionsCreate a list of roles that we agree to use todayRecommend / approve further exploration
Goal: To validate the roles proposed based on collaborative work prior to and including the June summit
2014 Workshop and Plenary
Definitions Impacting Roles
Role – Who Does Whatmust focus on skills must be applicable across a broad section of an industry or organizationmust be flexible to address to forward focus of an EA career path
Responsibility – Who Decides Whataddresses the critical decision points where an EA will be able to contribute to the success of the organizationaligned on the organizational processes and decision making practices and protocolfacilitates collaboration and decision-making
f
2014 Workshop and Plenary
Definitions Impacting Roles
Accountability – Owning the outcome of the decisionsthe critical component to the role and responsibility definitions is the level of accountability that must be assumed by any professional that in the role of an Enterprise Architect
Authoritywhat level of authority do you expect that the EA to have?
at a minimum, they must be able to make the recommendations for decisions that affect business success
2014 Workshop and Plenary
Roles FrameworkSummary of Career Path, Families, and Roles
Families: Paths:
Security Infrastructure Technical Integration Information/
Data Business General
Enterprise Architecture Family Roles
Chief Security
Architect Chief
Infrastructure Architect
Chief Technical/ Application
Architect
Chief Integration Architect
Chief Information/
Data Architect
Chief Business Architect
Chief Architect
Enterprise Security Architect
Enterprise Infrastructure
Architect
Enterprise Technical/ Application
Architect
Enterprise Integration Architect
Enterprise Information/
Data Architect
Enterprise Business Architect
Enterprise Architect
Solution Architecture Family Roles
Senior
Security Architect
Senior Infrastructure
Architect
Senior Technical/ Application
Architect
Senior Integration Architect
Senior Information/
Data Architect
Senior Business Architect
Lead or Solution Architect
Security Architect
Infrastructure Architect
Technical/ Application
Architect
Integration Architect
Information/ Data Architect
Business Architect
Design and Analyst Family Roles
Security Analyst
Network and Comm. Architecture Operating and Platform Architecture
Technical/ Application
Analyst
Integration Analyst
Data Modeler Business Analyst
Process
Architecture
Network Design
Software Design/
Developer
Data Analyst UI Designer
What level of expertise is implied by “general”?
Business (incl. Business Process Management?)
Security (Physical and Solution)
Data Management
Solution Architecture (incl Integration?)
Quality?
Enterprise Infrastructure (how is this different from Technology?)
2014 Workshop and Plenary
Role Advancement Path
How many levels should there be?Is Senior, Intermediate and Entry level appropriate?Can we align years of experience across competencies to determine where the experience matches the role?Should the levels be determined by job function?How do we provide an integrated role definition that includes
the enterprisethe technologythe people
How do we make generic levels that can be applicable across a broad mix of industries?