Competence & Leadership Development Program. for. Hightech Systems Architects. Domain architect level

Transcription

1 Competence & Development Program for Hightech Systems Architects Domain architect level For those who want to lead technology without leaving technology For more information:

2 Program overview (27 days) Company Assignment & Personal Ambition Intake Kick off (2) Role of the architect (3) Technical (1) Architecting for Hightech Embedded Systems (4) Models & Principles for Architectural Analysis (4) Company assignment + personal coach Technical (1) System Integration & Test (4) Architecture Assessment (3) Technical (1) System Reliability (3) Technical (1) Application in own organization Duration: 14 months

3 View on architecture & architects Problem space Domain of the Customer/User Solution space Domain of the Developer Market & Product Strategy (why) High Level System Design (how) Value Proposition (what) strategic marketing (focus on market position & value) system architect (focus on design strategy) 3

4 Mono d iscipline Mono discipline Mono discipline Mono discipline Focus Positioning the program When Why Market and customer context Product Lifecycle Context What How System Architecting (Multidisciplinar) Design With Technical Focus of the program is on architecting & design on a (sub)system level in the early phases of product development in a broader business & product innovation context. 4

5 Learning & Development goals General Accelerate corporate strategy on system/architectural level (= company) Develop system level design capabilities for complex high-tech products with special attention to architecting and technical leadership skills (= participant) Architecting competenties System level architecting & reasoning Models & principles for architectural analysis System Integration & Test System qualities (performance, reliability,..) Architecture assessment Architecting Roles & Responsibilities Technical leadership & influencing skills Application Deployment of architecting competencies and leadership skills on the participant s own working environment. 5

6 Target group participants Professionals in high tech industry: that are ready for a next step in their professional development (6-10 yrs experience); with the ambition & potential to take responsibility for the design of a meaningful system component, subsystem or dominant system function. What you KNOW What you DO What you ARE who want to operate in a broader Organizational Politics organizational and system icontext. Strategy Consulting Technology 6

7 Training concept 1. Challenging goals Stretch participants and go beyond individual s comfort zone to create learning that sticks. 2. Interaction based learning Strong interaction between lecturers, participants, peers and others (e.g. guest speakers & management team). 3. Real world context Reflect on architecting challenges by using industrial cases, realistic examples and proven approaches so that participants can relate to content effectively. 4. Applicable to daily work Company assignment and personal goals are leading during the training program. Combination of practice, theory, leadership skills and personal coaching in a multi-company environment. 7

8 Stakeholder commitments 1. Company commitment: To provide a challenging architecting assignment on (sub)system level. Personal coaching by senior architect. 2. Participant commitment: Strong ambition to operate at Domain Architect level. Personal goal to: Take responsibility for architecture on a subsystem or system function level; Improve leadership skills; Acquire and apply (new) architecting methods. 3. ESI commitment: State of the art training program. Provide added value for both participant and company. Top-level teachers & trainers. Personal coaching for application of architecting methods. 8

9 Program overview (27 days) Company Assignment & Personal Ambition Intake Kick off (2) Role of the architect (3) Technical (1) Architecting for Hightech Embedded Systems (4) Models & Principles for Architectural Analysis (4) Company assignment + personal coach Technical (1) System Integration & Test (4) Architecture Assessment (3) Technical (1) System Reliability (3) Technical (1) Application in own organization Duration: 14 months

10 Company assignment & personal Coaching Company assignment During the program each participant works on his/her own company case on a (sub)system level Cases should be visible on, and sponsored by, senior R&D management Master apprentice relationship Each participant receives a personal coach Company project + individual learning goals are leading for (monthly) coaching sessions Main coaching theme s: What you KNOW (= architecting); What you DO (= architecture); What you ARE (= architect). 10

11 Module 1: Role of the architect (3 days) Observation Having good technical skills and being able to articulate a good architecture is very important and the major focus of an architect s work, but most architecting projects ultimately succeed for people reasons. Objectives Roles involved in architecture programs are considered, and what they can do to contribute to the success or failure of architecture; Create a shift in how architects perceive their roles; What you KNOW What you DO What you ARE Provide models, tools and skills that will help make architectures more successful; Build awareness of the role architects ought to be playing and the role they are actually playing, and how they could be more effective. Organization al Politics Strategy Consulting Technology 11

12 Module 2: Architecting for Hightech Embedded Systems (4 days) Observation For an architecture it is important that it fits in the context and has a sound design. In order to realize this system architects must combine gathered information from multiple stakeholders into a coherent overview. Objectives Offer architects a framework that helps them to combine and present information in a structured way. 12

13 Module 3: Modeling & Principles for Architectural Analysis (4 days) Observation Architects work in a ill-defined environment. A broad spectrum of modeling and structured analysis techniques is being used to improve the efficiency and effectiveness of the design process and to predict the impact of design decisions. Objectives Provide the participants understanding how to work with models to: Link between product business goals and design requirements; Calibrate models with measurements and data, and perform proper sensitivity analysis to increase model credibility; Address difficult tensions in the design that call for trade-off decisions based on insight. 13

14 Module 4: System Integration & Test (4 days) Observation System complexity raises when a system is designed and built by more people from different disciplines (number of parts and emergent behavior). As architectural decisions can have a huge impact on the way a system is integrated it is important to address integration throughout the whole product creation process. Objectives Know how to create a system architecture & integration plan and be able to validate it in a efficient way; Provide a broad overview of system integration strategies, related processes, and methods; Provide insight and understanding in the relationship between the overall product creation process, architecture and system integration & test. Organizational Processes Business Objectives Integrating and Testing Your Product Managing it all Required knowledge and skills 14

15 Module 5: Architecture Assessment (3 days) Observation In early phases of product (re)design multiple design decisions are being made. Evaluation and assessment of architectural decicions, design alternatives, design criteria and trade-offs are key activities during the architecting process as architectural choices can have a huge impact on product realisation, product life cycle and business in general. Objectives Know how to assess whether architecture and design cover business goals and requirements; Determine the critical spots in the architecture Assess whether tensions have been properly handled in design and communication; Elicit the most important concerns from the stakeholders; Understand why particular decisions have been taken number of details system sub system 10 monodisciplinary 10 8 multidisciplinary 15

16 Module 6: System Reliability (3 days) Observation Meeting reliability requirements is very important from a business point of view. Companies deal with system reliability in various ways. There is no single solution. Architecture & architects play an important role in reaching the desired level of system reliability but are not the only stakeholders active in this field. Objectives Provide participants understanding and knowledge of: The impact of system reliability on all aspects of a business and how it affects architects; Reliability improvement processes; Various reliability definitions and terms and how to quantify them; The influence of the reliability characteristics of hardware and software on system reliability; Various methodologies and processes to improve product reliability; Engineering techniques and methods to build a reliable system; Architecting for reliability; Present reliability issues to management. 16

17 Technical modules Objectives Support development of leadership skills for architects by: A competency assessment; A leadership development framework based on 8 core competences; Focused career guidance and development. Overview skills development approach: Intake; Preparation (360 0 feedback); Program kick off (creating awareness of competencies and skills); Four 1-day training sessions; Influence without authority; Organizational politics; Create commitment; Core qualities + self assessment. 17