Evaluating CPI and SPI Indicators in Project Management Maturity Evolution
Resumo
Project management has become a common subject in Software Engineering and an everyday task in software organizations. In this task, the effective use of technologies can determine the success of any business; affect quality and ability to provide products and services on time. According to some authors, success in project execution can be associated with organization maturity. Organizations search for project management maturity in order to improve their management process and increase client satisfaction. Maturity is related to cost, time and quality, and can determine the success of projects. In the context of project management, we have two important indicators: Schedule Performance Indicator (SPI) and Cost Performance Indicator (CPI). SPI indicates whether the budgeted costs for work scheduled to date exceed the budgeted costs for the work performed to date. CPI indicates whether the actual costs for the work performed to date exceed the budgeted costs for the work performed to date. These indicators give information about whether or not the project is on track, so they are important factors which represent success in project management. This paper discusses how Cost/Schedule Performance Indicators are related to project management maturity and presents the results based on IT professionals’ opinion analysis.
Referências
Ahiable, A.; Dalcher, D. (2005) “Failure, Success, and Maturity in Projects”, IEEE International Engineering Management Conference.
Ali, A.; Money, W. (2005) “A Study of Project Management System Acceptance”, Hawaii International Conference on System Sciences.
Attarzadeh, I.; Hock, O. (2009) “Modern Project Management: A New Forecasting Model to Ensure Project Success”, International Conference on Future Computer and Communication.
Hillson, D. (2004) “Earned Value Management and Risk Management: A Practical Synergy”, Available at: http://www.risk-doctor.com/pdf-files/cev-b1004.pdf.
Bianchi, A. J. (2001) “Management Indicators Model to Evaluate Performance of IT Organizations”, Portland International Conference on Management of Engineering and Technology.
Kerzner, H. (2001) “Strategic Planning for Project Management using a Project Management Maturity Model”, 1ª ed. John Wiley & Sons.
Lu, X.; Shu, L.; Li, J. (2008) “Correlation Analysis between Maturity Factors and Performance Indexes in Software Project”, International Conference on Industrial Engineering and Engineering Management.
P3M3 (2008) “Portfolio, Programme & Project Management Maturity Model”, P3M3 Public Consultation Draft 2.0.
OPM3 (2003) “Organizational Project Management Maturity Model”, Knowledge Foundation, Pennsylvania: Project Management Institute.
PMBOK (2004) “PMBOK® Guide: Um guia do conjunto de conhecimentos do gerenciamento de projetos”, Pennsylvania: Project Management Institute, 3. ed.
PMI (2008). “Benchmarking em GP no Brasil Relatório 2008 (Visão Geral)”, Available at: http://pmi-rio.ning.com/page/benchmarking-1.
Prado, D. (2008) “Maturidade em Gerenciamento de Projeto”, Série Gerência de Projetos. Vol. 7, INDG Tecs.
Ramasubbu, N.; Balan, R. K. (2009) “The Impact of Process Choice in High Maturity Environments: An Empirical Analysis”, IEEE International Conference on Software Engineering. CMMI (2010) “Capability Maturity Model Integration for Development”, Version 1.3. CMU/SEI-2010-TR-033. USA.
SurveyMonkey(2009) Available at: http://www.surveymonkey.com/
Xian, Z.; Xue-qing, W. (2010) “Fuzzy Evaluation of Project Management Maturity Model Based on Neural Network”, IEEE International Conference on Advanced Management Science.
