Developing a Power BI dashboard requires multiple skills. Ralph Kimball, the data warehousing and business intelligence (DW/BI) guru has written extensively on the subject.
You need to know project management and business analysis to create useful project management dashboards. You need to know the industry, the domain [in this case, project management] and Power BI in general. Then you need to be specific with your client about what to build in the key knowledge or performance areas of project management: cost, schedule, risk, resource management, capacity, procurement integration, scope, quality, etc.
So the first thing you need to do is define these areas and determine if all of these areas will be thoroughly integrated into this dashboard.
Then you need to understand what the data sources are. For example, in our industry [oil/gas, civil construction], the schedule data comes from Oracle Primavera Cloud/P6. It may also come from Microsoft Project, powerproject.
Cost data can come from SAP, JD Edwards EnterpriseOne, Oracle Unifier, Kildrummy CostMANAGEMENT, an Access database or an Excel spreadsheet. We need to identify the sources of the data. We also need to understand the client’s specific business rules.
Risk data can come from Oracle Primavera Risk Analysis, Deltek Acumen Risk, Safran Risk, RiskyProject.
Let’s say the tool is Oracle Primavera Cloud or Primavera P6. How is it used? How is the WBS designed? How are the activity codes and the PSA designed? How are projects organized? How to manage baselines?
After understanding the data, it’s a matter of transferring it into Power BI. When I get the data, I link to the data source. I write queries when I need to retrieve the information in a specific format and in specific fields.
Never give up guysDaniel Augusto