PL EN


Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników
Tytuł artykułu

The Role of Organisational Phenomena in Software Cost Estimation: A Case Study of Supporting and Hindering Factors

Treść / Zawartość
Identyfikatory
Warianty tytułu
Języki publikacji
EN
Abstrakty
EN
Despite the fact that many researchers and practitioners agree that organisational issues are equally important as technical issues from the software cost estimation (SCE) success point of view, most of the research focus has been put on the development of methods, whereas organisational factors have received surprisingly little academic scrutiny. This study aims to identify organisational factors that either support or hinder meaningful SCE, identifying their impact on estimation success. Top management’s role is specifically addressed. The study takes a qualitative and explorative case study based approach. In total, 18 semi-structured interviews aided the study of three projects in three organisations. Hence, the transferability of the results is limited. The results suggest that the role of the top management is important in creating prerequisites for meaningful estimation, but their day-to-day participation is not required for successful estimation. Top management may also induce undesired distortion in estimation. Estimation maturity and estimation success seem to have an interrelationship with software process maturity, but there seem to be no significant individual organisational factors, which alone would make estimation successful. Our results validate several distortions and biases reported in the previous studies, and show the SCE research focus has remained on methodologies and technical issues.
Rocznik
Strony
167--198
Opis fizyczny
Bibliogr. 90 poz., tab.
Twórcy
autor
  • Vaadin Ltd
  • Pervasive Computing, Tampere University of Technology
autor
  • Department of Future Technologies, University of Turku
autor
  • Department of Information Technologies, Åbo Akademi University
