Tipping point failure and robustness in single development projects

System Dynamics Review

Volumn 22, Issue 1, 2006, Pages 51-71

  Taylor, Tim ^a   Ford, David N ^a  

^a Department of Electrical and Computer Engineering   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

PRODUCT DEVELOPMENT; PROJECT MANAGEMENT;

EID: 33646499160     PISSN: 08837066     EISSN: 10991727     Source Type: Journal    
DOI: 10.1002/sdr.330     Document Type: Article

References (35)

1. Abdel-Hamid TK. 1984. The dynamics of software development project management: an integrative system dynamics perspective. Doctoral thesis, Massachusetts Institute of Technology, Cambridge, MA.
2. Baldwin C, Clark C. 2000. Design Rules: The Power of Modularity. MIT Press: Cambridge, MA.
3. Black L, Repenning N. 2001. Why firefighting is never enough: preserving high-quality product development. System Dynamics Review 17(1): 33-62.
4. Busby S, Hughes E. 2004. Projects, pathogens, and incubation periods. International Journal of Project Management 22(2): 425-434.
5. Cooper K. 1980. Naval ship production: a claim settled and a framework built. Interfaces 10(6): 20-36.
6. Cooper K. 1993a. The rework cycle: why projects are mismanaged. PM Network February: 5-7.
7. Cooper K. 1993b. The rework cycle: how it really works...and reworks. PM Network February: 25-28.
8. Cooper K. 1993c. The rework cycle: benchmarks for the project managers. Project Management Journal 14(1): 17-21.
9. Cooper K. 1994. The $2,000 hour: how managers influence project performance through the rework cycle. Project Management Journal 15(1): 11-24.
10. Cooper K, Lyneis J, Bryant B. 2002. Learning to learn, from past to future. International Journal of Project Management 20(3): 213-219.
11. Evans M. 2005. Overdue and over budget, over and over again; project management. The Economist 375(8430): 66.
12. Ford D. 1995. The dynamics of project management: an investigation of the impacts of project process and coordination on performance. Doctoral thesis, Massachusetts Institute of Technology, Cambridge, MA.
13. Ford D. 1999. A behavioral approach to feedback loop dominance analysis. System Dynamics Review 15(1): 3-36.
14. Ford D, Sterman J. 1998. Modeling dynamic development processes. System Dynamics Review 14(1): 31-68.
15. Ford D, Sterman J. 2003a. The liar's club: impacts of concealment in concurrent development projects. Concurrent Engineering Research and Applications 111(3): 211-219.
16. Ford D, Sterman J. 2003b. Overcoming the 90% syndrome: iteration management in concurrent development projects. Concurrent Engineering Research and Applications 111(3): 177-186.
17. Gladwell M. 2000. The Tipping Point: How Little Things Make a Big Difference. Little, Brown: Boston, MA.
18. Graham A. 2000. Beyond PM 101: lessons for managing large development programs. Project Management Journal 31(4): 7-18.
19. Kharbanda O, Pinto J. 1996. What Made Gertie Gallop: Learning from Project Failures. Van Nostrand Reinhold: New York.
20. Luo L, Kannan P, Besharati B, Azram S. 2005. Design of robust new products under variability: marketing meets design. Journal of Product Innovation Management 22(2005): 177-192.
21. Lyneis F, Cooper K, Els S. 2001. Strategic management of complex projects: a case study using system dynamics. System Dynamics Review 17(3): 237-260.
22. Matta F, Ashkenas R. 2003. Why good projects fail anyway. Harvard Business Review September: 109-114.
23. NRC (Nuclear Regulatory Commission). 1973-1982. Nuclear Power Plant Construction Status Reports (report periods from 1973-1982). NUREG-0030.
24. Paul L. 2005. It's your move. PM Network 19(4): 34-38.
25. Rahamandad H. 2005. Dynamics of platform-based product development. In Proceedings of the 2004 International System Dynamics Conference, Boston, MA, 17-21 July.
26. Repenning N. 2001. Understanding fire fighting in new product development. Journal of Product Innovation Management 18: 265-300.
27. Rodrigues A, Williams TM. 1997. System dynamics in project management: assessing the impacts of client behavior on project performance. Journal of the Operational Research Society 49: 2-15.
28. Sterman J. 2000. Business Dynamics: Systems Thinking and Modeling for a Complex World. Irwin McGraw-Hill: New York.
29. Swan K, Kotabe M, Allred B. 2005. Exploring robust design capabilities, their role in creating global products, and their relationship to firm performance. The Journal of Product Innovation Management 22: 144-164.
30. Taguchi G, Chowdhury S, Taguchi S. 2000. Robust Engineering. McGraw-Hill: New York.
31. Taylor T, Ford D, Johnson S. 2005. When good projects go bad, tipping point dynamics in development projects. In 2005 International System Dynamics Conference, Boston, MA, 17-21 July.
32. Thomas HR, Napolitan CL. 1994. The Effects of Changes on Labor Productivity: Why and How Much. SD No. 99. Construction Industry Institute: Austin, TX.
33. USGAO (United States General Accounting Office). 1996. Department of Energy: Opportunity to improve management of major systems acquisitions. GAO/RCED-97-17. Washington, DC.
34. USGAO (United States General Accounting Office). 1997. Department of Energy: Improving Management of Major Systems Acquisitions. GAO/ T-RCED-97-92. Washington, DC.
35. Wells W. 1999. From the editor. Project Management Journal 30(2): 4-5.