Software Project Costing: Coupling CMMI and PMBOK into a Generic Costing Framework

Software Project Costing: Coupling CMMI and PMBOK into a Generic Costing Framework

Liran Edelist (Graduate School of Business Administration, Bar-Ilan University, Ramat-Gan, Israel), Roy Gelbard (Graduate School of Business Administration, Bar-Ilan University, Ramat-Gan, Israel), and Jeffrey Kantor (Odette School of Business, University of Windsor, Windsor, ON, Canada)
DOI: 10.4018/jitpm.2012100105
OnDemand PDF Download:
No Current Special Offers


This study puts forward a generic and comprehensive costing framework for software projects that aims for simplicity. This is achieved by integrating commonly used CMMI (Capability Maturity Model Integration) and PMBOK (Project Management Body of Knowledge) costing concepts in a broader organizational context. The costing framework comprises three layers: costing targets, costing activities, and policy evaluation. While the first two layers are derived from commonly used software engineering elements, the third integrates an organizational perspective through software engineers, project managers, accountants and top management. Employment of CMMI and PMBOK standards allows for easy adoption of the proposed model by organizations that are already relying on these standards.
Article Preview


Cost management, or the costing process in most projects increasingly adheres to standards set by the PMBOK (A Guide to the Project Management Body of Knowledge published by the Project Management Institute, PMI) and the CMMI (Capability Maturity Model Integration published by the Software Engineering Institute, SEI). However, the two treat cost management with varying approaches, a discrepancy that may confuse the average user who is not an accounting specialist. The PMBOK defines the costing process as one of the project's core activities, comprising three stages: cost estimating, cost budgeting, and cost control (Kinsella, 2002; PMI, 2004). At the same time, the CMMI, in its continuous representation, does not consider costing as an independent process but groups costing elements within its six project management process areas: project planning, project monitoring and control, supplier agreement management, integrated project management, risk management, and quantitative project management (SEI, 2002).

We contend that in order to make informed managerial decisions, detailed costing data are mandatory and these should include all types of costs involved in manufacturing a product or in providing a service. These data are derived from the firm's income statement and backup schedules and include historical execution data as well as future estimates and forecasts (Needy, 2003). Such data are defined by both the PMBOK and the CMMI, albeit in different ways. In the PMBOK each one of the costing stages (cost estimating, cost budgeting, and cost control) is described in terms of inputs, tools and techniques, and outputs. Two of these – the inputs and outputs – interact with other core processes and activities as part of the complete project management framework. While the CMMI does not define costing activities as a separate process or a specific model, it, too, highlights the importance of integrating one system with another (Valerdi et al., 2007). Both the CMMI and the PMBOK describe the costing process along the project life cycle (also termed PLC), starting with project planning and estimating and ending with control activities. However, both standards deal only with direct costs of the projects and are restricted to the level of project management, thus disregarding a broader organizational or financial perspective.

Despite considering the overlapping role of cost management in various aspects of the project, both standards are not all-inclusive. The integration of several fields of engineering, as described in the CMMI, or well-defined project managing processes as suggested by the PMBOK, do not necessarily take into account the “big picture” – an organizational perception of the project as merely one component among other projects and activities. The current research puts forward an extensive framework – the Generic Costing Framework, henceforth called the GCF model – that provides broader insights into costing. It does so by dealing with both direct and indirect costs, considering the profitability of project tasks, and defining the responsibilities and workflow within an organization among all functions involved in the initiation of a software engineering project: engineers, project managers, analysts, and other management levels. Moreover, it can be easily adopted by organizations currently using the PMBOK or CMMI standards in order to enhance costing information and improve decision and analysis processes.

Complete Article List

Search this Journal:
Volume 14: 1 Issue (2023)
Volume 13: 4 Issues (2022): 3 Released, 1 Forthcoming
Volume 12: 4 Issues (2021)
Volume 11: 4 Issues (2020)
Volume 10: 4 Issues (2019)
Volume 9: 4 Issues (2018)
Volume 8: 4 Issues (2017)
Volume 7: 4 Issues (2016)
Volume 6: 4 Issues (2015)
Volume 5: 4 Issues (2014)
Volume 4: 4 Issues (2013)
Volume 3: 4 Issues (2012)
Volume 2: 4 Issues (2011)
Volume 1: 4 Issues (2010)
View Complete Journal Contents Listing