Who We Are Werner Conzelmann

CATWORKX MIDSUMMER DAY 2016 ALM WITH ATLASSIAN-TOOLS IN SUPPLY CHAIN

WERNER CONZELMANN, HARMAN JUNE 17

1. Who we are

2. Facts

3. From requirement to developer

4. From developer to product

5. Challenges

6. Overview

7. Questions

• $6.825 Billion revenues* • 29,000 Professionals worldwide • 6,100 Patents and patents pending • EBITDA $825 Million* • 12,600 Engineers • 56 Design awards in 2015 • EPS $6.20* • 25+ Countries: Americas, Europe • 3 GRAMMY® Awards-AKG, JBL, • $23 Billion automotive order backlog** and Asia Lexicon *FY2016 Guidance • 16+ Legendary brands • 2 Academy Awards **As of June 30, 2015

MARKET LEADER GLOBALLY DIVERSE INNOVATION LEADER

• Over 80 years of industry groundbreaking “firsts” 2004 1999 JBL one of first to HK Soundsticks debut 1953 1975 release audio docks for iPod. at MOMA Harman Kardon Becker launches introduces first FM tuner first car cassette radio 2008 STC joins OHA and enables Android for the CDMA market 1958 1983 1928 Harman Kardon Crown taps JBL to 2002 World’s first talking movie releases the world’s develop first THX licensed system features Lansing’s Three JBL first stereo receiver HD loudspeakers engineers receive 2012 1989 Academy Awards JBL introduces Flip 1953 Digitech Whammy 1970’s AKG invents world’s first 2004 first dynamic cardiod JBL co-develops foot-controlled pitch 2013 Harman microphone the Wall Of Sound shifting guitar pedal STC developed the first dual-sided for the Grateful Dead enables first smartphone for Yota 1949 Bluetooth wireless Crown introduces first 1997 1984 connectivity open reel tape recorder First car 1971 JBL in Lincoln Town Car in the car with built-in power amp radio/CD/nav. DBX brings Premiers as First OEM system realism Branded Car Audio System 2014 of live HARMAN wins 1937 1991 MGM-Lansing sound performance third GRAMMY 1956 AKG binaural System wins first of to 1983 / Sidney Harman buys out two Academy Awards recorded George Lucas selects JBL to products used on Bernard Kardon and music develop the first THX licensed Mir Space Station 2015 creates Harman International theater audio system STC launches Marimba Cloud– World’s 1948 first, most comprehensive cloud based First ever 1987 IoT management platform in-car radio 1969 Martin lights up the JBL powers first of dance floor with disco lights and three Woodstocks fog machines

CONNECTED CAR LIFESTYLE AUDIO PROFESSIONAL CONNECTED SOLUTIONS SERVICES

Navigation, Multimedia, Premium Branded Audio products Audio, Lighting, Video Switching Cloud, Mobility and Analytics Connectivity, Telematics, Safety for use at home, in and Enterprise Automation for Software Solutions & OTA update & Security Solutions the car and on the go Entertainment and Enterprises technologies for Automotive, Mobile and Enterprises

LTM Revenue $3,018M LTM Revenue* $2,023M LTM Revenue* $1,013M LTM Revenue* $682M

LTM EBITDA 13.7% LTM EBITDA 14.7% LTM EBITDA 13.2% LTM EBITDA 13.7%

EBITDA is non-GAAP measure and excludes restructuring, non-recurring charges and acquisition-related items. LTM = Last Twelve Months ending March 31, 2016. *Includes intercompany revenues. HARMAN International. Confidential. Copyright 2016. 5 Who we are

Werner Conzelmann • Team Lead Global Engineering Tools & ALM, Harman

• in Software Development for 25 years

• responsible for Atlassian Applications at Harman since 2008

Marc Keil • Subject Matter Expert Atlassian Tools

• works with Atlassian Applications since 2011

• has implemented JIRA in uncommon environments (e.g. in Facility Management)

Agenda

1. Who we are

2. Facts

3. From requirement to developer

4. From developer to product

5. Challenges

6. Overview

7. Questions

• JIRA in use in Harman since ~ 2008

• Users > 9000

• Current release in use 6.4.13

• No. of projects ~ 900

• No. of issues ~ 490.000

Facts

Development target: „Automotive Infotainment System“:

• Domains: ~ 60

• Customer requirements: ~ 50.000

• Features to be developed: ~10.000

~10.000 is the initial amount of JIRA tasks for feature implementation only

1. Who we are

2. Facts

3. From requirement to developer

4. From developer to product

5. Challenges

