Lessons from a Successful Data Warehousing Project Management

Lessons from a Successful Data Warehousing Project Management

Nayem Rahman (Portland State University, Portland, OR, USA)
DOI: 10.4018/IJITPM.2017100103
OnDemand PDF Download:
No Current Special Offers


This article provides an overview of project management aspects of a data warehouse application implementation. More specifically, the article discusses the project's implementation, challenges faced, and lessons learned. The project was initiated with an objective to redesign the procurement data pipeline of a data warehouse. The data flows from enterprise resource planning (ERP) system to enterprise data warehouse (EDW) to reporting environments. This project was challenged to deliver more quickly to the consumers with improved report performance, and reduced total cost of ownership (TCO) in EDW and data latency. Strategies of this project include providing continuous business value, and adopt new technologies in data extraction, transformation and loading. The project's strategy was also to implement it using some of the agile principles. The project team accomplished twice the scope of previous project in the same duration with a relatively smaller team. It also achieved improved quality of the products, and increased customer satisfaction by improving the reports' response time for management.
Article Preview

Literature Review

Data warehouse is the central repository of an organization’s enterprise data. It holds both historical and current data. Organizations build their reporting environment and dashboards on top of the data warehouse. These data come from heterogeneous sources of operational databases and data marts (Rahman, 2016). In data warehouses hundreds of applications are built over a period of time. Each year dozens of applications are released as part of new project or as part of enhancements of existing applications. These application projects may cause many unforeseen technical challenges. The data warehouse project managers need to have technical background as well as leadership capability to be successful. Otherwise, they might not comprehend unforeseen technical challenges and risks until they are imminent at which point they find it difficult to meet the deadline, manage resources and do a flawless production release. (Rahman, 2013).

Complete Article List

Search this Journal:
Open Access Articles
Volume 13: 4 Issues (2022): Forthcoming, Available for Pre-Order
Volume 12: 4 Issues (2021): 3 Released, 1 Forthcoming
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