{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,9,28]],"date-time":"2025-09-28T15:32:38Z","timestamp":1759073558796},"publisher-location":"Berlin, Heidelberg","reference-count":58,"publisher":"Springer Berlin Heidelberg","isbn-type":[{"type":"print","value":"9783540346821"},{"type":"electronic","value":"9783540346838"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":[],"published-print":{"date-parts":[[2006]]},"DOI":"10.1007\/11767718_9","type":"book-chapter","created":{"date-parts":[[2006,9,18]],"date-time":"2006-09-18T12:04:58Z","timestamp":1158581098000},"page":"61-78","source":"Crossref","is-referenced-by-count":4,"title":["Troubleshooting Large-Scale New Product Development Embedded Software Projects"],"prefix":"10.1007","author":[{"given":"Petri","family":"Kettunen","sequence":"first","affiliation":[]}],"member":"297","reference":[{"issue":"11","key":"9_CR1","doi-asserted-by":"crossref","first-page":"39","DOI":"10.1109\/2.963442","volume":"34","author":"S. Farbman White","year":"2001","unstructured":"Farbman White, S., Melhart, B.E., Lawson, H.W.: Engineering Computer-Based Systems: Meeting the Challenge. IEEE Computer\u00a034(11), 39\u201343 (2001)","journal-title":"IEEE Computer"},{"issue":"1","key":"9_CR2","doi-asserted-by":"crossref","first-page":"37","DOI":"10.2307\/41165820","volume":"38","author":"M. Iansiti","year":"1995","unstructured":"Iansiti, M.: Shooting the Rapids: Managing Product Development in Turbulent Environ-ments. California Management Review\u00a038(1), 37\u201358 (1995)","journal-title":"California Management Review"},{"issue":"1","key":"9_CR3","doi-asserted-by":"publisher","first-page":"133","DOI":"10.1287\/mnsc.47.1.133.10663","volume":"47","author":"A. MacCormack","year":"2001","unstructured":"MacCormack, A., Verganti, R., Iansiti, M.: Developing Products on \u201cInternet Time\u201d: The Anatomy of a Flexible Development Process. Management Science\u00a047(1), 133\u2013150 (2001)","journal-title":"Management Science"},{"key":"9_CR4","doi-asserted-by":"publisher","first-page":"224","DOI":"10.1016\/S0737-6782(97)00081-7","volume":"15","author":"J.W. Mullins","year":"1998","unstructured":"Mullins, J.W., Sutherland, D.J.: New Product Development in Rapidly Changing Markets: An Exploratory Study. Journal of Product Innovation Management\u00a015, 224\u2013236 (1998)","journal-title":"Journal of Product Innovation Management"},{"issue":"1","key":"9_CR5","doi-asserted-by":"publisher","first-page":"32","DOI":"10.1109\/52.62930","volume":"8","author":"B.W. Boehm","year":"1991","unstructured":"Boehm, B.W.: Software Risk Management: Principles and Practices. IEEE Software\u00a08(1), 32\u201341 (1991)","journal-title":"IEEE Software"},{"key":"9_CR6","volume-title":"Walzing with Bears: Managing Risks On Software Projects","author":"T. DeMarco","year":"2003","unstructured":"DeMarco, T., Lister, T.: Walzing with Bears: Managing Risks On Software Projects. Dorset House Publishing, New York (2003)"},{"key":"9_CR7","unstructured":"Kontio, J.: Software engineering risk management: a method, improvement framework, and empirical evaluation. Helsinki University of Technology (2001)"},{"key":"9_CR8","volume-title":"Software Runaways","author":"R.L. Glass","year":"1998","unstructured":"Glass, R.L.: Software Runaways. Prentice-Hall, Upper Saddle River (1998)"},{"issue":"4","key":"9_CR9","doi-asserted-by":"crossref","first-page":"5","DOI":"10.1177\/875697280403500403","volume":"35","author":"A. Pavlak","year":"2004","unstructured":"Pavlak, A.: Project Troubleshooting: Tiger Teams for Reactive Risk Management. Project Management Journal\u00a035(4), 5\u201314 (2004)","journal-title":"Project Management Journal"},{"key":"9_CR10","doi-asserted-by":"publisher","first-page":"915","DOI":"10.1016\/S0166-4972(03)00033-6","volume":"24","author":"Y.H. Kwak","year":"2004","unstructured":"Kwak, Y.H., Stoddard, J.: Project risk management: lessons learned from software development environment. Technovation\u00a024, 915\u2013920 (2004)","journal-title":"Technovation"},{"key":"9_CR11","doi-asserted-by":"publisher","first-page":"144","DOI":"10.1016\/S0737-6782(01)00134-5","volume":"19","author":"W.A. Sheremata","year":"2002","unstructured":"Sheremata, W.A.: Finding and solving problems in software new product development. Journal of Product Innovation Management\u00a019, 144\u2013158 (2002)","journal-title":"Journal of Product Innovation Management"},{"issue":"3","key":"9_CR12","doi-asserted-by":"publisher","first-page":"83","DOI":"10.1109\/52.589242","volume":"14","author":"E.H. Conrow","year":"1997","unstructured":"Conrow, E.H., Shishido, P.S.: Implementing Risk Management on Software Intensive Projects. IEEE Software\u00a014(3), 83\u201389 (1997)","journal-title":"IEEE Software"},{"issue":"4","key":"9_CR13","first-page":"16","volume":"15","author":"M.W. Evans","year":"2002","unstructured":"Evans, M.W., Abela, A.M., Belz, T.: Seven Characteristics of Dysfunctional Software Projects. CrossTalk\u00a015(4), 16\u201320 (2002)","journal-title":"CrossTalk"},{"key":"9_CR14","unstructured":"Houston, D.: Results of Survey on Potential Effects of Major Software Development Risk Factors (1999) (accessed, February 2005), http:\/\/www.eas.asu.edu\/~sdm\/dhouston\/risksrvy.htm"},{"key":"9_CR15","volume-title":"Patterns of Software System Failure and Success","author":"C. Jones","year":"1996","unstructured":"Jones, C.: Patterns of Software System Failure and Success. International Thompson Computer Press, Boston (1996)"},{"issue":"7","key":"9_CR16","first-page":"9","volume":"11","author":"L.J. May","year":"1998","unstructured":"May, L.J.: Major Causes of Software Project Failures. CrossTalk\u00a011(7), 9\u201312 (1998)","journal-title":"CrossTalk"},{"issue":"3","key":"9_CR17","doi-asserted-by":"publisher","first-page":"18","DOI":"10.1109\/52.765782","volume":"16","author":"J.S. Reel","year":"1999","unstructured":"Reel, J.S.: Critical Success Factors In Software Projects. IEEE Software\u00a016(3), 18\u201323 (1999)","journal-title":"IEEE Software"},{"issue":"2","key":"9_CR18","doi-asserted-by":"publisher","first-page":"12","DOI":"10.1109\/52.991324","volume":"19","author":"D. Reifer","year":"2002","unstructured":"Reifer, D.: Ten Deadly Risks in Internet and Intranet Software Development. IEEE Software\u00a019(2), 12\u201314 (2002)","journal-title":"IEEE Software"},{"key":"9_CR19","unstructured":"Wiegers, K.E.: Know Your Enemy: Software Risk Management (1998), (accessed, February 2005), http:\/\/www.processimpact.com\/articles\/risk_mgmt.pdf"},{"key":"9_CR20","volume-title":"The Mythical Man-Month: Essays on Software Engineering. 20th Anniversary Edition","author":"F.P. Brooks Jr.","year":"1995","unstructured":"Brooks Jr., F.P.: The Mythical Man-Month: Essays on Software Engineering. 20th Anniversary Edition. Addison-Wesley, Reading (1995)"},{"issue":"11","key":"9_CR21","doi-asserted-by":"publisher","first-page":"1268","DOI":"10.1145\/50087.50089","volume":"31","author":"B. Curtis","year":"1988","unstructured":"Curtis, B., Krasner, H., Iscoe, N.: A Field Study of the Software Design Process for Large Systems. Communications of the ACM\u00a031(11), 1268\u20131287 (1988)","journal-title":"Communications of the ACM"},{"key":"9_CR22","volume-title":"Rapid Development: Taming Wild Software Schedules","author":"S. McConnell","year":"1996","unstructured":"McConnell, S.: Rapid Development: Taming Wild Software Schedules. Microsoft Press, Redmond (1996)"},{"key":"9_CR23","volume-title":"Software Project Survival Guide","author":"S. McConnell","year":"1998","unstructured":"McConnell, S.: Software Project Survival Guide. Microsoft Press, Redmond (1998)"},{"key":"9_CR24","volume-title":"Software Project Management","author":"W. Royce","year":"1998","unstructured":"Royce, W.: Software Project Management. Addison-Wesley, Reading (1998)"},{"issue":"2","key":"9_CR25","doi-asserted-by":"publisher","first-page":"343","DOI":"10.2307\/258850","volume":"20","author":"S.L. Brown","year":"1995","unstructured":"Brown, S.L., Eisenhardt, K.M.: Product Development: Past Research, Present Findings, and Future Directions. Academy of Management Review\u00a020(2), 343\u2013378 (1995)","journal-title":"Academy of Management Review"},{"issue":"2","key":"9_CR26","doi-asserted-by":"publisher","first-page":"98","DOI":"10.1109\/32.841112","volume":"26","author":"J. Ropponen","year":"2000","unstructured":"Ropponen, J., Lyytinen, K.: Components of Software Development Risk: How to Address Them? A Project Manager Survey. IEEE Trans. Software Engineering\u00a026(2), 98\u2013111 (2000)","journal-title":"IEEE Trans. Software Engineering"},{"issue":"4","key":"9_CR27","doi-asserted-by":"crossref","first-page":"5","DOI":"10.1080\/07421222.2001.11045662","volume":"17","author":"R. Schmidt","year":"2001","unstructured":"Schmidt, R., Lyytinen, K., Keil, M., Cule, P.: Identifying Software Project Risks: An In-ternational Delphi Study. Journal of Management Information Systems\u00a017(4), 5\u201336 (Spring 2001)","journal-title":"Journal of Management Information Systems"},{"key":"9_CR28","doi-asserted-by":"crossref","unstructured":"Smith, J.M.: Troubled IT Projects \u2013 prevention and turnaround. IEE (2001)","DOI":"10.1049\/PBPC003E"},{"issue":"2","key":"9_CR29","doi-asserted-by":"publisher","first-page":"83","DOI":"10.1049\/em:20020205","volume":"12","author":"G. May","year":"2002","unstructured":"May, G., Ould, M.: Software project casualty. IEE Engineering Management Journal\u00a012(2), 83\u201390 (2002)","journal-title":"IEE Engineering Management Journal"},{"issue":"2","key":"9_CR30","doi-asserted-by":"publisher","first-page":"18","DOI":"10.1109\/MS.2003.1184161","volume":"20","author":"R.E. Fairley","year":"2003","unstructured":"Fairley, R.E., Willshire, M.J.: Why the Vasa Sank: 10 Problems and Some Antidotes for Software Projects. IEEE Software\u00a020(2), 18\u201325 (2003)","journal-title":"IEEE Software"},{"key":"9_CR31","doi-asserted-by":"crossref","unstructured":"Carr, M., Kondra, S., Monarch, I., Ulrich, F., Walker, C.: Taxonomy-Based Risk Identification (Technical Report CMU\/SEI-93-TR-6). SEI (1993)","DOI":"10.21236\/ADA266992"},{"key":"9_CR32","volume-title":"AntiPatterns in Project Management","author":"W.J. Brown","year":"2000","unstructured":"Brown, W.J., McCormick III, H.W., Thomas, S.W.: AntiPatterns in Project Management. John Wiley & Sons, New York (2000)"},{"key":"9_CR33","volume-title":"Managing Software Quality and Business Risk","author":"M.A. Ould","year":"1999","unstructured":"Ould, M.A.: Managing Software Quality and Business Risk. John Wiley & Sons, Chichester (1999)"},{"key":"9_CR34","unstructured":"Kuvaja, P., Maansaari, J., Sepp\u00e4nen, V., Taramaa, J.: Specific Requirements for Assessing Embedded Product Development. In: Proc. International Conference on Product Focused Software Process Improvement (PROFES), pp. 68\u201385 (1999)"},{"key":"9_CR35","doi-asserted-by":"publisher","first-page":"186","DOI":"10.1111\/1540-5885.1230186","volume":"12","author":"T.G. Rauscher","year":"1995","unstructured":"Rauscher, T.G., Smith, P.G.: Time-Driven Development of Software in Manufactured Goods. Journal of Product Innovation Management\u00a012, 186\u2013199 (1995)","journal-title":"Journal of Product Innovation Management"},{"key":"9_CR36","doi-asserted-by":"crossref","unstructured":"Ronkainen, J., Abrahamsson, P.: Software development under stringent hardware constraints: Do agile methods have a chance? In: Proc. 4th Int\u2019l. Conf. Extreme Programming and Agile Processes in Software Engineering, pp. 73\u201379 (2003)","DOI":"10.1007\/3-540-44870-5_10"},{"issue":"6","key":"9_CR37","doi-asserted-by":"publisher","first-page":"359","DOI":"10.1049\/ip-sen:20031173","volume":"150","author":"P. Kettunen","year":"2003","unstructured":"Kettunen, P.: Managing embedded software project team knowledge. IEE Proc. \u2013 Software\u00a0150(6), 359\u2013366 (2003)","journal-title":"IEE Proc. \u2013 Software"},{"key":"9_CR38","doi-asserted-by":"publisher","first-page":"301","DOI":"10.1016\/S0737-6782(01)00100-X","volume":"18","author":"R.F. Riek","year":"2001","unstructured":"Riek, R.F.: From experience: Capturing hardwon NPD lessons in checklists. Journal of Product Innovation Management\u00a018, 301\u2013313 (2001)","journal-title":"Journal of Product Innovation Management"},{"key":"9_CR39","volume-title":"Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency, and Quality","author":"S.C. Wheelwright","year":"1992","unstructured":"Wheelwright, S.C., Clark, K.B.: Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency, and Quality. The Free Press, New York (1992)"},{"key":"9_CR40","doi-asserted-by":"publisher","first-page":"124","DOI":"10.1016\/S0737-6782(97)00077-5","volume":"15","author":"X.M. Song","year":"1998","unstructured":"Song, X.M., Montoya-Weiss, M.M.: Critical Development Activities for Really New versus Incremental Products. Journal of Product Innovation Management\u00a015, 124\u2013135 (1998)","journal-title":"Journal of Product Innovation Management"},{"issue":"1","key":"9_CR41","doi-asserted-by":"publisher","first-page":"1","DOI":"10.1111\/1468-2370.00075","volume":"4","author":"H. Ernst","year":"2002","unstructured":"Ernst, H.: Success factors of new product development: a review of the empirical literature. International Journal of Management Reviews\u00a04(1), 1\u201340 (2002)","journal-title":"International Journal of Management Reviews"},{"issue":"6","key":"9_CR42","first-page":"43","volume":"47","author":"R.G. Cooper","year":"2004","unstructured":"Cooper, R.G., Edgett, S.J., Kleinschmidt, E.J.: Benchmarking Best NPD Practices \u2013 III. Research. Technology Management\u00a047(6), 43\u201355 (2004)","journal-title":"Technology Management"},{"issue":"6","key":"9_CR43","first-page":"13","volume":"11","author":"C. Jones","year":"1998","unstructured":"Jones, C.: Minimizing the Risks of Software Development. Cutter IT Journal\u00a011(6), 13\u201321 (1998)","journal-title":"Cutter IT Journal"},{"key":"9_CR44","volume-title":"Software Assessments, Benchmarks, and Best Practices","author":"C. Jones","year":"2000","unstructured":"Jones, C.: Software Assessments, Benchmarks, and Best Practices. Addison-Wesley, Reading (2000)"},{"key":"9_CR45","doi-asserted-by":"crossref","unstructured":"Rautiainen, K., Lassenius, C., Nihtil\u00e4, J., Sulonen, R.: Key Issues in New Product Development Controllability Improvement \u2013 Lessons Learned from European High-tech Industries. In: Proc. Portland Int\u2019l. Conf. Management of Engineering and Technology (PICMET) (1999)","DOI":"10.1109\/PICMET.1999.808091"},{"key":"9_CR46","volume-title":"Developing Products in Half the Time: New Rules, New Tools","author":"P.G. Smith","year":"1998","unstructured":"Smith, P.G., Reinertsen, D.G.: Developing Products in Half the Time: New Rules, New Tools. John Wiley & Sons, New York (1998)"},{"key":"9_CR47","volume-title":"Product Design and Development","author":"K.T. Ulrich","year":"2000","unstructured":"Ulrich, K.T., Eppinger, S.D.: Product Design and Development. McGraw-Hill, New York (2000)"},{"key":"9_CR48","volume-title":"Death March \u2013 The Complete Software Developer\u2019s Guide to Surviving \u201cMission Impossible\u201d Projects","author":"E. Yourdon","year":"1999","unstructured":"Yourdon, E.: Death March \u2013 The Complete Software Developer\u2019s Guide to Surviving \u201cMission Impossible\u201d Projects. Prentice-Hall, Upper Saddle River (1999)"},{"key":"9_CR49","doi-asserted-by":"publisher","first-page":"139","DOI":"10.1016\/S0263-7863(99)00074-5","volume":"19","author":"D. Baccarini","year":"2001","unstructured":"Baccarini, D., Archer, R.: The risk ranking of projects: a methodology. International Journal of Project Management\u00a019, 139\u2013145 (2001)","journal-title":"International Journal of Project Management"},{"issue":"4","key":"9_CR50","doi-asserted-by":"crossref","first-page":"47","DOI":"10.1080\/08956308.2004.11671641","volume":"47","author":"M.F. Holmes","year":"2004","unstructured":"Holmes, M.F., Campbell Jr., R.B.: Product Development Processes: Three Vectors of Improvement. Research \u2219 Technology Management\u00a047(4), 47\u201355 (2004)","journal-title":"Research \u2219 Technology Management"},{"issue":"11","key":"9_CR51","doi-asserted-by":"publisher","first-page":"76","DOI":"10.1145\/287831.287843","volume":"41","author":"M. Keil","year":"1998","unstructured":"Keil, M., Cule, P.E., Lyytinen, K., Schmidt, R.C.: A Framework for Identifying Software Project Risks. Communications of the ACM\u00a041(11), 76\u201383 (1998)","journal-title":"Communications of the ACM"},{"issue":"2","key":"9_CR52","doi-asserted-by":"crossref","first-page":"66","DOI":"10.1145\/383371.383376","volume":"30","author":"J. Iversen","year":"1999","unstructured":"Iversen, J., Nielsen, P.A., N\u00f8rbjerg, J.: Situated Assessment of Problems in Software Development. The DATA BASE for Advances in Information Systems\u00a030(2), 66\u201381 (Spring 1999)","journal-title":"The DATA BASE for Advances in Information Systems"},{"key":"9_CR53","unstructured":"Fitzgerald, D.: Principle-Centered Agile Project Portfolio Management. Agile Project Management Advisory Service Executive Report 6(5) (2005) (accessed, June 2005), http:\/\/www.cutter.com\/project\/fulltext\/reports\/2005\/05\/index.html"},{"key":"9_CR54","doi-asserted-by":"publisher","first-page":"495","DOI":"10.1007\/s10664-005-3864-z","volume":"10","author":"Y. Takagi","year":"2005","unstructured":"Takagi, Y., Mizuno, O., Kikuno, T.: An Empirical Approach to Characterizing Risky Software Projects Based on Logistic Regression Analysis. Empirical Software Engineering\u00a010, 495\u2013515 (2005)","journal-title":"Empirical Software Engineering"},{"key":"9_CR55","unstructured":"De Carlo, D.: Leading Extreme Projects to Success. Agile Project Management Advisory Service Executive Report 5(8) (2004) (accessed, June 2005), http:\/\/www.cutter.com\/project\/fulltext\/reports\/2004\/08\/index.html"},{"key":"9_CR56","doi-asserted-by":"crossref","unstructured":"Little, T., Greene, F., Phillips, T., Pilger, R., Poldervaart, R.: Adaptive Agility. In: Proc. Agile Development Conference (ADC), pp. 63\u201370 (2004)","DOI":"10.1109\/ADEVC.2004.2"},{"issue":"9","key":"9_CR57","doi-asserted-by":"crossref","first-page":"587","DOI":"10.1016\/j.infsof.2004.11.001","volume":"47","author":"P. Kettunen","year":"2005","unstructured":"Kettunen, P., Laanti, M.: How to steer an embedded software project: tactics for selecting the software process model. Information and Software Technology\u00a047(9), 587\u2013608 (2005)","journal-title":"Information and Software Technology"},{"key":"9_CR58","doi-asserted-by":"crossref","unstructured":"Kettunen, P., Laanti, M.: How to Steer an Embedded Software Project: Tactics for Selecting Agile Software Process Models. In: Proc. International Conference on Agility (ICAM), pp. 241\u2013257 (2005)","DOI":"10.1016\/j.infsof.2004.11.001"}],"container-title":["Lecture Notes in Computer Science","Product-Focused Software Process Improvement"],"original-title":[],"link":[{"URL":"http:\/\/link.springer.com\/content\/pdf\/10.1007\/11767718_9.pdf","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2020,11,17]],"date-time":"2020-11-17T20:06:41Z","timestamp":1605643601000},"score":1,"resource":{"primary":{"URL":"http:\/\/link.springer.com\/10.1007\/11767718_9"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2006]]},"ISBN":["9783540346821","9783540346838"],"references-count":58,"URL":"https:\/\/doi.org\/10.1007\/11767718_9","relation":{},"ISSN":["0302-9743","1611-3349"],"issn-type":[{"type":"print","value":"0302-9743"},{"type":"electronic","value":"1611-3349"}],"subject":[],"published":{"date-parts":[[2006]]}}}