6. Overview

7. Questions

Feature Nav Harman Requirements Management

Feature Nav Domain Disp Task Magic Customer Harman TRS Requirements Documents Feature Nav (domain specific Documents documents) Domain Map Task

Harman Requirements Management Harman JIRA – Task Management Feature Nav Main Tasks Sub-Tasks Feature Nav Feature Nav Required for Do. Disp -Task 1 Domain Disp Release x Required for Rel at CW Workpackage A

Feature Nav Feature Nav Domain Disp Domain Disp Task Workpackage B

Feature Nav Feature Nav Feature Nav Domain Map Do. Map - Task 2 Domain Map Task Required for Rel at CW Workpackage C

• Main tasks in JIRA will be assigned Harman JIRA – Task Management to functional owner of domain

Main Tasks Sub-Tasks • After review 1-n subtasks will be Feature Nav Feature Nav created (criteria for # of subtasks: Domain Disp Domain Disp complexity, architecture, effort …) Task 1 Workpackage A

Feature Nav • Subtask has to be assigned to Domain Disp Workpackage B developer by FO or by Senior developer Feature Nav Feature Nav Domain Map Domain Map • Developer will create Feature Task 2 Workpackage C Branch in Stash (Bitbucket)

1. Who we are

2. Facts

3. From requirement to developer

4. From developer to product

5. Challenges

6. Overview

7. Questions

Harman JIRA – Task Management • Developer is working in Stash until Sub-Tasks solution fulfills functional and quality Workflow criteria Feature Nav Domain Disp Workpackage A In Implementation • By pull request in Stash, JIRA subtask status will be switched to

Stash „Ready for Integration in Module“ Pull request status

Ready for Integration • This way, subtask is completed for in Module developer

• Domain Workpackages will be Harman JIRA – Task Management integrated in Master Branch by Sub-Tasks Main Tasks Continuous Integration (CI – Feature Nav Feature Nav Bamboo) (optional) Domain Disp Domain Disp Workpackage A Task 1 • Features (Main Tasks) can be Feature Nav tested on Domain level, after all Domain Disp Workpackages have been Workpackage B completed

Feature Nav Feature Nav • Release branches will be managed Domain Map Domain Map Workpackage C Task 2 more restrictive

• Feature overall Harman JIRA – Task Management Harman Requirements Management status will be generated in RM Sub-Tasks Main Tasks Feature Nav tooling Feature F1 Feature Nav Domain 1 Domain Disp Required for Workpackage A Task 1 Release x • Test management (TMS) is using that Feature F1 Feature Nav information for Domain 1 Domain Disp Workpackage B Part system tests

Feature F1 Feature Nav Feature Nav • Feature reportings Domain 1 Domain Map Domain Map will be done from Workpackage C Task 2 Part that point HARMAN International. Confidential. Copyright 2016. 18 Agenda

1. Who we are

2. Facts

3. From requirement to developer

4. From developer to product

5. Challenges

6. Overview

7. Questions

Harman JIRA

Main Tasks Sync Plugin • External suppliers are working with Feature F1 Developed by their own JIRA Domain Suppl catWorkX Task x • Harman is requested by customer to transfer domain specific tasks to supplier JIRA Supplier JIRA

Main Tasks • “Sync“ is implemented by custom Feature F1 solution, developed by catWorkX Domain Suppl Task y

• Domain and Project integration are Harman JIRA – Task Management supported by „Integration Tasks“

Sub-Tasks Main Tasks • „Integration Tasks are using „Issue Feature F1 Feature F1 Picker“ plugin, to collect Domain 1 Domain 1 workpackages/tasks which have Workpackage A Task 1 been implemented Feature F1 Domain 1 Workpackage B Issue Picker Developed by Feature F1 Feature F1 catWorkX Domain 1 Domain 2 Workpackage C Task 2

1. Who we are

2. Facts

3. From requirement to developer

4. From developer to product

5. Challenges

6. Overview

7. Questions

Requirements Engineering Task Management TOOL Source Code Management TOOL TOOL Jira Issue Feature Domain 1 Branch Jira Issue WP A WP A Domain 1 Feature F1 Integration Jira Issue Feature Branch Domain 1 Projekt Requirements WP B WP B Integration

Jira Issue Feature Domain 2 Jira Issue Domain 2 Branch Integration Feature F2 WP C WP C

1. Who we are

2. Facts

3. From requirement to developer

4. From developer to product

5. Challenges

6. Overview

7. Questions

Thanks for attention!

WERNER CONZELMANN, HARMAN JUNE 17