How to steer an embedded software project: tactics for selecting the software process model |
| |
| Affiliation: | 1. Duke University School of Medicine, Durham, North Carolina;2. Department of Medicine, Duke University Medical Center, Durham, North Carolina;3. Duke Clinical Research Institute and the Department of Medicine, Duke University Medical Center, Durham, North Carolina;4. Department of Surgery, Duke University Medical Center, Durham, North Carolina;1. Department of Radiology, Henry Ford Health System, Detroit, Michigan;2. Department of Emergency Medicine, Henry Ford Health System, Detroit, Michigan;3. Department of Public Health Sciences, Henry Ford Health System, Detroit, Michigan;4. Department of Radiology, NYU Langone Medical Center, New York, New York;1. Tissue Mechanics Laboratory, Bioengineering Graduate Program, and Department of Aerospace and Mechanical Engineering, University of Notre Dame, 147 Multidisciplinary Research Building, Notre Dame, IN 46556, United States;2. Surgical Research Laboratory, Department of Clinical Sciences, Colorado State University, Ft. Collins, CO, United States;1. Department of Medical Oncology, Dana-Farber Cancer Institute, Boston, MA;2. Department of Biostatistics & Computational Biology, Dana-Farber Cancer Institute, Boston, MA;3. Clinical Operations and Program Management, Tokai Pharmaceuticals, Cambridge, MA;4. Department of Oncology, Barbara Ann Karmanos Cancer Institute, Detroit, MI;5. Division of Hematology/Oncology, Department of Medicine, Beth Israel Deaconess Medical Center, Boston, MA;6. Division of Medical Oncology, Department of Medicine, University of Washington, Seattle, WA |
| |
| Abstract: | Modern large new product developments (NPD) are typically characterized by many uncertainties and frequent changes. Often the embedded software development projects working on such products face many problems compared to traditional, placid project environments. One of the major project management decisions is then the selection of the project's software process model. An appropriate process model helps coping with the challenges, and prevents many potential project problems. On the other hand, an unsuitable process choice causes additional problems. This paper investigates the software process model selection in the context of large market-driven embedded software product development for new telecommunications equipment. Based on a quasi-formal comparison of publicly known software process models including modern agile methodologies, we propose a process model selection frame, which the project manager can use as a systematic guide for (re)choosing the project's process model. A novel feature of this comparative selection model is that we make the comparison against typical software project problem issues. Some real-life project case examples are examined against this model. The selection matrix expresses how different process models answer to different questions, and indeed there is not a single process model that would answer all the questions. On the contrary, some of the seeds to the project problems are in the process models themselves. However, being conscious of these problems and pitfalls when steering a project enables the project manager to master the situation. |
| |
| Keywords: | |
| 本文献已被 ScienceDirect 等数据库收录！ |
|
