Abstract

Defining business requirement is a critical activity in determining what functionality the enabling technology solution needs to deliver. Customer Centric Project Management (CCPM) is the continuous re-examination, evolution and definition of the stakeholders' business requirements. The aim of this research and impact analysis was to examine all the changes in the organization that make it viable. The objective was to explore the application of academic methodology, identify sine qua non components in operational environments and by extension inspire future reflections, future research to pro-actively prevent one or the most problematic aspects that fail projects.

Findings and conclusions are primarily based on empirical evidence from observing the behaviour of CCPM applied to actual projects/cases, current literature and interviews with senior project managers. The focus of interest was on the impacts on business stakeholders, developers, the methodology, business analysts, organizational executives and on a promising framework for a solution.

To make the methodology work, the findings point to the imperative to engage stakeholders, assign needed accountability, use business analysts, involve executives and allow the PM to govern the project.