Shield: Product Development in a Distributed Team
(Case study No: 06/2005-5285)
Assignment Case Study
Table of Contents
1Executive Summary Ã¯Â¿Â½
2Managing Global Complexity in the DRM Software Industry Ã¯Â¿Â½
3Flux and Speed Ã¯Â¿Â½
3The Cultures of Infotech and Professional Ã¯Â¿Â½
3Organisational Culture Ã¯Â¿Â½
5Culture Model - Gofee and Jones Ã¯Â¿Â½
6Team Motivation Ã¯Â¿Â½
7Performance Management Ã¯Â¿Â½
7Goal-setting Theory Ã¯Â¿Â½
8Performance Management Analysis Ã¯Â¿Â½
13Appendix A: Complexity Ã¯Â¿Â½
14Appendix B: Macro Environment (PEST) of the DRM Industry Ã¯Â¿Â½
15Appendix C: Geert Hofstede 5D model for India and USA Ã¯Â¿Â½
16Appendix D: Herzberg Hygiene and Motivator Factors Ã¯Â¿Â½
17Appendix E: Implementation Plan Ã¯Â¿Â½
Executive Summary 366
Main Text 2986
Shield is the code name for a Digital Rights Management (DRM) 'suite of software components for tracking and protection of digital property rights' that is being developed with the goal of having the language for expressing digital rights being accepted as the industry standard and then planning for their suite becoming the best DRM software on the market.
The development is being undertaken by two teams; Infotech is based in USA and the Professional is based in India.
Two of the key Manager's departed from the team prior to the software entering the commercialisation stage and a decision was made not to replace them but to employ engineers into the Infotech team. This decision has resulted in Infotech not passing on responsibility for the project as they thought they could do the work themselves; not recognising the value Professional brought to the project. Professional has attempted to fulfil their believed responsibilities but with realisation of the changing level of autonomy there was significant disappointment within the team...