Bibliografia
  • [1] Y.K. Dwivedi, D. Wastell, S. Laumer, H.Z. Henriksen, M.D. Myers, D. Bunker, A. Elbanna, M.N. Ravishankar, and S.C. Srivastava, “Research on information systems failures and successes: Status update and future directions,” Information Systems Frontiers, Vol. 17, No. 1, 2014, pp. 143–157.
  • [2] D.L. Hughes, Y.K. Dwivedi, A.C. Simintiras, and N.P. Rana, Success and Failure of IS/IT Projects. Springer International Publishing, 2016.
  • [3] T. Halkjelsvik and M. Jørgensen, “From origami to software development: A review of studies on judgment-based predictions of performance time.” Psychological Bulletin, Vol. 138, No. 2, 2012, pp. 238–271.
  • [4] The Standish Group International, “The CHAOS manifesto: Think big and act small,” 2013.
  • [5] D. Galorath, Software project failure costs billions. Better estimation & planning can help, (2012). [Online]. http://galorath.com/blog/softwareproject- failure-costs-billions-better-estimationplanning- can-help/ [Accessed 16 September 2014].
  • [6] J. McManus and T. Wood-Harper, A study in project failure, (2008). [Online]. http: //www.bcs.org/content/ConWebDoc/19584 [Retrieved 19/4/2012].
  • [7] R.R. Nelson, “IT project management: Infamous failures, classic mistakes,and best prac tices,” MIS Quarterly Executive, Vol. 6, No. 2, 2007, pp. 67–78.
  • [8] M. Jørgensen, “Communication of software cost estimates,” in Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering – EASE’14. ACM Press, 2014, p. 28.
  • [9] A. Magazinius, S. Börjesson, and R. Feldt, “Investigating intentional distortions in software cost estimation – An exploratory study,” Journal of Systems and Software, Vol. 85, No. 8, 2012, pp. 1770–1781.
  • [10] A. Magazinovic and J. Pernstål, “Any other cost estimation inhibitors?” in Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement – ESEM’08. ACM Press, 2008, pp. 233–242.
  • [11] J. Rahikkala, V. Leppänen, J. Ruohonen, and J. Holvitie, “Top management support in software cost estimation,” International Journal of Managing Projects in Business, Vol. 8, No. 3, 2015, pp. 513–532.
  • [12] J.J. Ahonen, P. Savolainen, H. Merikoski, and J. Nevalainen, “Reported project management effort, project size, and contract type,” Journal of Systems and Software, Vol. 109, 2015, pp. 205–213.
  • [13] S. McConnell, Software Estimation: Demystifying the Black Art. Microsoft Press, 2006.
  • [14] M. Jorgensen and M. Shepperd, “A systematic review of software development cost estimation studies,” IEEE Transactions on Software Engineering, Vol. 33, No. 1, 2007, pp. 33–53.
  • [15] B. Pitterman, “Telcordia technologies: The journey to high maturity,” IEEE Software, Vol. 17, No. 4, 2000, pp. 89–96.
  • [16] L. Putnam and W. Myers, Five core metrics: The Intelligence Behind Successful Software Management. Dorset House Publishing, 2003.
  • [17] J. Rahikkala, S. Hyrynsalmi, and V. Leppänen, “Accounting testing in software cost estimation: A case study of the current practice and impacts,” in Proceedings of 14th Symposium on Programming Languages and Software Tools, J. Nummenmaa, O. Sievi-Korte, and E. Mäkinen, Eds. University of Tampere, 2015, pp. 64–75.
  • [18] D. White and J. Fortune, “Current practice in project management – An empirical study,” International Journal of Project Management, Vol. 20, No. 1, 2002, pp. 1–11. [19] A Guide to the Project Management Body of Knowledge: PMBOK Guide, Std. ANSI/PMI 99-001-2013, 2013.
  • [20] N. Cerpa and J.M. Verner, “Why did your project fail?” Communications of the ACM, Vol. 52, No. 12, 2009, p. 130.
  • [21] L. McLeod and S.G. MacDonell, “Factors that affect software systems development project outcomes,” ACM Computing Surveys, Vol. 43, No. 4, 2011, pp. 1–56.
  • [22] H.N.N. Mohd and S. Shamsul, “Critical success factors for software projects: A comparative study,” Scientific Research and Essays, Vol. 6, No. 10, 2011, pp. 2174–2186.
  • [23] CMMI Product Team, “CMMI for development. version 1.3,” Software Engineering Institute, Carnegie Mellon University, Tech. Rep. CMU/SEI-2010-TR-0336, 2010.
  • [24] G. Caupin, H. Knoepfel, G. Koch, K. Pannenbäcker, F. Pérez-Polo, and C. Seabury, Eds., IPMA Competence Baseline Version 3. International Project Management Association, 2006. [Online]. http://www.ipma.world/assets/ ICB3.pdf
  • [25] O. Zwikael, “Top management involvement in project management,” International Journal of Managing Projects in Business, Vol. 1, No. 4, 2008, pp. 498–511.
  • [26] T. Cooke-Davies, “The ‘real’ success factors on projects,” International Journal of Project Management, Vol. 20, No. 3, 2002, pp. 185–190.
  • [27] M. Lycett, A. Rassau, and J. Danson, “Programme management: A critical review,” International Journal of Project Management, Vol. 22, No. 4, 2004, pp. 289–299.
  • [28] P. Dietrich and P. Lehtonen, “Successful management of strategic intentions through multiple projects – reflections from empirical study,” International Journal of Project Management, Vol. 23, No. 5, 2005, pp. 386–391.
  • [29] S. Srivannaboon and D.Z. Milosevic, “A two-way influence between business strategy and project management,” International Journal of Project Management, Vol. 24, No. 6, 2006, pp. 493–505.
  • [30] B.J. Kolltveit, J.T. Karlsen, and K. Grønhaug, “Perspectives on project management,” International Journal of Project Management, Vol. 25, No. 1, 2007, pp. 3–9.
  • [31] H.K. Doloi, “Understanding stakeholders’ perspective of cost estimation in project management,” International Journal of Project Management, Vol. 29, No. 5, 2011, pp. 622–636.
  • [32] B. Nanus and L. Farr, “Some cost contributors to large-scale programs,” in Proceedings of the April 21-23, 1964, spring joint computer conference on XX – AFIPS ’64 (Spring). ACM Press, 1964, pp. 239–248.
  • [33] E.A. Nelson, “Management handbook for the estimation of computer programming costs,” Defense Technical Information Center, Technical Documentary Report ESD-TR-67-66, 1967. [Online]. http://www.dtic.mil/dtic/tr/fulltext/ u2/648750.pdf
  • [34] L.C. Briand and I. Wieczorek, in Encyclopedia of Software Engineering. John Wiley & Sons, Inc., 2002.
  • [35] S.K. Sehra, Y.S. Brar, N. Kaur, and S.S. Sehra, “Research patterns and trends in software effort estimation,” Information and Software Technology, Vol. 91, 2017, pp. 1–21.
  • [36] J. Hihn and H. Habib-agahi, “Cost estimation of software intensive projects: A survey of current practices,” in Proceedings of the 13th International Conference on Software Engineering. IEEE Comput. Soc. Press, 1991, pp. 276–287.
  • [37] R. Turner, The handbook of project based management, 2nd ed. McGraw-Hill, 1999.
  • [38] D.I. Cleland, “The strategic context of projects,” in Project portfolio management – selecting and prioritizing projects for competitive advantage, L. Dye and J. Pennypacker, Eds. Center for Business Practices, 1999.
  • [39] L.F. Luna-Reyes, J. Zhang, J. Ramón Gil-García, and A.M. Cresswell, “Information systems development as emergent socio-technical change: A practice approach,” European Journal of Information Systems, Vol. 14, No. 1, 2005, pp. 93–105.
  • [40] J. Fortune and D. White, “Framing of project critical success factors by a systems model,” International Journal of Project Management, Vol. 24, No. 1, 2006, pp. 53–65.
  • [41] T. Okoro, “Diverse talent: Enhancing gender participation in project management,” Procedia – Social and Behavioral Sciences, Vol. 226, 2016, pp. 170–175, proceedings of the 29th IPMA World Congress WC2015 (28-30 September – 1 October, Panama).
  • [42] R. Young and E. Jordan, “Top management support: Mantra or necessity?” International Journal of Project Management, Vol. 26, No. 7, 2008, pp. 713–725.
  • [43] R. Schmidt, K. Lyytinen, M. Keil, and P. Cule, “Identifying software project risks: An international Delphi study,” Journal of Management Information Systems, Vol. 17, No. 4, 2001, pp. 5–36.
  • [44] M.L. Markus, “Implementation politics: Top management support and user involvement,” MIT, Center for Information Systems Research, Alfred P. Sloan School of Management, Tech. Rep. CISR 75, 1981. [Online]. https://dspace.mit.edu/bitstream/handle/ 1721.1/48186/implementationpo00mark.pdf [45] Y.H. Kwak and F.T. Anbari, “Analyzing project management research: Perspectives from top management journals,” International Journal of Project Management, Vol. 27, No. 5, 2009, pp. 435–446.
  • [46] J. Thomas, C. Delisle, K. Jugdev, and P. Buckle, “Selling project management to senior executives: The case for avoiding crisis sales?” Project Management Journal, Vol. 33, No. 2, 2002, pp. 19–28.
  • [47] L. Crawford, “Senior management perceptions of project management competence,” International Journal of Project Management, Vol. 23, No. 1, 2005, pp. 7–16.
  • [48] J.T. Garrity, “Top management and computer profits,” Harvard Business Review, Vol. 41, No. 4, 1963, pp. 6–12. [49] C.M. Beath, “Supporting the information technology champion,” MIS Quarterly, Vol. 15, No. 3, 1991, p. 355.
  • [50] G. H A Morton, “Become a project champion,” International Journal of Project Management, Vol. 1, No. 4, 1983, pp. 197–203. [51] Software Extension to the PMBOK Guide, 5th ed. Project Management Institute, Inc & IEEE Computer Society, 2013.
  • [52] S. Adams, ITIL V3 foundation handbook. The Stationery Office, 2009, Vol. 1.
  • [53] Guidance on Project Management, Std. 2150:2012, 2012.
  • [54] M. Cohn, Agile Estimating and Planning, ser. Robert C. Martin Series. Pearson Education, Inc., 2005.
  • [55] M. Petrini and M. Pozzebon, “Managing sustainability with the support of business intelligence: Integrating socio-environmental indicators and organisational context,” The Journal of Strategic Information Systems, Vol. 18, No. 4, 2009, pp. 178–191.
  • [56] A. Magazinius and R. Feldt, in Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering – CHASE’10. ACM Press, 2010, pp. 92–95.
  • [57] J. Smyrk, “Why most IT projects are really IT without the project,” in Third world project management conference, Gold Coast, Australia, 2002.
  • [58] R. Young and E. Jordan, “Lifting the game: Board views on e-commerce risk,” in The Adoption and Diffusion of IT in an Environment of Critical Change, D. Bunker, D. Wilson, and S. Elliot, Eds., 2002, pp. 102–113.
  • [59] R.K. Yin, Case Study Research: Design and Methods, 3rd ed. SAGE Publications, Inc., 2003. [60] C. Robson, Real World Research: A Resource for Social Scientists and Practitioner-researchers, 2nd ed. Blackwell Publishing, 2002. [61] M. Patton, Qualitative Research and Evaluation Method, 3rd ed. SAGE Publications, Inc., 2001.
  • [62] M.C. Paulk, B. Curtis, M.B. Chrissis, and C.V. Weber, “Capability maturity model for software,” Software Engineering Institute, Carnegie Mellon University, Tech. Rep. ESC-TR-93-177, 1993. [Online]. https://www.sei.cmu.edu/reports/93tr024.pdf
  • [63] A.L. Lederer and J. Prasad, “Nine management guidelines for better cost estimating,” Communications of the ACM, Vol. 35, No. 2, 1992, pp. 51–59.
  • [64] T. Little, “Schedule estimation and uncertainty surrounding the cone of uncertainty,” IEEE Software, Vol. 23, No. 3, 2006, pp. 48–54.
  • [65] B.W. Boehm, R. Madachy, B. Steece et al., Software cost estimation with Cocomo II. Prentice Hall PTR, 2000.
  • [66] M. Jørgensen and D.I. Sjøberg, “The impact of customer expectation on software development effort estimates,” International Journal of Project Management, Vol. 22, No. 4, 2004, pp. 317–325.
  • [67] J. Aranda and S. Easterbrook, “Anchoring and adjustment in software estimation,” in Proceedings of the 10th European Software Engineering Conference Held Jointly with 13th ACM SIGSOFT International Symposium on Foundations of Software Engineering. ACM Press, 2005, pp. 346–355.
  • [68] D. Milosevic and P. Patanakul, “Standardized project management may increase development projects success,” International Journal of Project Management, Vol. 23, No. 3, 2005, pp. 181–192.
  • [69] J.J. Jiang, G. Klein, H.G. Hwang, J. Huang, and S.Y. Hung, “An exploration of the relationship between software development process maturity and project performance,” Information & Management, Vol. 41, No. 3, 2004, pp. 279–288.
  • [70] D.R. Goldenson and D.L. Gibson, “Demonstrating the impact and benefits of CMMITM: An update and preliminary results,” Defense Technical Information Center, Tech. Rep., 2003. [Online]. http://www.dtic.mil/dtic/tr/fulltext/ u2/a418481.pdf
  • [71] D.R. Goldenson and J.D. Herbsleb, “After the appraisal: A systematic survey of process improvement, its benefits, and factors that influence success.” Defense Technical Information Center, Tech. Rep., 1995. [Online]. http://www. dtic.mil/dtic/tr/fulltext/u2/a300225.pdf
  • [72] H.K. Klein and M.D. Myers, “A set of principles for conducting and evaluating interpretive field studies in information systems,” MIS Quarterly, Vol. 23, No. 1, 1999, p. 67.
  • [73] P. Runeson and M. Höst, “Guidelines for conducting and reporting case study research in software engineering,” Empir Software Eng, Vol. 14, No. 2, 2008, pp. 131–164.
  • [74] J. Arnowitz, M. Arent, and N. Berger, Effective Prototyping for Software Makers. Elsevier, 2007.
  • [75] A.L. Lederer and J. Prasad, “Causes of inaccurate software development cost estimates,” Journal of Systems and Software, Vol. 31, No. 2, 1995, pp. 125–134.
  • [76] A. Magazinius and R. Feldt, “Confirming distortional behaviors in software cost estimation practice,” in 37th EUROMICRO Conference on Software Engineering and Advanced Applications. IEEE, 2011, pp. 411–418.
  • [77] M. Jørgensen, “Top-down and bottom-up expert estimation of software development effort,” Information and Software Technology, Vol. 46, No. 1, 2004, pp. 3–16.
  • [78] A. Boonstra, “How do top managers support strategic information system projects and why do they sometimes withhold this support?” International Journal of Project Management, Vol. 31, No. 4, 2013, pp. 498–512.
  • [79] T.W. Malone and K. Crowston, “The interdisciplinary study of coordination,” ACM Computing Surveys, Vol. 26, No. 1, 1994, pp. 87–119.
  • [80] D. Stelzer and W. Mellis, Software Process: Improvement and Practice, Vol. 4, No. 4, 1998, pp. 227–250.
  • [81] K. Henttonen and K. Blomqvist, “Managing distance in a global virtual team: The evolution of trust through technology-mediated relational communication,” Strategic Change, Vol. 14, No. 2, 2005, pp. 107–119.
  • [82] M. Paasivaara and C. Lassenius, Software Process: Improvement and Practice, Vol. 8, No. 4, 2003, pp. 183–199.
  • [83] K. Beck, M. Beedle, A. Van Bennekum, A. Cockburn, W. Cunningham, M. Fowler, J. Grenning, J. Highsmith, A. Hunt, R. Jeffries et al., “Manifesto for Agile software development,” http://www.agilemanifesto.org, 2001.
  • [84] M. Jorgensen, “Practical guidelines for expert-judgment-based software effort estimation,” IEEE Software, Vol. 22, No. 3, 2005, pp. 57–63.
  • [85] M. Jørgensen, “A review of studies on expert estimation of software development effort,” Journal of Systems and Software, Vol. 70, No. 1-2, 2004, pp. 37–60.
  • [86] R.M. Flowe and J.B. Thordahl, “A correlational study of the SEI’s capability maturity model and software development performance in DoD contracts.” DTIC Document, Tech. Rep., 1994. [Online]. http://www.dtic.mil/dtic/tr/fulltext/ u2/a288890.pdf
  • [87] H.J. Yazici, “The role of project management maturity and organizational culture in perceived performance,” Project Management Journal, Vol. 40, No. 3, 2009, pp. 14–33.
  • [88] E.S. Andersen and S.A. Jessen, “Project maturity in organisations,” International Journal of Project Management, Vol. 21, No. 6, 2003, pp. 457–461.
  • [89] A. Raja, W. Mohsin, N. Ehsan, E. Mirza, and M. Saud, “Impact of emotional intelligence and work attitude on quality of service in the call centre industry of Pakistan,” in IEEE International Conference on Management of Innovation & Technology. IEEE, 2010, pp. 402–407.
  • [90] Y.J.T. Zidane, B.A. Hussein, J.Ø. Gudmundsson, and A. Ekambaram, “Categorization of organizational factors and their impact on project performance,” Procedia – Social and Behavioral Sciences, Vol. 226, 2016, pp. 162–169.
Uwagi
PL
Opracowanie rekordu w ramach umowy 509/P-DUN/2018 ze środków MNiSW przeznaczonych na działalność upowszechniającą naukę (2018).
Typ dokumentu
Bibliografia
Identyfikator YADDA
bwmeta1.element.baztech-9259cc14-b501-463b-a70c-cff3f77b89c0
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.