Effectiveness of Business Software Systems Development and Enhancement Projects versus Work Effort Estimation Methods

Authors: Beata Czarnacka-Chrobot

Abstract:

Execution of Business Software Systems (BSS) Development and Enhancement Projects (D&EP) is characterized by the exceptionally low effectiveness, leading to considerable financial losses. The general reason for low effectiveness of such projects is that they are inappropriately managed. One of the factors of proper BSS D&EP management is suitable (reliable and objective) method of project work effort estimation since this is what determines correct estimation of its major attributes: project cost and duration. BSS D&EP is usually considered to be accomplished effectively if product of a planned functionality is delivered without cost and time overrun. The goal of this paper is to prove that choosing approach to the BSS D&EP work effort estimation has a considerable influence on the effectiveness of such projects execution.

Keywords: Business software systems, development and enhancement projects, effectiveness, work effort estimation methods, software product size, software product functionality, project duration, project cost.

Digital Object Identifier (DOI): doi.org/10.5281/zenodo.1087958

References:

[1] M. Wideman, “First Principles of Project Management”. AEW Services, Vancouver 2005.
[2] Standish Group, “CHAOS Manifesto 2011”. West Yarmouth, Massachusetts, 2011.
[3] Standish Group, “CHAOS summary 2009”. West Yarmouth, Massachusetts, 2009.
[4] B. Czarnacka-Chrobot, “The economic importance of business software systems size measurement”, in Proc. of the 5th International Multi- Conference on Computing in the Global Information Technology (ICCGI 2010), 20-25 September 2010, Valencia, Spain, M. Garcia, J-D. Mathias, Eds. Los Alamitos, California-Washington-Tokyo: IEEE Computer Society Conference Publishing Services, pp. 293-299, 2010.
[5] T. C. Jones, “Patterns of software systems failure and success”. Boston, MA: International Thompson Computer Press, 1995.
[6] PCG, “2008 ERP report, topline results”. Denver: Panorama Consulting Group, 2008.
[7] PCG, “2011 ERP Report”. Denver: Panorama Consulting Group, 2011.
[8] Sofrecom Polska, Procesowcy.pl, „Maturity of IT System Development Processes in Polish Organizations” („Dojrzałość procesów rozwoju systemów informatycznych w polskich organizacjach”). Warsaw, 2011.
[9] T. C. Jones, “Software project management in the twenty-first century”. Burlington: Software Productivity Research, 1999.
[10] J. Johnson, “CHAOS rising”. in Proc. of 2nd Polish Conference on Information Systems Quality, Jachranka: Standish Group- Computerworld, 2005.
[11] Standish Group, “CHAOS summary 2008”. West Yarmouth, Massachusetts, 2008.
[12] B. Czarnacka-Chrobot, “The economic importance of business software systems development and enhancement projects functional assessment”. International Journal on Advances in Systems and Measurements, vol. 4, no 1&2, pp. 135-146. Wilmington, Delaware, USA: International Academy, Research, and Industry Association, 2011.
[13] Economist Intelligence Unit, “Global survey reveals late IT projects linked to lower profits, poor business outcomes”. Palo Alto, California, 2007; http://www.hp.com/hpinfo/newsroom/press/2007/070605xa.html (14.06.2013).
[14] Standish Group, “The CHAOS Report (1994)”. West Yarmouth, Massachusetts, 1995; http://www.projectsmart.co.uk/docs/chaosreport. pdf (14.06.2013).
[15] T. C. Jones, “Software Assessments, Benchmarks, and Best Practices”. Information Technology Series, Addison-Wesley, 2000.
[16] ISO/IEC 20926 Software and systems engineering - Software measurement - IFPUG functional size measurement method 2009, edition 2, ISO, Geneva, 2009.
[17] CMMI Product Team, "CMMI for Development, Version 1.3". Pittsburgh, Pennsylvania: Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-2010-TR-033, 2010; http://www.sei.cmu.edu/library/abstracts/reports/10tr033.cfm (14.06.2013).
[18] G. Klaschke, “What the CHAOS Chronicles 2003 Reveal”. http://www.costxpert.com/resource_center/chaos_compared.html (19.07.2006).
[19] E. Yourdon, “A new perspective on IT Metrics”. Soft Measures – A Total Metrics Newsletter Publication, vol. 1, no. 4., 2002.
[20] D.L. Babcock, “Managing Engineering and Technology: An Introduction to Management for Engineers”, edition 3. Upper Saddle River, NJ: Prentice Hall, 2001.
[21] H. Kerzner, “Project Management: A Systems Approach to Planning, Scheduling, and Controlling”, edition 8. New York: John Wiley and Sons, 2003.
[22] J. R. Meredith, S. J. Mantel Jr., “Project Management: A Managerial Approach”, edition 5. New York: John Wiley & Sons, 2003.
[23] S. Seweryn, „Discussing Main Factors Affecting Project’s Failure” („Omówienie podstawowych czynników wpływających na niepowodzenie przedsięwzięcia”), in Professionalism – The 3rd Conference on Project Management, pp. 200–203. Gdansk: Project Management Poland, 2000.
[24] T. DeMarco, T. Lister, “Waltzing with Bears: Managing Risk on Software Projects”. New York: Dorset House Publishing, 2003.
[25] D. Churchville, “The Seven Deadly Sins of Software Project Management”. ExtremePalanner Software, pp. 3-13, 2006.
[26] B. Czarnacka-Chrobot, “The role of benchmarking data in the software development and enhancement projects effort planning”. in New Trends in Software Methodologies, Tools and Techniques, H. Fujita, V. Marik, Eds. Proc. of the 8th International Conference SOMET’2009, Frontiers in Artificial Intelligence and Applications, vol. 199, pp. 106-127. Amsterdam-Berlin-Tokyo-Washington: IOS Press, 2009,.
[27] B. Czarnacka-Chrobot, “Factors of Effective Business Software Systems Development and Enhancement Projects Work Effort Estimation”, International Journal of Social and Human Sciences, vol. 6, pp. 46-53. Las Cruces, NM, USA: WASET, 2012.
[28] Z. Jiang, B. Jiang, and P. Naudé, “The effects of software size on development effort and software quality”, International Journal of Computer and Information Science and Engineering, vol. 1, no. 4, pp. 230-234, 2007.
[29] B. Czarnacka-Chrobot, “Reliability of the BSS development and enhancement projects effort estimation methods” (“Wiarygodnosc metod szacowania pracochlonnosci przedsiewziec rozwoju systemow oprogramowania wspomagajacych zarzadzanie”), in Business Informatics. Informatics in Management (Informatyka Ekonomiczna. Informatyka w zarzadzaniu), J. Sobieska-Karpinska, Ed., Wroclaw University of Economics Research Papers (Prace Naukowe Uniwersytetu Ekonomicznego we Wrocławiu), vol. 88, pp. 163-176. Wroclaw 2010.
[30] B. Czarnacka-Chrobot, “The effectiveness of business software systems functional size measurement”, in Proceedings of the 6th International Multi-Conference on Computing in the Global Information Technology (ICCGI 2011), 19-24 June 2011, Luxemburg City, Luxemburg, Constantin Paleologu, Constandinos Mavromoustakis, Marius Minea, Eds. Wilmington, Delaware, USA: International Academy, Research, and Industry Association, pp. 63-71, 2011.
[31] M. A. Parthasarathy, “Practical software estimation: function point methods for insourced and outsourced projects”. Addison Wesley Professional, 2007.
[32] ISO/IEC 14143 Information Technology – Software measurement – Functional size measurement – Part 1-6, ISO, Geneva, 2011.
[33] ISO/IEC 20968 Software engineering – Mk II Function Point Analysis - Counting practices manual, ISO, Geneva, 2002.
[34] ISO/IEC 24570 Software engineering – NESMA functional size measurement method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis, ISO, Geneva, 2005.
[35] ISO/IEC 19761 Software engineering – COSMIC: a functional size measurement method, edition 2, ISO, Geneva, 2011.
[36] ISO/IEC 29881 Information Technology – Software and systems engineering – FiSMA 1.1 functional size measurement method, ISO, Geneva 2010.
[37] B. Czarnacka-Chrobot, “The ISO/IEC Standards for the Software Processes and Products Measurement”, in New Trends in Software Methodologies, Tools and Techniques, H. Fujita, V. Marik, Eds., Proceedings of the 8th International Conference SOMET’2009, Frontiers in Artificial Intelligence and Applications, vol. 199, pp. 187- 200. Amsterdam-Berlin-Tokyo-Washington: IOS Press, 2009.
[38] B. Czarnacka-Chrobot, “Analysis of the functional size measurement methods usage by Polish business software systems providers”, in Software Process and Product Measurement, A. Abran, R. Braungarten, R. Dumke, J. Cuadrado-Gallego, J. Brunekreef, Eds., Proc. of the 3rd International Conference IWSM/Mensura 2009, Lecture Notes in Computer Science, vol. 5891, pp. 17–34. Berlin-Heidelberg: Springer-Verlag, 2009.
[39] P. R. Hill, “Some practical uses of the ISBSG history data to improve project management”. Hawthorn VIC, Australia: International Software Benchmarking Standards Group, 2007.
[40] International Software Benchmarking Standards Group, “The ISBSG: Software project estimates – how accurate are they?”. Hawthorn VIC, Australia: ISBSG, 2005.
[41] International Software Benchmarking Standards Group; http://www. isbsg.org/Isbsg.Nsf/weben/Functional%20Sizing%20Methods (14.06. 2013).
[42] US Government Accountability Office, “Cost estimating and assessment guide: best practices for developing and managing capital program costs”; http://www.gao.gov/new.items/d093sp.pdf (14.06.2013).
[43] G. Rule, “The most common Functional Size Measurement (FSM) methods compared”. St. Clare’s, Mill Hill, Edenbrige, Kent, UK: Software Measurement Services, 2010.