ttmg 5001 principles of management for engineers
play

TTMG 5001 Principles of Management for Engineers Session 2: Sep 21 - PowerPoint PPT Presentation

TTMG 5001 Principles of Management for Engineers Session 2: Sep 21 Fall 2011 Michael Weiss www.carleton.ca/tim www.carleton.ca/tim/tim.pdf weiss@sce.carleton.ca Session 2 objectives Upon completion of the session, you will know about


  1. TTMG 5001 Principles of Management for Engineers Session 2: Sep 21 Fall 2011 Michael Weiss www.carleton.ca/tim www.carleton.ca/tim/tim.pdf weiss@sce.carleton.ca

  2. Session 2 objectives Upon completion of the session, you will know about • objective, deliverables, contributions and relevance of literature reviews • differences among the reviews of the product development literature • important topics not being addressed in the literature reviews and you will be able to • access the online library, course files and other course tools • start preparing a literature review • generate lessons learned from reading the reviews of the product development literature • distinguish good from poor literature reviews weiss@sce.carleton.ca Slide 2

  3. Agenda 1. Access to TTMG 5001 files and course tools 2. Access articles using online library 3. Questions about • TTMG 5001 assignments • Gate 0 for TIM thesis and project 4. Summary of assigned readings 5. Additions/modifications to the summary 6. Lessons learned weiss@sce.carleton.ca Slide 3

  4. 1. To access TTMG 5001 files 1. Go to http://cms.sce.carleton.ca 2. Enter the user name and password I sent you 3. Under My courses click on TTMG 5001 Information is organized by topic, and corresponds to the topics in the course outline weiss@sce.carleton.ca Slide 4

  5. Course tools • Files (course outline, slides, readings) • Forums (news and announcements, project groups, course discussion) • Profile (photo, blog) • Events • Recent activity and forum posts • Glossary • Wikis (lessons learned) • Upload files (assignments, exam) weiss@sce.carleton.ca Slide 5

  6. 2. To access articles using online library 1. Go to http://library.carleton.ca 2. Go to Journals & Journal Articles 3. Enter the name of the journal (e.g., Academy of Management Review) in the text box and select "Title" in the left column and "Web resource" in the right column, then click Search 4. Select one of the hot links (e.g., Business Source Complete) 5. Enter your patron bar code number and your PIN 6. Select the year of the journal (e.g., 1995) 7. Select the volume of the journal (e.g., volume 20, issue 2) 8. Select "PDF Full text" under the name of the article you seek (e.g., select PDF Full text under PRODUCT DEVELOPMENT: PAST RESEARCH, PRESENT FINDINGS, AND FUTURE DIRECTIONS) 9. Save or print PDF file weiss@sce.carleton.ca Slide 6

  7. 3. Questions TTMG 5001 Assignments Gate 0 • Objectives • Literature review • Deliverables • Gate 0 • Relevance • Contributions • Theoretical basis (thesis) • Method • Data acquisition • Data analysis • References weiss@sce.carleton.ca Slide 7

  8. 4. Summary • What is a literature review • How to summarize the results of a literature review when making presentations • Objective, deliverables, contribution and relevance • Comparison • Lessons learned • Topics not in the literature reviewed weiss@sce.carleton.ca Slide 8

  9. What is a literature review? • Literature review is a summary and interpretation of research findings reported in the literature • It presents major ideas in the state of the art right up to, but not including, your own ideas • You organize the literature review by idea (streams), not by author or by publication • Each literature review uses a perspective to examine one or more domains weiss@sce.carleton.ca Slide 9

  10. How to summarize • Table that shows: – Literature streams reviewed – Key highlights for each literature stream reviewed – Key references • Lessons learned from the literature review that link to contributions you wish to make • References weiss@sce.carleton.ca Slide 10

  11. Literature review Stream Key highlights of the stream Key references Code release • Motives of firms to release code as open source Lerner & Tirole (2002) Goldman & Gabriel (2005) • Risks of releasing code as open source Henkel (2003) Open source • Description and classification of open source Bonaccorsi & Rossi (2005) license licenses Lerner & Tirole (2002) Chesbrough & Rosenbaum (2000) Open source • Key elements of business model business Hecker (1999) • Key elements of software business model models Morris et al. (2005) • Categorization of open source business models • Revenue model for open source software producer Open source • Motives of individuals to contribute to open source Bonaccorsi & Rossi (2004) software projects Hecker (1999) Raymond (1999) • Motives of firms to contribute to open source projects Wichmann (2002) Software • Software taxonomy Spiller & Wichmann (2002) Valimaki & Oksanen (2002) • Software value chain Value creation • Value and value net Bowman & Ambrosini (2000) and Brandenburger & Nalebuff (1996) • Process of value creation and appropriation appropriation Brandenburger & Stuart (1996) • PARTS framework weiss@sce.carleton.ca Slide 11

  12. Lessons learned from literature review • Lack of research on when to release code as open source – How companies create and appropriate value – How companies create use value and realize exchange value – How companies adjust business models to code release – Risks of releasing code as open source • Added value method can be used to assess firm’s ability to capture value from interactions with others • PARTS framework can be used to assess if company can change a business game in its favor weiss@sce.carleton.ca Slide 12

  13. References • Bonaccorsi, A. & Rossi, C. 2004. Comparing motivations of individual programmers and firms to take part in the open source movement. From community to business. http://opensource.mit.edu/papers/bnaccorsirossimotivationlong.pdf • Bonaccorsi, A. & Rossi, C. 2005. Licensing schemes in the production and distribution of open source software. An empirical investigation. http:// opensource.mit.edu/papers/bnaccorsirossilicense.pdf • Bowman, C. & Ambrosini, V. 2000. Value creation versus value capture: Towards a coherent definition of value in strategy. British Journal of Management, 11: 1-15 • Brandenburger, A. M. & Nalebuff, B. J. 1996. Coopetition. Bantam Doubleday Dell Publishing Group, Inc • Brandenburger, A. M. & Stuart, H. W. 1996. Value-based strategy. Journal of Economics & Management Strategy, 5: 5-24 • Chesbrough, H. & Rosenbaum, R. S. 2002. The role of the business model in capturing value from innovation: evidence from Xerox Corporation’s technology spin-off companies. Industry and Corporate Change, 11(3): 529-555 • Gabriel, R. P. & Goldman, R. 2005. Innovation happens elsewhere. Morgan Kaufmann Publishers • Hecker, F. 1999. Setting up shop: The business of open-source software. IEEE Software, 16(1): 45-51 • Henkel, J. 2003. Open source software from commercial firms – Tools, complements, and collective invention. http://www.inno-tec.bwl.uni-muenchen.de/forschung/henkel/OSS_JHenkel_2003-05.pdf weiss@sce.carleton.ca Slide 13

  14. Objective of three articles assigned • Objective (i.e., purpose, goal) of these articles is to review the product development literature. Shane and Ulrich (2004) also review the technological innovation and entrepreneurship literatures • Brown, S. L., & Eisenhardt, K. M. 1995. Product development: Past research, present findings and future directions. Academy of Management Review, 20(2): 343-378. • Krishnan, V., & Ulrich, K. 2001. Product development decisions: A review of the literature. Management Science, 47(1): 1-21. • Shane, S., & Ulrich, K.T. 2004. Technological innovation, product development and entrepreneurship in Management Science. Management Science, 50(2): 133-144. weiss@sce.carleton.ca Slide 14

  15. Other literature reviews • Balachandra, R. and Friar, J.H. 1997. Factors for success in R&D projects and new product innovation: A contextual framework. IEEE Transactions on Engineering Management, 4(August): 276-288. • Cusumano, M. A., & Nobeoka, K. 1992. Strategy, structure and performance in product development – observations from the auto industry. Research Policy, 21(June): 265-293. • Finger, S., & Dixon, 1989a. A review of research in mechanical engineering design, part I: Descriptive, prescriptive, and computer based models of design processes. Research in Engineering Design, 1(1): 51-68. • Finger, S., & Dixon, 1989b. A review of research in mechanical engineering design, part II: Representations, analysis, and design for the life cycle. Research in Engineering Design,1(2): 121-137. • Gerwin, D., & Barrowman, N. J. 2002. An evaluation of research on integrated product development. Management Science, 48(7): 938-953. • Griffin, A., & Hauser, J. R. 1996. Integrating R&D and marketing: A review and analysis of the literature. Journal of Product Innovation Management, 13(3): 191-125. • Schilling, M., & Hill, C. 1998. Managing the new product development process: Strategic imperatives. Academy of Management Executive, 12(3): 67-81. • Whitney, D. E. 1990. Designing the design process. Research in Engineering Design, 2(2): 3-13. weiss@sce.carleton.ca Slide 15

Recommend


More recommend