QPLAN: Decision support for evaluating planning quality in software development projects

Decision Support Systems

Volumn 96, Issue , 2017, Pages 92-102

  Féris, Marco Antônio Amaral ^a   Zwikael, Ofer ^b   Gregor, Shirley ^b  

^a CRANFIELD UNIVERSITY   (United Kingdom)

^b AUSTRALIAN NATIONAL UNIVERSITY   (Australia)

Author keywords

Decision support tool; Dual process theory; Planning quality; Planning performance theory; Software projects

Indexed keywords

DECISION THEORY; SOFTWARE DESIGN;

BUSINESS ENVIRONMENTS; DECISION SUPPORT TOOLS; DECISION SUPPORTS; DUAL-PROCESS THEORIES; PROJECT PLANNING; PSYCHOLOGICAL BIAS; SOFTWARE DEVELOPMENT PROJECTS; SOFTWARE PROJECT;

DECISION SUPPORT SYSTEMS;

EID: 85014090145     PISSN: 01679236     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.dss.2017.02.008     Document Type: Article

References (77)

1. [1] Abran, A., Bourque, P., Dupuis, R., Moore, J., Guide to the Software Engineering Body of Knowledge - SWEBOK. 2004, 1–202, 10.1109/SESS.1999.767664.
2. [2] van Aken, J.E., Design science and organization development interventions. J. Appl. Behav. Sci. 43:1 (2007), 67–88, 10.1177/0021886306297761.
3. [3] van Aken, J.E., Management research on the basis of the design paradigm: the quest for field-tested and grounded technological rules. J. Manag. Stud. 41:2 (2004), 219–246, 10.1111/j.1467-6486.2004.00430.x.
4. [4] Alblas, A.A., Wortmann, J.C., Managing large engineering changes. Int. J. Oper. Prod. Manag. 32:11 (2012), 1252–1280, 10.1108/01443571211274549.
5. [5] Armstrong, J.S., The value of formal planning for strategic decisions: review of empirical research. Strateg. Manag. J. 3:3 (1982), 197–211, 10.1002/smj.4250030303.
6. [6] Arnott, D., Pervan, G., A critical analysis of decision support systems research revisited: the rise of design science. J. Inf. Technol. 29:4 (2014), 269–293, 10.1057/jit.2014.16.
7. [7] Arnott, D., Pervan, G., Eight key issues for the decision support systems discipline. Decis. Support. Syst. 44:3 (2008), 657–672, 10.1016/j.dss.2007.09.003.
8. [8] Amaral Féris, M.A., QPLAN: A Tool for Enhancing Software Development Project Performance with Customer Involvement. Handbook of Research on Strategic Alliances and Value Co-Creation in the Service Industry, 2017, IGI Global, Hershey, PA, 259–283, 10.4018/978-1-5225-2084-9.ch013.
9. [9] Bannerman, P.L., Risk and risk management in software projects: a reassessment. J. Syst. Softw. 81:12 (2008), 2118–2133, 10.1016/j.jss.2008.03.059.
10. [10] Barbour, R.S., Checklists for improving rigour in qualitative research: a case of the tail wagging the dog?. Br. Med. J. 322 (2001), 1115–1117, 10.1136/bmj.322.7294.1115.
11. [11] Barry, L., Uys, M.-L., An investigation into the status of project management in South Africa. S. Afr. J. Ind. Eng. 22:1 (2011), 29–44, 10.7166/22-1-31.
12. [12] Baskerville, R., What design science is not. Eur. J. Inf. Syst. 17:5 (2008), 441–443, 10.1057/ejis.2008.45.
13. [13] Breyfogle, F.W., Implementing Six Sigma: Smarter Solutions Using Statistical Methods. second ed., 2003, John Wiley & Sons, Inc., Hoboken, NJ, 10.2307/1271088.
14. [14] Conforto, D.C., Amaral, E.C., Evaluating an agile method for planning and controlling innovative projects. Proj. Manag. J. 41:2 (2010), 73–80, 10.1002/pmj.20089.
15. [15] Daskalantonakis, M.K., A practical view of software measurement and implementation experiences within Motorola. IEEE Trans. Softw. Eng. 18:11 (1992), 998–1010, 10.1109/32.177369.
16. [16] Flynn, D.J., Arce, E.A., A CASE tool to support critical success factors analysis in IT planning and requirements determination. Inf. Softw. Technol. 39:5 (1997), 311–321, 10.1016/S0950-5849(96)01150-0.
17. [17] Flyvbjerg, B., Skamris Holm, M.K., Buhl, S.L., How (in)accurate are demand forecasts in public works projects? The case of transportation. J. Am. Plan. Assoc. 71:2 (2005), 131–146, 10.1080/01944360508976688.
18. [18] Flyvbjerg, B., Quality control and due diligence in project management: getting decisions right by taking the outside view. Int. J. Proj. Manag. 31:5 (2013), 760–774.
19. [19] Fortune, J., White, D., Framing of project critical success factors by a systems model. Int. J. Proj. Manag. 24:1 (2006), 53–65, 10.1016/j.ijproman.2005.07.004.
20. [20] Gartner says worldwide IT spending forecast to grow 2.7 percent in 2017. http://www.gartner.com/newsroom/id/3568917.
21. [21] Gopal, A., Krishnan, M.S., Mukhopadhyay, T., Goldenson, D.R., Measurement programs in software development: determinants of success. IEEE Trans. Eng. Manag. 28:9 (2002), 863–875, 10.1109/TSE.2002.1033226.
22. [22] Staff, I.B.M., IBM Rational Unified Process: Best Practices for Software Development Teams. http://www.ibm.com/developerworks/rational/library/253.html, 2003.
23. [23] Gregor, S., Hevner, A.R., Positioning and presenting design science research for maximum impact. MIS Q. 37:2 (2013), 337–355, 10.2753/MIS0742-1222240302.
24. [24] Hevner, A.R., March, S.T., Park, J., Ram, S., Design science in information systems. MIS Q. 28:1 (2004), 75–105.
25. [25] Houston, D., The value of a good checklist, software quality professional., 6(2), 2004, 17–26, 10.1109/MC.2010.181.
26. [26] International Organization for Standardization, ISO/IEC 15939, 2007 - Systems and software engineering - measurement process. http://www.iso.org/iso/catalogue_detail.htm?csnumber=44344, 2007.
27. [27] International Organization for Standardization, ISO/IEC FCD 25040, Software engineering - software product quality requirements and evaluation (SQuaRE) - data quality model. http://www.iso.org/iso/catalogue_detail.htm?csnumber=35736, 2009.
28. [28] Jørgensen, M., Gruschke, T.M., The impact of lessons-learned sessions on effort estimation and uncertainty assessments. IEEE Trans. Softw. Eng. 35:3 (2009), 368–383.
29. [29] Jørgensen, M., Top-down and bottom-up expert estimation of software development effort. Inf. Softw. Technol. 46:1 (2004), 3–16, 10.1016/S0950-5849(03)00093-4.
30. [30] Kahneman, D., Thinking, Fast and Slow. first ed., 2011, Farrar, Straus and Giroux, New York.
31. [31] Kahneman, D., Knetsch, J.L., Thaler, R.H., The endowment effect, loss aversion, and status quo bias: anomalies. J. Econ. Perspect. 5:1 (1991), 193–206, 10.1257/jep.5.1.193.
32. [32] Karnaugh, M., The map method for synthesis of combinational logic circuits. Transactions of the American institute of electrical engineers, part I: communication and electronics., 72(5), 1953, 593–599, 10.1109/TCE.1953.6371932.
33. [33] Keil, M., Li, L., Mathiassen, L., Zheng, G., The influence of checklists and roles on software practitioner risk perception and decision-making. J. Syst. Softw. 81:6 (2008), 908–919, 10.1016/j.jss.2007.07.035.
34. [34] Krishnan, M., Kriebel, C., An empirical analysis of productivity and quality in software products. Manag. Sci. 46:6 (2000), 745–759, 10.1016/S0267-3649(00)88914-1.
35. [35] Lechler, T., Dvir, D., An alternative taxonomy of project management structures: linking project management structures and project success. IEEE Trans. Softw. Eng. 57:2 (2010), 198–210, 10.1109/TEM.2010.2044441.
36. [36] Lin, C., Pervan, G., The practice of IS/IT benefits management in large Australian organizations. Inf. Manag. 41:1 (2003), 13–24, 10.1016/S0378-7206(03)00002-8.
37. [37] Ling, F.Y.Y., Low, S.P., Wang, S.Q., Lim, H.H., Key project management practices affecting Singaporean firms’ project performance in China. Int. J. Proj. Manag. 27:1 (2009), 59–71, 10.1016/j.ijproman.2007.10.004.
38. [38] Loh, T.C., Koh, S.C.L., Critical elements for a successful enterprise resource planning implementation in small- and medium-sized enterprises. Int. J. Prod. Res. 42:17 (2004), 3433–3455, 10.1080/00207540410001671679.
39. [39] Lutz, M.H., Laplante, P.A., C# and the NET framework: ready for real time?. IEEE Softw. 20:1 (2003), 74–80, 10.1109/MS.2003.1159034.
40. [40] Mahanti, R., Jiju, A., Six sigma in the Indian software industry: some observations and results from a pilot survey. TQM J. 21:6 (2009), 549–564, 10.1108/17542730910995837.
41. [41] March, S., Smith, G., Design and natural science research on information technology. Decis. Support Syst. 15:4 (1995), 251–266, 10.1016/0167-9236(94)00041-2.
42. [42] Masters, B., Frazier, G.V., Project quality activities and goal setting in project performance assessment. Qual. Manag. J. 14:3 (2007), 25–35.
43. [43] Mihm, J., Incentives in new product development projects and the role of target costing. Manag. Sci. 56:8 (2010), 1324–1344, 10.1287/mnsc.1100.1175.
44. [44] Milkman, K.L., Chugh, D., Bazerman, M.H., How can decision making be improved?. Perspect. Psychol. Sci. 4:4 (2009), 379–383, 10.1111/j.1745-6924.2009.01142.x.
45. [45] Mintzberg, H., Raisinghani, D., Théorêt, A., The structure of “unstructured” decision processes. Adm. Sci. Q. 21:2 (1976), 246–275, 10.2307/2392045.
46. [46] Napier, N.P., Keil, M., Tan, F.B., IT project managers’ construction of successful project management practice: a repertory grid investigation. Inf. Syst. J. 19:3 (2009), 255–282, 10.1111/j.1365-2575.2007.00264.x.
47. [47] Norris, G.D., Post-investment appraisal. Willcocks, L., (eds.) Investing in Information Systems: Evaluation and Management, 1996, Chapman & Hall, London, 193–223.
48. [48] Papke-Shields, K.E., Beise, C., Quan, J., Do project managers practice what they preach, and does it matter to project success?. Int. J. Proj. Manag. 28:7 (2010), 650–662, 10.1016/j.ijproman.2009.11.002.
49. [49] Peffers, K., Tuunamen, T., Rotenberger, M.A., Chatterjee, S., A design science research methodology for information systems research. J. Manag. Inf. Syst. 24:3 (2007), 45–77, 10.2753/MIS0742-1222240302.
50. [50] Project Management Body of Knowledge (PMBOK ®), Guide - Fifth Edition. 2013, Project Management Institute, Newtown Square, PA.
51. [51] Raghunathan, S., Impact of information quality and decision-maker quality on decision quality: a theoretical model and simulation analysis. Decis. Support. Syst. 26:4 (1999), 275–286, 10.1016/S0167-9236(99)00060-3.
52. [52] Rees-Caldwell, K., Pinnington, A.H., National culture differences in project management: comparing British and Arab project managers’ perceptions of different planning areas. Int. J. Proj. Manag. 31:2 (2013), 212–227, 10.1016/j.ijproman.2012.04.003.
53. [53] Rezaei, A.R., Çelik, T., Baalousha, Y., Performance measurement in a quality management system, transaction E. Ind. Eng. 18:3 (2011), 742–752, 10.1016/j.scient.2011.05.021.
54. [54] Rodriguez-Repiso, L., Setchi, R., Salmeron, J.L., Modelling IT projects success with fuzzy cognitive maps. Expert Syst. Appl. 32:2 (2007), 543–559, 10.1016/j.eswa.2006.01.032.
55. [55] Rossman, S.F., Rallis, G.B., Learning in the Field: An Introduction to Qualitative Research. second ed., 2003, Sage Publications, Thousand Oaks, CA.
56. [56] Sedoglavich, V., Absorptive Capacity and Internalization of New Zealand High-Tech SMEs in the Agro-Technology Sector (Thesis, Doctor of Philosophy (PhD)). 2008, The University of Waikato http://researchcommons.waikato.ac.nz/handle/10289/2606.
57. [57] Salas, E., Rosen, M.A., Expertise-based intuition and decision making in organizations. J. Manag. 36:4 (2010), 941–973, 10.1177/0149206309350084.
58. [58] Serrador, P., Pinto, J.K., Does agile work? — a quantitative analysis of agile project success. Int. J. Proj. Manag. 33:5 (2015), 1040–1051, 10.1016/j.ijproman.2015.01.006.
59. [59] Shenhar, A., Dvir, D., Reinventing Project Management: The Diamond Approach to Successful Growth and Innovation. 2007, Harvard Business School Press, Boston, MA.
60. [60] Shepperd, M., Cartwright, M., Predicting with sparse data. IEEE Trans. Softw. Eng. 27:11 (2001), 987–998, 10.1109/32.965339.
61. [61] Shmueli, O., Pliskin, N., Fink, L., Can the outside-view approach improve planning decisions in software development projects?. Inf. Syst. J. 26:4 (2016), 395–418, 10.1111/isj.12091.
62. [62] Shmueli, O., Pliskin, N., Fink, L., Explaining over-requirement in software development projects: an experimental investigation of behavioral effects. Int. J. Proj. Manag. 33:2 (2015), 380–394, 10.1016/j.ijproman.2014.07.003.
63. [63] Software Engineering Institute, CMMI® for Development, Version 1.3. http://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9661, 2010.
64. [64] Stach, W., Kurgan, L., Pedrycz, W., Reformat, M., Genetic learning of fuzzy cognitive maps. Fuzzy Sets Syst. 153:3 (2005), 371–401, 10.1016/j.fss.2005.01.009.
65. [65] Standish Group, Chaos manifesto, Think Big, Act Small, (2013). 2013, 1–52 https://www.versionone.com/assets/img/files/CHAOSManifesto2013.pdf.
66. [66] Stojanov, Z., Dobrilovic, D., Stojanov, J., Analyzing trends for maintenance request process assessment: empirical investigation in a very small software company, theory and applications of mathematics & computer science., 3(2), 2013, 59–74.
67. [67] Sudhakar, G.P., A model of critical success factors for software projects. J. Enterp. Inf. Manag. 25:6 (2012), 537–558, 10.1108/17410391211272829.
68. [68] Symons, C., Metrics software industry performance. IEEE Softw. 27:6 (2010), 66–72, 10.1109/MS.2009.162.
69. [69] Tesch, D., Kloppenborg, T.J., Frolick, M.N., IT project risk factors: the project management professional's perspective. J. Comput. Inf. Syst. 47:4 (2007), 61–69.
70. [70] Weick, M., Guinote, A., How long will it take? Power biases time predictions. J. Exp. Soc. Psychol. 46:4 (2010), 595–604, 10.1016/j.jesp.2010.03.005.
71. [71] White, D., Fortune, J., Current practice in project management — an empirical study. Int. J. Proj. Manag. 20:1 (2002), 1–11, 10.1016/S0263-7863(00)00029-6.
72. [72] Zwikael, O., Sadeh, A., Planning effort as an effective risk management tool. J. Oper. Manag. 25:4 (2007), 755–767, 10.1016/j.jom.2006.12.001.
73. [73] Zwikael, O., Critical planning processes in construction projects. Constr. Innov. 9:4 (2009), 372–387, 10.1108/14714170910995921.
74. [74] Zwikael, O., Ahn, M., The effectiveness of risk management: an analysis of project risk planning across industries and countries. Risk Anal. Int. J. 31:1 (2011), 25–37.
75. [75] Zwikael, O., Globerson, S., Evaluating the quality of project planning: a model and field results. Int. J. Prod. Res. 42:8 (2004), 1545–1556, 10.1080/00207540310001639955.
76. [76] Zwikael, O., Globerson, S., From critical success factors to critical success processes. Int. J. Prod. Res. 44:17 (2006), 3433–3449, 10.1080/00207540500536921.
77. [77] Zwikael, O., Top management involvement in project management: exclusive support practices for different project scenarios. Int. J. Manag. Proj. Bus. 1:3 (2008), 387–403, 10.1108/17538370810883837.