Issus for improving Quantity and Quality of Collaboration between RD/PT2 ←→ RDI/CDV

Iniziamo. È gratuito!
o registrati con il tuo indirizzo email
Issus for improving Quantity and Quality of Collaboration between RD/PT2 ←→ RDI/CDV da Mind Map: Issus for improving Quantity and Quality of Collaboration between RD/PT2 ←→ RDI/CDV

1. Organization

1.1. Germany RD/PT2

1.1.1. Monitoring

1.1.2. Planning

1.1.3. Realization

1.1.4. Role Distribution Impat Justification Criterias Benefits Scope for Colaboration E4

1.2. India RDI/CDV

1.2.1. Monitoring Personal Development Trainings Skill-Matrix Team Development Monthly Meeting Skill Matrix Efficency Task Tracker Timesheets

1.2.2. Planning Rotation-Schedule Justification Criterias Meetings Date Frequency Content

1.2.3. Realization

1.2.4. Role Distribution L4/L5 Engineers

1.3. India ←→ Germany RDI/CDV←→RD/PT2

1.3.1. Monitoring MRM Utilization Distribution Efficency BTV Instant Evaluation Tracking

1.3.2. Planning Onsite-Engineer Justification Criteria Scope for Colaboration Task-Flow Meetings

1.3.3. Realization

1.3.4. Role Distribution Impat Onsite Engineer Coordinator

2. Motivation

2.1. Feedback

2.1.1. From Germany Honest Feedback Praise Constructive critiques Including L4/L5 Confidence Promt Feedback Directly from BTV Oral Email webcam stucurized specific/detailed be aware of the cultur Iteration loop

2.1.2. In India Dialog

2.2. Appreciation/ Involvement

2.2.1. From Germany Personal relation to German engineers Resposibilities BTV's Projects Tasks Interest in culture Attandence in India Recognize Ideas More Information about whole FDCT Share Expertise News Help to help themselves Contribution to the greater whole Use English slides Onsite Engineer Activities Team Building

2.2.2. In India Salary Career chances Hierarchy Trips to Germany Responsibilities More Hardware

3. Communication

3.1. Flow of commonucation

3.1.1. Assignment of Tasks Packages Task Relevant Informations Contacts Backround Clear Pririorities avoid Task changes

3.1.2. Involve whole Team Swarm Intelligence Proper Distribution of Tasks

3.1.3. Standarizised Handover of tasks Clear Structure Ensure Understanding "Poka Yoke"

3.1.4. Flexible for direct contact

3.2. Way of communication

3.2.1. Use of new Media Parallel Channels Webcam Headset VC

3.3. Misunderstandings

3.3.1. Language Clear voice English/German

3.3.2. missing integrety

3.3.3. lack of understanding

3.3.4. no direct request for issues

3.3.5. Terms for Components Structure register

4. Culture

4.1. Contacting

4.1.1. Face to Face

4.1.2. personal contact/know each other

4.1.3. relationship

4.1.4. Different reaction/reply

4.2. Language

4.2.1. Interpretation/context

4.2.2. different clarification of tasks

4.3. Will/Way of continuous Optimization

4.4. Scheduling

4.4.1. time shift (4,5h)

4.4.2. Holidays

4.4.3. Vacations

5. Resources

5.1. Facilities Workplace

5.1.1. Communication Devices Webcam Phone Headset Skype/Lync VC Rooms

5.1.2. CAE/CAD Assets Laptops Workstations 3D-Spacemouse

5.1.3. Meeting-Rooms VC Rooms Think-Tanks Scheduling

5.2. Resource Management

5.3. Human Resources

5.3.1. Recruiting Who Why

5.3.2. Probper Induction Mentor Trainings Overview

5.3.3. Promotion Social technical

5.3.4. Team Team Building Keep "Crew" together Limit internal switching Standarize Tasktransfer for Dropouts